[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

PCIe debugging error messages - kern.log



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:
Jul 24 02:49:45 gaia kernel: [806292.204503]   TDH                  <8c>
Jul 24 02:49:45 gaia kernel: [806292.204504]   TDT                  <8f>
Jul 24 02:49:45 gaia kernel: [806292.204505]   next_to_use          <8f>
Jul 24 02:49:45 gaia kernel: [806292.204506]   next_to_clean        <8c>
Jul 24 02:49:45 gaia kernel: [806292.204508] buffer_info[next_to_clean]:
Jul 24 02:49:45 gaia kernel: [806292.204509]   time_stamp           <10c029ca3>
Jul 24 02:49:45 gaia kernel: [806292.204510]   next_to_watch        <8c>
Jul 24 02:49:45 gaia kernel: [806292.204511]   jiffies              <10c029dc2>
Jul 24 02:49:45 gaia kernel: [806292.204512]   next_to_watch.status <0>
Jul 24 02:49:45 gaia kernel: [806292.204513] MAC Status             <80383>
Jul 24 02:49:45 gaia kernel: [806292.204514] PHY Status             <792d>
Jul 24 02:49:45 gaia kernel: [806292.204516] PHY 1000BASE-T Status  <3800>
Jul 24 02:49:45 gaia kernel: [806292.204517] PHY Extended Status    <3000>
Jul 24 02:49:45 gaia kernel: [806292.204518] PCI Status             <10>


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? I've tried searching all of the log files in /var/log for the
dump information in case it gets logged somewhere else, but could not
find anything. I have checked to make sure that the debug message
level is set correctly:

Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off
        Supports Wake-on: pumbag
        Wake-on: g
        Current message level: 0x00002c01 (11265)
        Link detected: yes


Any help would be appreciated.

Thanks


Reply to: