On Mon, 2012-08-06 at 15:24 -0500, Andrew Peng wrote: > I've been working with the Intel E1000 development team in trying to > find the cause of a hardware hang in my kern.log. They suggested > contacting the Debian User list for extra help, whom suggested that I > ask the Kernel list to see if I could get any insight. > > This is the error in my kern.log: > > Jul 24 02:49:45 gaia kernel: [806292.204500] e1000e 0000:02:00.0: > eth1: Detected Hardware Unit Hang: [...] > One of the steps to find the cause of this is to enable extended error > reporting by using ethtool: > sudo ethtool -s eth1 msglvl 0x2c01 > > This will tell the driver to dump extended debugging (a PCIe Ring > Dump) info to the kernel log with another error is detected. However, > after enabling this extended logging, the next time an error occurs, I > still don't get the debug dump in the kern.log. I get basically the > same info as above. > > Is there anything Debian specific that would cause this to not get > logged? [...]
The ring dump is only shown in case the driver resets the chip, and it doesn't do that in the case of Hardware Unit Hang. So I think whichever developer told you this was confused. Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure.
signature.asc
Description: This is a digitally signed message part
