On Mon, 30 Jul 2012 08:43:56 -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:
(...) I've read the report you posted at "e1000-devel" mailing list. > 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. (...) It could be something specific to the kernel module in use (e1000e). Consider sending this question also at "debian-kernel" where Debian kernel hackers use to be. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jv6bns$ltk$1...@dough.gmane.org
