On 11/21/2011 10:07 AM, Stefan Priebe wrote:

quoted

You are going to need to clarify some things since as far as I know we
never released a v3.0.8 driver, and the kernel in the bug below is a
version 2.6.40.8 which sounds more like a modified and possibly
backported Linux kernel since as far as I know Linus never released a
2.6.40 kernel version.

Sorry that my description was so inaccurate. I'm talking about a
vanilla v3.0.8 linux kernel. Just renamed to 2.6.40.8.

quoted

In order to be able to assist you we will need some additional
information.  What Linux distro are your running?  Do you have the
latest updates from them?  Also have you tried running the latest
out-of-tree driver we provide at e1000.sf.net in order to verify if the
same issue occurs with that driver?

Linux Distri is Debian Lenny but we're running a self compiled vanilla
3.0.X kernel. I haven't tried to use the up2date e1000.sf.net driver
as 3.0 is a long time supported kernel by greg - so all needed fixes
should be backported or at least send to stable@ so that greg can have
a look at them.

Thanks!

Stefan

Stefan,

It would be useful if you could try the latest driver from e1000.sf.net
just to verify  if this is a bug in the upstream kernel or if it is also
present in our e1000.sf.net.driver.  This way we can figure out if this
is an issue where a patch wasn't pushed into the stable kernel or if it
is an issue that still exists in our latest release.

Also could you provide us with the part number you are currently using. 
If you could provide us with the device ID for the part via lspci we can
start narrowing down the root cause for the issue as currently we don't
have any information about what hardware you are experiencing this issue on.

Thanks,

Alex