none
Client fails to wake-on-LAN with USB-Ethernet adapter RRS feed

  • Question

  • I have Win8 and WinRT HCK clients that fail to wake during the CHAOS and Sleep jobs on a HID device/touchpad. I'm thinking that it's because the USB-Ethernet adapter loses power during sleep which prevents wake from the controller. Has anyone else seen this? Thanks.
    Friday, April 26, 2013 12:19 AM

All replies

  • Hi,

    Please verify your power-savings options on your Clients. HCK is supposed to configure them before running tests but sometimes it misses options.

    Eventually give us the content of you logs (if there are logs) or the error related to the test (probably "test failed due to unexpected reboot" or something like that).

    Regards.

    Friday, April 26, 2013 10:53 AM
  • Thanks ingenico. I verified all power management options are good. The logs just say failed due to unexpected reboot from restarting the system to recover from sleep.

    Monday, April 29, 2013 11:59 PM
  • Hi,

    Have you already passed the Sleep and PNP test ?

    This error happens when you either reboot your Test Client unexpectedly during a test or when you get a BSOD and you have to reboot manually.

    Did you disable Windows Update during tests ? It can reboot your Machine if updates are to install.

    Regards.

    Tuesday, April 30, 2013 8:04 AM
  • No, the problem still exists. The manual restart is required because the system never wakes from sleep during the CHAOS and Sleep jobs. Windows Update is disabled. Thanks for the information.
    Tuesday, April 30, 2013 8:14 PM
  • Hi,

    Check the below information once:

    Task Cancelled Because of an Unexpected Reboot error indicates:

    1. There was a bugcheck during the test run, OR
    2. The system rebooted when sleep tests tried to put the machine to a sleep state.

    In this case, you should run tests with a kernel debugger attached if you believe the reason for the failure is a bugcheck. If the system bugchecks while it is connected to a kernel debugger, it will automatically break into the debugger.

    System event logs also help with investigating “Unexpected Reboot” failures. These logs can be accessed from Event Viewer (Windows Logs->System). You should do the following:

    1. Clear existing system event logs from Event Viewer on the test system, so only logs during the test run appear.
    2. Re-run the test that repro’s “Unexpected Reboot” error.
    3. Save the system event logs.

    For Event Logs:

    Go to Control panel --> System and Security-->Administration Tools-->Event Viewer(Double click on that)

    In left Windows Logs-->System.


    Yesubabu Gude

    • Proposed as answer by Yesubabu Gude Thursday, May 23, 2013 12:22 PM
    Wednesday, May 1, 2013 10:29 AM
  • Hi,

    Refer the below link once..

    https://sysdev.microsoft.com/en-us/Hardware/EC/FilterDetail.aspx?id=1400


    Yesubabu Gude

    Tuesday, May 21, 2013 5:50 AM
  • Yesubabu,

    Thanks for your help.

    The final conclusion from our analysis is that the problem stems from the client systems' power management hardware and/or firmware. The faulty systems were prototype machines, not production. After trying two more prototype systems, we finally got a production system that worked. The driver under test was not at fault.


    CR

    Tuesday, November 5, 2013 5:13 PM