Date: Thu, 18 Aug 2005 20:37:51 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu> To: alan bryan <alanbryan1234@yahoo.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: nve0 nvidia onboard ethernet dies daily on 6.0 beta1 Message-ID: <4304D57F.4030804@t-hosting.hu> In-Reply-To: <20050818183051.10024.qmail@web50307.mail.yahoo.com> References: <20050818183051.10024.qmail@web50307.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
alan bryan wrote: >I'm still having problems with my onboard ethernet. >It usually runs for a day or two and then I see this >in the dmesg: >... >nve0: device timeout (63) >nve0: link state changed to DOWN >nve0: link state changed to UP >nve0: device timeout (63) >nve0: link state changed to DOWN >nve0: link state changed to UP >nve0: device timeout (64) >nve0: link state changed to DOWN >nve0: link state changed to UP >... > >It seems that once it counts up to 64 that it then >dies. What does that number count stand for? Is >there a way to prevent this? Why does the link state >keep going up/down (although I haven't noticed any >problems and web/shh seem to work fine until it dies) > >This is on a Shuttle XPC SN25P system running 6.0 >beta1. > >Thanks, >Alan Bryan > > > The nve driver has a lot of problems. You experienced just device timeouts, but other people - including me - experiences system crashes. As for me, I've had two kind of kernel panics, and device timeouts too. Cheers, Gabor Kovesdan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4304D57F.4030804>