Problems with NIC
This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled dc0: TX underrun -- increasing TX thresholdn isa0 dc0: TX underrun -- increasing TX thresholdort 0x64,0x60 on isa0 dc0: failed to force tx and rx to idle stateed irqs 0 Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source : dc0: watchdog timeoutn't assign resources (port) dc0: failed to force tx and rx to idle stateort) dc0: watchdog timeoutn't assign resources (port) dc0: failed to force tx and rx to idle stateort) dc0: watchdog timeoutquency 379986358 Hz quality 800 dc0: failed to force tx and rx to idle state dc0: watchdog timeout4K020H1/A08.1500 [39560/16/63] at ata0-master UDMA66 dc0: failed to force tx and rx to idle state dc0: watchdog timeout Apr 13 05:21:16 www kernel: dc0: watchdog timeout Apr 13 05:21:16 www kernel: dc0: failed to force tx and rx to idle state Basicly I think I will replace this NIC cause I have had nothing but problems with it. It's an old one I have had in several boxs as a spare/backup. Might be going south on me. One other ? how do I start and stop networking on FreeBSD. I am just moving to FreeBSD from SV Linux and am used to a /etc/rc.d/init.d/network restart. Thanks for any input. -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NIC
On Wed, Apr 13, 2005 at 05:50:27AM +, Jaimie Garner wrote: This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source Looks like the USB bus (ohci0) and your network card are sharing an interrupt line. My guess would be that a USB device generates too much interrupts causing the kernel to throttle them. This then screws up the network. According to polling(4), the dc driver supports polling instead of using an interrupt line. You could try rebuilding the kernel with polling support and see if the problem goes away. Or you could disable ohci0 in the bios, or plug the offending USB device into another port. Or you could try to force the dc triver to use another interrupt line. See the acpi manual page and google for 'irq routing freebsd'. I _think_ you should do the following: 'ps -xa|grep irq' will show which irq's are free. Let's say that irq 10 is still free. Now you'd have to find the pci address of the network card with 'pciconf -l -v|grep dc0'. Let's say you get something like '[EMAIL PROTECTED]:11:0' You can now tune the interrupt by setting the following in /boot/device.hints: hw.acpi.pci.link.0.11.0.irq=10 HTH, Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards pgpQNhMiujlSb.pgp Description: PGP signature
Re: Problems with NIC
How about disable USB altogether since it is not used on this machine. Thanks for the info On Wednesday 13 April 2005 16:15, Roland Smith wrote: On Wed, Apr 13, 2005 at 05:50:27AM +, Jaimie Garner wrote: This just started happing this evening not sure what is up. The nic is a Linksys LNE 100 V 4.something I forget now. I had some weird errors a while back when I first installed 5.3-RELEASE but i disabled ACPI and they seemed to work fine. Here is some info dc0: ADMtek AN985 10/100BaseTX port 0x1000-0x10ff mem 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 miibus0: MII bus on dc0i0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:03:6d:16:09:1e dc0: if_start running deferred for Giant dc0: [GIANT-LOCKED] This looks odd especaly this: Interrupt storm detected on irq9: dc0 ohci0; throttling interrupt source Looks like the USB bus (ohci0) and your network card are sharing an interrupt line. My guess would be that a USB device generates too much interrupts causing the kernel to throttle them. This then screws up the network. According to polling(4), the dc driver supports polling instead of using an interrupt line. You could try rebuilding the kernel with polling support and see if the problem goes away. Or you could disable ohci0 in the bios, or plug the offending USB device into another port. Or you could try to force the dc triver to use another interrupt line. See the acpi manual page and google for 'irq routing freebsd'. I _think_ you should do the following: 'ps -xa|grep irq' will show which irq's are free. Let's say that irq 10 is still free. Now you'd have to find the pci address of the network card with 'pciconf -l -v|grep dc0'. Let's say you get something like '[EMAIL PROTECTED]:11:0' You can now tune the interrupt by setting the following in /boot/device.hints: hw.acpi.pci.link.0.11.0.irq=10 HTH, Roland -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
