nve timeout (and down) regression?

[Ion-Mihai Tetcu]

On Fri, 24 Mar 2006 12:55:41 -0800
"Kevin Oberman" <oberman at es.net> wrote:

> > Date: Fri, 24 Mar 2006 22:33:17 +0200
> > From: Ion-Mihai Tetcu <itetcu at people.tecnik93.com>
> > 
> > On Thu, 23 Mar 2006 14:34:24 -0800
> > "Kevin Oberman" <oberman at es.net> wrote:
> > 
> > > > Date: Thu, 23 Mar 2006 21:59:56 +0000 (UTC)
> > > > From: "Bjoern A. Zeeb" <bzeeb-lists at lists.zabbadoz.net>
> > > > 
> > > > On Thu, 23 Mar 2006, JoaoBR wrote:
> > > > 
> > > > > On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
> > > > >
> > > > > nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for
> > > > > me) in end of dezember
> > > > >
> > > > > since a month or so with recent releng_6 the problem came back, timeouts and
> > > > > stopping rx/tx
> > > > 
> > > > did you do more updates in the timeframe from december to about a
> > > > month ago?
> > > > 
> > > > if the problem was gone and is back now any (exact) dates to narrow
> > > > down the timeframe where the problem came back would be very helpful.
> > 
> > nve0: <NVIDIA nForce MCP9 Networking Adapter> port 0xbc00-0xbc07 mem 0xfebfa000-0xfebfafff irq 22 at device 10.0 on pci0
> > nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfebfa000
> > nve0: Ethernet address 00:0a:48:1d:c6:97
> > miibus1: <MII bus> on nve0
> > nve0: bpf attached
> > nve0: Ethernet address: 00:0a:48:1d:c6:97
> > nve0: [MPSAFE]
> > 
> > This happens w/o any "real" activity on that interface (which goes into
> > an Allied Telesyn switch):
> > .......
> > Mar 24 19:39:54 worf kernel: nve0: device timeout (1)
> > Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN
> > Mar 24 19:39:55 worf kernel: nve0: link state changed to UP
> > Mar 24 19:40:14 worf kernel: nve0: device timeout (1)
> > Mar 24 19:40:14 worf kernel: nve0: link state changed to DOWN
> > Mar 24 19:40:15 worf kernel: nve0: link state changed to UP
> > Mar 24 19:40:33 worf kernel: nve0: device timeout (2)
> > Mar 24 19:40:33 worf kernel: nve0: link state changed to DOWN
> > Mar 24 19:40:34 worf kernel: nve0: link state changed to UP
> > Mar 24 19:45:52 worf kernel: nve0: device timeout (1)
> > Mar 24 19:45:52 worf kernel: nve0: link state changed to DOWN
> > Mar 24 19:45:53 worf kernel: nve0: link state changed to UP
> > .........
> > 
> > 
> > FreeBSD worf.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Tue Mar 21 01:39:15 EET 2006     itetcu at worf.tecnik93.com:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> Note that we are running on i386 running am an AMD64 platform.

I just enabled the nve0 on my desktop (I'm using sk0, it's a Asus
A8N-SLI Deluxe motherboard, both interfaces connected to the same 8-port
Surecom switch - talking about very inexpensive :) and it seems to work
OK.

nve0: <NVIDIA nForce MCP9 Networking Adapter> port 0xb000-0xb007 mem 0xca100000-0xca100fff irq 23 at device 10.0 on pci0
nve0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xca100000
nve0: Ethernet address 00:15:f2:39:09:08
miibus1: <MII bus> on nve0
nve0: bpf attached
nve0: Ethernet address: 00:15:f2:39:09:08
nve0: [MPSAFE]

FreeBSD it.buh.tecnik93.com 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Fri Feb 24 07:01:54 EET 2006     root at it.buh.tecnik93.com:/usr/obj/usr/src/sys/IT6_B_P  i386

> I updated my system (which was happy on Feb. 15 code) to March 13 code
> and I am still running fine. No errors at all. Also, another system was
> updated to RELENG_6 yesterday and it is also running clean.
> 
> Again, all systems are identical dual core AMD64 systems running i386
> code. (We would like to run amd64, but OpenOffice.org still does not run
> on it and we need that.)

Both my systems are single core single CPU.

> Only the system in Iowa with the AT switch is seeing problems.
> 
> Even if there is no traffic, it is possible that something that is
> negotiated by the switch is triggering the problem.

Possibly, but I think I remember seeing the same w/o cable plugged-in;
I'll try to remember to test this for a a few minutes when I'll be
on-site next week.


-- 
IOnut - Unregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"

BOFH excuse #266:
All of the packets are empty