--On 10 August 2012 12:18 -0700 "EXT-Glatting, Dennis P"
<[email protected]> wrote:
I've seen this too on a H8DG6-F but changed to the igb interfaces. I am
also seeing a problem under ESXi 5.0 on an unpatched system but haven't
had the opportunity to patch (ESXi) it. There I will see these messages
under a FreeBSD instance:
nms# uname -a
FreeBSD nms 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #9: Mon Aug 6 22:02:46
PDT 2012 root@nms:/sys/amd64/compile/SMUNI amd64
nms# grep em0 /var/log/messages
Jul 9 15:50:39 nms kernel: em0: <Intel(R) PRO/1000 Legacy Network
Connection 1.0.4> port 0x2000-0x203f mem
0xd1020000-0xd103ffff,0xd1000000-0xd100ffff irq 18 at device 0.0 on pci2
Jul 9 15:50:39 nms kernel: em0: Memory Access and/or Bus Master bits
were not set! Jul 9 15:50:39 nms kernel: em0: Ethernet address:
00:0c:29:a2:36:c2 Jul 10 09:28:49 nms kernel: em0: Watchdog timeout --
resetting
Your NIC's ID differently to mine:
Mine - em0: <Intel(R) PRO/1000 Network Connection 7.2.3>
Yours - em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.4>
Looks like that's different driver code? (presuming the 7.2.3 and 1.0.4 are
the driver versions) - the 'virtual' NIC created by ESXi must be using a
different driver.
Also - I don't get anything logged on the console or anywhere - it just
"stops" (i.e. no watchdog errors or similar - nothing).
Aside from the apparent 'billions' of packets errors (or corrupt counters)
- the only other thing I've found that was weird was the '-1's in the dump
from doing 'dev.em.0.debug=1'
I think you've got a problem :( - But probably not the same problem that I
have on this SuperMicro machine :-(
-Karl
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[email protected]"
