> Same backtrace as reported here? I'm unable to get the new backtrace, but judging from what I can see on the console pre-reboot, it's exactly the same deal since 8.0-RELEASE - panic with dummynet as main star.
> What revision of the em(4) driver code are you using? I know Jack has > been working out certain quirky issues lately, and there have been > updates to the code since last you posted an update to your problem. em0: <Intel(R) PRO/1000 Network Connection 7.1.8> port 0x2040-0x205f mem 0xb1a00000-0xb1a1ffff,0xb1a25000-0xb1a25fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:15:17:... em1: <Intel(R) PRO/1000 Network Connection 7.1.8> port 0x1000-0x101f mem 0xb1900000-0xb191ffff,0xb1920000-0xb1923fff irq 16 at device 0.0 on pci2 em1: Using MSIX interrupts with 3 vectors em1: [ITHREAD] em1: [ITHREAD] em1: [ITHREAD] em1: Ethernet address: 00:15:17:.. > Maybe Jack could shed some light on the whether the updates could > somehow work out to be a fix for your problem -- or whether or not > your issue is even related to the em(4) driver. I'm not sure anymore that em is at fault here. Anyway, currently I'm running FreeBSD 8.2-PRERELEASE #1: Fri Jan 7 17:19:28. If something happened since then that could fix this, I'll gladly update. _______________________________________________ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"
