em driver, 82574L chip, and possibly ASPM
Jack Vogel
jfvogel at gmail.com
Tue Nov 23 18:36:15 UTC 2010
82574 is supposed to be em, not igb :) Its always had this kind of
'in-between'
status, it was targeted as a 'client' or consumer part, but it has MSIX
which
make it almost like 8257[56].
Mike, there are some further 82574 changes to shared code that I'm looking
into today.
Jack
On Tue, Nov 23, 2010 at 10:17 AM, Mike Tancsa <mike at sentex.net> wrote:
> On 11/23/2010 12:39 PM, Sean Bruno wrote:
> > On Tue, 2010-11-23 at 04:47 -0800, Ivan Voras wrote:
> >> It looks like I'm unfortunate enough to have to deploy on a machine
> >> which has the 82574L Intel NIC chip on a Supermicro X8SIE-F board, which
> > igb0 at pci0:5:0:0: class=0x020000 card=0x8975152d chip=0x10c98086
>
> Strange, the 82574 attaches as em for me, not igb
>
> 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 enabled with 1 message
> 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
> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected
> ecap 0003[140] = Serial 1 001517ffffed68a4
>
> Normally, its msix, but I had disabled that hoping it would fix the problem
>
> em1: <Intel(R) PRO/1000 Network Connection 7.1.7> port 0x2000-0x201f mem
> 0xb4100000-0xb411ffff,0xb4120000-0xb4123fff irq 16 at dev
> ice 0.0 on pci10
> em1: Using an MSI interrupt
> em1: [FILTER]
> em1: Ethernet address: 00:15:17:ed:68:a4
>
>
> ---Mike
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>
More information about the freebsd-net
mailing list