I suspect that this bug is due to incorrect initialisation of RTL8101E or RTL8102E chips. This was supposed to be fixed upstream in 2.6.32 and was backported to 2.6.26-21.
There are currently 4 submitters to this bug: Carlos Fonseca <[email protected]> using RTL8101E/RTL8102E chip not yet known whether this is fixed Victor Pablos Ceruelo <[email protected]> using RTL8101E/RTL8102E chip reported in #528362 that this is not fixed in 2.6.32 Jakub Zeman <[email protected]> using D945GCLF2 motherboard which I think has an RTL8101E chip not yet known whether this is fixed Marcel Meckel <[email protected]> using unknown hardware reported as fixed in 2.6.26-21 Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig.
signature.asc
Description: This is a digitally signed message part
