Contribute
Register

AppleIntelE1000e Hardware Hang - Ethernet port non-responsive until reboot

Status
Not open for further replies.
Joined
May 6, 2014
Messages
232
Motherboard
Asus Maximus VI Extreme, 32GB Kingston HyperX RAM, 512GB Samsung 840 Pro SSD, 4 x WD 3TB HDs
CPU
Intel Core i7 4770K (Quad Core; Haswell)
Graphics
Gigabyte Windforce 3 GTX 780 3GB (Not Overclocked)
Mac
  1. iMac
  2. MacBook Air
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. iMac
  2. LC
  3. Performa
  4. Plus
  5. Power Mac
  6. PowerBook
  7. Quadra
  8. SE
  9. Xserve
Mobile Phone
  1. Android
  2. iOS
  3. Other
I have a strange new problem that I found tonight when trying to transfer a VM from my Hack Pro to another machine. Between 2 to 6 GB into the file transfer my ethernet completely stops working. When I do a tail -F on system.log, I see an error that says AppleIntelE1000(Err): Detected Hardware Unit Hang and it repeats over and over until I reboot the machine. :banghead:

I've been using v3.0.4.1a up until now and it seemed ok but now any large file transfer kills my ethernet. I tried using v2.5.4d but the same thing happens.

The only thing that has changed on the system recently is updating to 10.9.4 but I am not convinced (yet) that it is the cause of the issue.

My rig specs are in my profile.

Anyone run into this before? Any help or ideas would be apprecaited.
 
I should note that everything works fine for small file transfers and regular use such as downloading files from the Internet. This problem only seems to occur when I am transferring large files such as VMs across the LAN to another machine. Both are on gigabit Ethernet. File transfer rate is around 880 to 900 mbps when the Ethernet stops working and I get the error message.

Any ideas?
 
I just tried v2.4.14 and I've been able to transfer the 60GB VM now twice successfully. It's too early to tell if things are "fixed" yet though.

Anyone else run into this before? If so, what did you do to fix it?

Anyone know what the differences would be between the v2.4.14 and the 3.0.4.1a versions of the driver are?

Any help is greatly appreciated.
 
In further testing, v2.4.14 seems to be working reliably for large file transfers. :geek:

Versions v3.0.4.1a and v2.5.4d give me a dead Ethernet port on large file transfers about 2 to 6 GB into the transfer. Why would the oldest of the three drivers be the stable one? :confused:

My Hack Pro has a 4770K, 32GB Kingston HyperX RAM, GTX 690, Asus Maximus VI Extreme w/BIOS 1402, 1 x PCI-E 1394b controller, 2 x PCI-E USB 3.0 Controllers, 512GB Samsung 840 Pro SSD, 4 x 3TB WD Red Hard Drives, LG DVD Burner, OS X 10.9.4 as the only OS. These specs are also in my profile.

I would still like to know what the differences are in the three drivers and if anyone else has run into this issue.

It would be great to get some opinions, ideas and advice on the matter... ;)
 
I have a similar problem with GA-X79-UP4 mobo. Working with big images saved on a server, after saving 7-8 times the ethernet connection stop working until reboot.
I tried every version of the kext without results (v2.4 doesn't work at all).

I think there is a big problem with the intel ethernet driver and maverick. Now I'm at a death point, with an unusable hack, hope someone can help
:rolleyes:

I opened a specific thread some hours ago
 
I have a similar problem with GA-X79-UP4 mobo. Working with big images saved on a server, after saving 7-8 times the ethernet connection stop working until reboot.
I tried every version of the kext without results (v2.4 doesn't work at all).

I think there is a big problem with the intel ethernet driver and maverick. Now I'm at a death point, with an unusable hack, hope someone can help
:rolleyes:

I opened a specific thread some hours ago

v2.4.14 has been stable for me so far under 10.9.4. Odd because I ran the v3.x driver just fine on 10.9.2 and 10.9.3. It would be great to know why the oldest driver rev is the only one that works, for me at least.
 
I am experiencing this too.

I've been able to just restart the port using these terminal commands instead of doing a full reboot:

sudo ifconfig en0 down
sudo ifconfig en0 up

I'm on 10.9.3, AppleIntelE1000e v3.0.4.
 
Try v2.4.14. On my rig, its the only version that doesnt hang the Ethernet port on 10.9.4
 
I'm trying right now v2.4.14 and I can see the network. The first time I did it I wasn't able to see the network at all.

Satay tuned!!! ;)
 
74 GB read, 74 GB written without errors in the console!!! :headbang:

I keep on testing!!! :)

Thank you very mouch
 
Status
Not open for further replies.
Back
Top