pending em0 commits for FreeBSD 8.1 STABLE

Mike Tancsa mike at sentex.net
Fri Oct 29 02:06:28 UTC 2010


At 09:39 PM 10/28/2010, Bjoern A. Zeeb wrote:
>On Fri, 29 Oct 2010, Denis Ahrens wrote:
>
>>Hi Jack
>>
>>It seems that I am also victim to some strange bug which is
>>possibly the fault of the em0 code.
>>
>>After some research I have seen that you have changed that
>>code awhile ago which could possibly have fixed my problems
>>already.
>>
>>The code changes:
>>
>>http://lists.freebsd.org/pipermail/svn-src-head/2010-September/020313.html
>>http://lists.freebsd.org/pipermail/svn-src-head/2010-September/020314.html
>>http://lists.freebsd.org/pipermail/svn-src-head/2010-September/021027.html
>>
>>The last one even had an MFC of one week. But it was never committed to
>>STABLE.
>>
>>It would be nice if you could commit that so I can update my code and see
>>if the problem still occurs.
>
>Especially the first two seem to be interesting.

I am testing 7.1.5 on cvsup.sentex.ca, which was locking up the nic 
and crashing a few weeks ago under specific loads the box sees on 
weekends.  Swapping in a bge nic solved the problem. I had changed 
out all the other hardware, so I dont think its an issue with the em 
nics themselves. I have changed back to the em nic and it will take a 
good week to see if it solves that problem or not.

em1 at pci0:10:0:0:        class=0x020000 card=0x34ec8086 
chip=0x10d38086 rev=0x00 hdr=0x00
     vendor     = 'Intel Corporation'
     device     = 'Intel 82574L Gigabit Ethernet Controller (82574L)'
     class      = network
     subclass   = ethernet
     cap 01[c8] = powerspec 2  supports D0 D3  current D0
     cap 05[d0] = MSI supports 1 message, 64 bit
     cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
     cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled
ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
ecap 0003[140] = Serial 1 001517ffffed68a4



I am also testing the driver on a couple of test motherboards and for 
some reason, it does not want to boot RELENG_8 on one of them. The 
same hardware boots HEAD. On RELENG_8, the last thing to appear is

em0: <Intel(R) PRO/1000 Network Connection 7.1.6> port 0xf040-0xf05f 
mem 0xfe400000-0xfe41ffff,0xfe428000-0xfe428fff irq 20 at device 25.0 on pci0
em0: attempting to allocate 1 MSI vectors (1 supported)
msi: routing MSI IRQ 256 to local APIC 0 vector 50
em0: using IRQ 256 for MSI
em0: Using an MSI interrupt

Its an oddball nic so I am not sure why it on RELENG_8 has issues. 
The stock RELENG_8 driver works

em0 at pci0:0:25:0:        class=0x020000 card=0x00368086 
chip=0x10f08086 rev=0x06 hdr=0x00
     vendor     = 'Intel Corporation'
     class      = network
     subclass   = ethernet
     cap 01[c8] = powerspec 2  supports D0 D3  current D0
     cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
     cap 13[e0] = PCI Advanced Features: FLR TP


>>My problems are looking like this one:
>>
>>http://lists.freebsd.org/pipermail/freebsd-stable/2010-October/059618.html
>>
>>My FreeBSD STABLE codebase is from 29. September 2010

I will give it a try.  I was able to recreate the issue with the 
stock RELENG_8 driver. I will try with the version from HEAD

         ---Mike




--------------------------------------------------------------------
Mike Tancsa,                                      tel +1 519 651 3400
Sentex Communications,                            mike at sentex.net
Providing Internet since 1994                    www.sentex.net
Cambridge, Ontario Canada                         www.sentex.net/mike



More information about the svn-src-head mailing list