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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
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
Forgot to also add the details of the Ethernet as it's being detected if that helps: nve0: <NVIDIA nForce MCP9 Networking Adapter> port 0xb000-0xb007 mem 0xd8100000-0xd8100fff irq 5 at device 10.0 on pci0 nve0: Ethernet address 00:30:1b:b8:86:dc miibus0: <MII bus> on nve0 ukphy0: <Generic IEEE 802.3u media interface> on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:30:1b:b8:86:dc nve0: [GIANT-LOCKED] Thanks for any help. --Alan --- alan bryan <alanbryan1234@yahoo.com> 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 > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable> To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" >__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com