On Wed, Apr 11, 2007 at 01:05:12PM +0300, Stefan Lambrev wrote: > Hi, > > -cut- > > > I thought getting latest nfe source will help but it doesn't. > > > > > > -cut- > > > > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > > > > >According to the above message, it seems that you use new nfe(4). :-) > > > Yes this is is with latest nfe, but I've got watchdog timeouts with > previous version of this driver too.
Without polling(4) on shared interrupt system it's expected one. > > > interrupt total rate > > > irq1: atkbd0 6660 0 > > > irq12: psm0 153054 0 > > > irq15: ata1 778797 1 > > > irq16: pcm0 2735727 7 > > > irq17: skc0 115669786 296 > > > irq18: nvidia0 24802500 63 > > > irq21: ohci0+ 2418887 6 > > > irq22: nfe0 ehci0 92319117 236 > > ^^^^^^^^^^ > >You are using shared interrut so it's possible to get occasional > >watchdog timeouts. polling(4) should fix your issue here. > > > I'll try this, and test :), It wasn't hard to generate generate watchdog > timeout. > But isn't polling bad under heavy load and busy CPU(s) ? Could be. YMMV. You couldn't also get best performance if interrupt is shared with other devices. > > > > cpu0: timer 780827522 2000 > > > Total 1019712050 2612 > > > > > > FreeBSD 6.2-STABLE i386 > > > > > > nfe0: <NVIDIA nForce4 CK804 MCP9 Networking Adapter> port 0xb000-0xb007 > > > mem 0xd5000000-0xd5000fff irq 22 at device 10.0 on pci0 > > > > > > >nfe(4) should be teached to use MSI/MSI-X for PCI-Express/PCI-X based > >adapters but it's not done yet. > > > > > > -- Regards, Pyun YongHyeon _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
