Results 1 to 7 of 7

Thread: Ethernet dead after wake from sleep

  1. #1

    Exclamation Ethernet dead after wake from sleep

    Leap 42.1
    Desktop computer with wired network connection

    Computer running fine all day. Put to sleep for an hour. Upon wake, Firefox reported that it had crashed. Could not restart Firefox. Rebooted computer and ethernet is dead, no network connection.

    Network status lamp glows on network swtich while starting and through GRUB screen. Goes dark during boot.

    YAST Network Settings says "Ethernet Connection I217-V (Not Connected)

    systemctl status wickedd-auto4.service results in:

    Loaded: loaded (usr/lib/systemd/system/wickedd-auto4.service; enabled)
    Active: failed (Result: exit-code) since Wed 2016-10-19 21:10:56 EDT
    Process: 1021 ExecStart=/usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground (code=exited, status=1/FAILURE)


    What happened? How to fix?

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,378
    Blog Entries
    1

    Default Re: Ethernet dead after wake from sleep

    Quote Originally Posted by SUSEtoad View Post
    Leap 42.1
    Desktop computer with wired network connection

    Computer running fine all day. Put to sleep for an hour. Upon wake, Firefox reported that it had crashed. Could not restart Firefox. Rebooted computer and ethernet is dead, no network connection.



    Network status lamp glows on network swtich while starting and through GRUB screen. Goes dark during boot.
    Have you checked the cable/termination?

    What is reported by the following? (assuming eth0 for interface)
    Code:
    /usr/sbin/ethtool eth0

  3. #3

    Lightbulb Re: Ethernet dead after wake from sleep

    Have tried different Ethernet cable. Have tried different port on swtich. Have tried rebooting switch. Have tried rebooting router.

    ethtool eth0 reports:

    Supported ports: [ TP ]
    Supported link modes: 10baseT/Half 10baseT/Full
    100baseT/Half 100baseT/Full
    1000baseT/Full
    Supported pause frame use : No
    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: Unknown!
    Duplex: Unknown! (255)
    Port: Twisted Pair
    PHYAD: 2
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown (auto)
    Supports Wake-on: pumbg
    Wake-on: d
    Current message level: 0x000000007 (7)
    drv probe link
    Link detected: no

  4. #4

    Default Re: Ethernet dead after wake from sleep

    The following appears in boot.log

    Started wicked DHCPv4 supplicant service
    FAILED Failed to start wicked DHVPv6 supplicant service
    FAILED Failed to start wicked AutoIPv4 supplicant service

    ...

    FAILED Failed to start wicked managed network interface

  5. #5

    Default Re: Ethernet dead after wake from sleep

    wicked show config

    wicked: Unable to open /usr/share/wicked/schema/types.xml: Stale file handle
    wicked: cannot parse schema file "/usr/share/wicked/schema/types.xml"
    wicked: invalid schema xml for schema file "/usr/share/wicked/schema/wicked.xml"
    wicked: Cannot create dbus xml schema: error in schema definition
    wicked: Giving up.

  6. #6

    Default Re: Ethernet dead after wake from sleep

    Solution was to copy corrupted file from backup.

    Now to find a way to delete the "Stale file handle" file. Normal ways don't work.

    Feeling so confident knowing that waking my computer from sleep can result in corrupted files.

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,378
    Blog Entries
    1

    Default Re: Ethernet dead after wake from sleep

    Interesting find. Haven't come across that before.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •