#84 WOL Shutdown Reboot Error

closed
nobody
e1000e (107)
in-kernel_driver
5
2014-08-19
2011-05-25
Martin Owens
No

On the first wakeonlan event, the machine comes on and then shuts down perfectly. On the second wakeonlan event, the machine comes on and thereafter the machine starts up automatically when ever shutdown is attempted. The only remedy is to disconnect the power manually and wait for the power to drain from the ethernet device.

System: Ubuntu 10.10
Kernel: 2.6.35-28
Module: e1000e
Version: 1.0.2-k4
Device: 00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)
Subsystem: Hewlett-Packard Company Device 3048
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort-="">SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 46
Region 0: Memory at f0500000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f0525000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 1100 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0200c Data: 41c9
Capabilities: [e0] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: e1000e
Kernel modules: e1000e

Discussion

  • Martin Owens
    Martin Owens
    2011-06-16

    The BIOS was updated on all machines from 786G2 v1.09 to v2.01a (April 2011). This did not fix the issue.

    Attempting to use the trunk version of the e1000e device driver has failed to build so far, requesting assistance or binary.

     
  • Martin Owens
    Martin Owens
    2011-06-16

    This is a useful set of information that we almost always ask for when trying to solve a problem:

    * Summary of bug (one line):
    
    * Detailed description of bug:
    
    * Reproducible with steps:
    
    * Distribution and version:
    
    * Kernel version:
    
    * Intel Network Driver version (ethtool -i ethX):
    
    * Dmesg info with modprobe e1000 debug=21, or at least any relevant dmesg info:
    
    * 'ethtool <ethx>' output:
    
    * 'ethtool -i <ethx>' output:
    
    * 'ethtool -e <ethx>' output:
    
    * 'lspci -v -v' output:
    
    * 'cat /proc/interrupts' output:
    

    Also please see the file REPORTING-BUGS included in your kernel source. One possible location is here: http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

     
  • Tushar Dave
    Tushar Dave
    2011-06-16

    Sorry to hear that you have this issue. We have latest e1000e driver available at Sourceforge. Could you please give it a try?

     
  • Martin Owens
    Martin Owens
    2011-06-16

    Log Files

     
    Attachments
  • Martin Owens
    Martin Owens
    2011-06-16

    I can confirm that the issue still exists using the latest stable release e1000e 1.3.17-NAPI, I will attach another set of logs to help debug the issue.

     
  • Martin Owens
    Martin Owens
    2011-06-16

    This is a useful set of information that we almost always ask for when trying to solve a problem:

    * Summary of bug (one line):
    
    * Detailed description of bug:
    
    * Reproducible with steps:
    
    * Distribution and version:
    
    * Kernel version:
    
    * Intel Network Driver version (ethtool -i ethX):
    
    * Dmesg info with modprobe e1000 debug=21, or at least any relevant dmesg info:
    
    * 'ethtool <ethx>' output:
    
    * 'ethtool -i <ethx>' output:
    
    * 'ethtool -e <ethx>' output:
    
    * 'lspci -v -v' output:
    
    * 'cat /proc/interrupts' output:
    

    Also please see the file REPORTING-BUGS included in your kernel source. One possible location is here: http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

     
  • Martin Owens
    Martin Owens
    2011-06-16

    Log Files

     
  • Tushar Dave
    Tushar Dave
    2011-06-16

    @doctormo:
    In tarballs you attached, there is no ethtool log and there is no dmesg log.
    Can you please confirm and resend them?

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-07-09

    • status: open --> closed
    • Group: --> in-kernel_driver
     
  • Todd Fujinaka
    Todd Fujinaka
    2013-07-09

    Closing due to inactivity.