Intel 82574L Cards not working 'attach returned 6'

Status
Not open for further replies.

madmax14304

Cadet
Joined
Jul 6, 2011
Messages
3
I'm running FreeNAS 8 and tried adding two Intel gigabit network cards but I'm getting an "device_attach: em1 attach returned 6" error. Can someone point me in the right direction? Is it possible that if_em module is built into the FreeNAS kernel and that module is old, or incompatible with my card? I built a FreeBSD System, compiled the driver and copied it to freenas, but when loading it indicates that a file already exists.

Thanks

em1: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x4000-0x401f mem 0xd9d20000-0xd9d3ffff,0xd9d04000-0xd9d07fff irq 18 at device 0.0 on pci3
em1: Memory Access and/or Bus Master bits were not set!
em1: MSIX: insufficient vectors, using MSI
em1: No MSI/MSIX using a Legacy IRQ
em1: Setup of Shared code failed
device_attach: em1 attach returned 6

em2: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0x5000-0x501f mem 0xd9e20000-0xd9e3ffff,0xd9e04000-0xd9e07fff irq 19 at device 0.0 on pci11
em2: Memory Access and/or Bus Master bits were not set!
em2: MSIX: insufficient vectors, using MSI
em2: No MSI/MSIX using a Legacy IRQ
em2: Setup of Shared code failed
device_attach: em2 attach returned 6
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
Sorry to revive an old thread but I just got this message on 9.1 with an Intel Pro 1000

em1: <Intel(R) PRO/1000 Network Connection 7.3.7> port 0x4000-0x401f mem 0xd2420000-0xd243ffff,0xd2480000-0xd24fffff,0xd2400000-0xd2403fff irq 18 at device 0.0 on pci3
em1: Memory Access and/or Bus Master bits were not set!
em1: Unable to allocate bus resource: RX MSIX Interrupt 0
device_attach: em1 attach returned 6
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Have you tried a Linux live CD or Windows to see if the NIC actually works? One person had a similar problem and after racking his brain for days he found out the NIC was broken.
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
Hey thanks for getting back. So to be completely honest I'm running this on ESXi 5 and the card is passed through via VT-d. I will do some more investigation to make sure the cards work properly within ESXi.

Thanks man
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
Yup NICs work fine, if I don't pass through and just attach them as standard e1000 NICs that ESXi creates it all works perfect.

So in 9.1 I get that error and can't see any NICs, in 8.3.1 they attach fine but won't get an IP or work in any NIC like way. I see lots of posts on the webz talking about drivers for these NICs being an issue
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
They get discovered in FreeNAS 8 but won't pick up an IP so they don't work in 8 either. In 9 they won't even hook in. Grrr... Guess I'll just have to keep using them as virtualized devices :(
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Well, when someone chooses to virtualize, they are totally on their own to deal with any potential problems. It's too hard to try to help figure out what is actually the problem in the mess between the actual hardware, the virtualized hardware, and the hypervisor settings.
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
I can appreciate that, but it works with everything else, Windows 7 VM and Debian 6 VM, flawlessly when passed through so I have to conclude that the issue lies somewhere in FreeNAS. I wonder if these two lines is what I should be looking into
em1: Memory Access and/or Bus Master bits were not set!
em1: Unable to allocate bus resource: RX MSIX Interrupt 0

I'll update if I find something for anyone else who is trying to use these
 

funkymcbain

Cadet
Joined
Aug 24, 2013
Messages
6
For anyone who might read this thread in the future, first of all I say hello from the past, and second I hate to say it but I ended up reverting back to 8.3.1 with a couple of flags to disable MSI/MSI-X. 9.1 is hopeless unfortunately, even if it does work I wouldn't trust the stability of it all.

#/boot/loader.conf
hw.re.msi_disable=1
hw.re.msix_disable=1
 
Status
Not open for further replies.
Top