Multibeast 6.4.1: AppleIntelE1000e.kext v3.1.0 bug and fix

[mucksavage]

I can confirm I have the issue on my Z87X-UD4H. Usually copying big files kills the ethernet and I have to deactivate/reactivate it to get it back.

 

[ueer3fc]

I can confirm this bug as well. Thanks for the solution!

When copying large files, AppleIntelE1000e just hangs with the following errors without this fix:

2014-12-27 12:59:37.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:37.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:37.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:38.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:38.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:39.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:39.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:39.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:40.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:40.000 kernel[0]: e1000_tx_map: failed to getphysicalsegment.
2014-12-27 12:59:41.000 kernel[0]: AppleIntelE1000e(Err): Detected Hardware Unit Hang:
2014-12-27 12:59:41.000 kernel[0]: TDH <ff>
2014-12-27 12:59:41.000 kernel[0]: TDT <d1>
2014-12-27 12:59:41.000 kernel[0]: next_to_use <d1>
2014-12-27 12:59:41.000 kernel[0]: next_to_clean <fa>
2014-12-27 12:59:41.000 kernel[0]: buffer_info[next_to_clean]:
2014-12-27 12:59:41.000 kernel[0]: time_stamp <6464f>
2014-12-27 12:59:41.000 kernel[0]: next_to_watch <ff>
2014-12-27 12:59:41.000 kernel[0]: next_to_watch.status <0>
2014-12-27 12:59:41.000 kernel[0]: MAC Status <80083>
2014-12-27 12:59:41.000 kernel[0]: PHY Status <796d>
2014-12-27 12:59:41.000 kernel[0]: PHY 1000BASE-T Status <3c00>
2014-12-27 12:59:41.000 kernel[0]: PHY Extended Status <3000>
2014-12-27 12:59:41.000 kernel[0]: PCI Status <10>

 

[mucksavage]

Haven't seen any updates on this issue, but I rebuilt a file server with that same main board, and had the same issues. Using the fix didn't help, however downgrading to the 2.4.14 driver seems to have worked so far. I have pushed time machine backups from all three of my machines at the same time and haven't seen any errors pop up in the log.

Pushing the wife's 3.5 terabytes of photos now, we'll see if it holds up

 

[MacMan]

hnack hasn't officially fixed this in a new build but has it incorporated into the latest source.

This fix will be in MultiBeast 7.2 which will be released after Yosemite 10.10.2.

If this is a major issue in Mavericks, I can do a MultiBeast 6.5.1 release.

 

[mucksavage]

Thanks for the response! I am using Yosemite across the board now, but saw this same issue on my Mavericks build.

Appreciate the work on everything!

 

[redbaritone]

I think I might have this problem, because internet speed tests are about ten times slower than on other computers in the house. However, where do I find the correct error log, to see if it's happening to me. I'm in Yosemite with an ASUS Z97I-Plus. Thanks!

 

[mucksavage]

Just open up Console, you will be able to see the error in the "All Messages" heading.

 

[rad-we]

You can also change the setting in OSX, check my signature.