Hi,
Björn Döbel wrote:
Hmm. In this case, this would be a bug in Linux' 2.6.20.19 e1000 driver. Do you know if (and how) this has been fixed in some recent version? If so, a future update will fix this bug and you should use your workaround until then.
I’ve performed short investigation. It looks like the issue isn’t fixed in Linux 2.6.28.7 yet. But problem is known. It was reported to driver developers in maillist http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg00496.html. Unfortunately from mentioned thread it is not clear was the patch accepted by developers or not. So additionally I’ve checked is the patch applied to working kernel branch in git repo. It is not. So there is strong possibility that the patch was rejected. In this case I forced to use my patched version of e1000 driver.
Regards, Alexander Valitov