hmm... perhaps this is a regression due to the Realtek 8168/8169 bug. Are you aware of this? There is a wiki article on resolving it. By first removing the 8168 ID from the 8169 driver, then recompiling a new version of the 8168 driver. Perhaps something has even removed the 8169 ID from the 8169 driver?! If you are not using the 8168 chipset in any way, then perhaps you should try downloading a new copy of the 8169 driver and replacing the old version in the diskless folder for your MD image?

hmm... perhaps this is a regression due to the Realtek 8168/8169 bug. Are you aware of this? There is a wiki article on resolving it. By first removing the 8168 ID from the 8169 driver, then recompiling a new version of the 8168 driver. Perhaps something has even removed the 8169 ID from the 8169 driver?! If you are not using the 8168 chipset in any way, then perhaps you should try downloading a new copy of the 8169 driver and replacing the old version in the diskless folder for your MD image?

Just to point out the obvious: 8139 != 8168/8169, the 8139 is a pretty old (and widespread) 10/100 mbit chipset and has been supported by the Linux kernel since like forever and a half.