Bug#830230: systemd disable wake-on-lan
Michael Biebl schrieb: > On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz > <n.sch...@rotorwerk.de> wrote: >> >> Christian Hofstaedtler schrieb: >>> * Norbert Schulz <n.sch...@rotorwerk.de> [160718 09:24]: >>>> Here are the required and some more information. >>> Thanks for following up on this. Unfortunately, I have no idea >>> either on what is happening here. >>> >> Is there any possibility to get some output if I send a wake-on-lan packet >> (with >> etherwake) to the ethernet card when the system is running? >> > > Is this still reproducible with an up-to-date stretch or sid system? > Sorry, until today I did not upgrade to stretch. Norbert Schulz ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#830230: systemd disable wake-on-lan
Christian Hofstaedtler schrieb: > * Norbert Schulz <n.sch...@rotorwerk.de> [160718 09:24]: >> Here are the required and some more information. > > Thanks for following up on this. Unfortunately, I have no idea > either on what is happening here. > Is there any possibility to get some output if I send a wake-on-lan packet (with etherwake) to the ethernet card when the system is running? Norbert ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#830230: systemd disable wake-on-lan
Christian Hofstaedtler schrieb: > * Norbert Schulz <n.sch...@rotorwerk.de> [160714 15:12]: >> output of ethtool eth0 with systemd >> Settings for eth0: > [..] >> MDI-X: on (auto) >> Wake-on: g >> >> output of ethtool eth0 with sysvinit >> Settings for eth0: > [..] >> MDI-X: off (auto) >> Wake-on: g > >> The difference between them is the MDI-X: value, with systemd it is 'on' and >> with sysvinit it is 'off'. > > Which network card and which driver is this? > Are you sure both boot options boot the same Linux kernel version? > (Which ones?) > > Please check dmesg if the driver in use prints helpful messages > about the link negotiation (some do, some don't), and if you see > them please report back what they say (for both systemd/sysvinit). > Here are the required and some more information. - sysvinit bootoption from /boot/grub/grub.cfg is menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (sysvinit)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-init-sysvinit-ed3c905d-d891-4706-ae9d-7df24fb8f1c8' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=ed3c905d-d891-4706-ae9d-7df24fb8f1c8 ro quiet init=/lib/sysvinit/init Here are some commands with there outputs. uname -a Linux backup-knecht 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux lspci |grep Ethernet 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection I use only one ethernet network card. dmesg |grep Intel [0.279960] smpboot: CPU0: Intel(R) Pentium(R) CPU G620 @ 2.60GHz (fam: 06, model: 2a, stepping: 07) [0.279991] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver. [0.671060] Intel P-state driver initializing. [0.671070] Intel pstate controlling: cpu 0 [0.671165] Intel pstate controlling: cpu 1 [0.704576] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [0.704578] e1000e: Copyright(c) 1999 - 2014 Intel Corporation. [0.981126] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection [1.094797] e1000e :02:00.0 eth1: Intel(R) PRO/1000 Network Connection [4.057498] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 dmesg |grep e1000 [0.704576] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [0.704578] e1000e: Copyright(c) 1999 - 2014 Intel Corporation. [0.704769] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [0.704793] e1000e :00:19.0: irq 42 for MSI/MSI-X [0.981119] e1000e :00:19.0 eth0: registered PHC clock [0.981124] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:25:90:57:7d:07 [0.981126] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection [0.981163] e1000e :00:19.0 eth0: MAC: 10, PHY: 11, PBA No: FF-0FF [0.982579] e1000e :02:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [0.982609] e1000e :02:00.0: irq 43 for MSI/MSI-X [0.982613] e1000e :02:00.0: irq 44 for MSI/MSI-X [0.982617] e1000e :02:00.0: irq 45 for MSI/MSI-X [1.094791] e1000e :02:00.0 eth1: registered PHC clock [1.094795] e1000e :02:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 00:25:90:57:7d:06 [1.094797] e1000e :02:00.0 eth1: Intel(R) PRO/1000 Network Connection [1.094882] e1000e :02:00.0 eth1: MAC: 3, PHY: 8, PBA No: FF-0FF [9.981318] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx lsmod |grep e1000 e1000e212128 0 ptp17692 1 e1000e end output with sysvinit --- The same with systemd. -- systemd bootoption from /boot/grub/grub.cfg is menuentry 'Debian GNU/Linux, mit Linux 3.16.0-4-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-advanced-ed3c905d-d891-4706-ae9d-7df24fb8f1c8' linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=ed3c905d-d891-4706-ae9d-7df24fb8f1c8 ro quiet uname -a Linux backup-knecht 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux lspci |grep Ethernet 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 05) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection dmesg |grep Intel [0.279027] smpboot: CPU0: Intel(R) Pentium(R) CPU G620 @ 2.60GHz (fam: 06, model: 2a, stepping: 07) [0.279058] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver. [0.669844] Intel P-state driver initializing. [0.669854] Intel pstate con
Bug#830230: systemd disable wake-on-lan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Biebl schrieb: > Am 14.07.2016 um 15:04 schrieb Norbert Schulz: > > Try that instead > > #!/bin/sh > mount -oremount,rw / > ethtool $iface > /ethtool.txt > mount -oremount,ro / > The output is as follow: Settings for eth0: 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: 1 Transceiver: internal Auto-negotiation: on MDI-X: Unknown (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: no There are some values which are 'Unknown' yet. Regards Norbert Schulz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAleHpToACgkQ6oHfnvuuOndSZACfZix83ma2CIWDRLv92qIIKD+N CjEAmQHWumuD842QJ+opnQNHn/A6fzC4 =SHe4 -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#830230: systemd disable wake-on-lan
Michael Biebl schrieb: > Control: tags -1 + moreinfo > > What's the output of > ethtool if you boot with systemd? What if you boot with > sysvinit. > output of ethtool eth0 with systemd Settings for eth0: 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: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes output of ethtool eth0 with sysvinit Settings for eth0: 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: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes The difference between them is the MDI-X: value, with systemd it is 'on' and with sysvinit it is 'off'. > Could you create a script /lib/systemd/system-shutdown/ethtool containing: > > #!/bin/sh > ethtool > > Mark it as executable and the run systemctl halt > > What's the output of the script? > There is no output of the script. No messages will be written to /var/log/syslog or /var/log/messages > Do you use systemd-networkd? No, not that I know of. regards Norbert Schulz ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#830230: systemd disable wake-on-lan
Package: systemd Version: 215-17+deb8u4 Severity: normal Dear Maintainer, after an upgrade from wheezy to jessie wake-on-lan does not work anymore. The output from ethtool shows, that wake-on-lan is enabled, but after a shutdown and sending a wake-on-lan signal from an other computer does not work. I found out, that I can boot jessie with the old sysvinit system from the grub menu. After booting jessie with the sysvinit system and shutdown the computer a wake-on-lan from an other computer works. The systemd makes some thing which the old sysvinit not make. I know that I should send some detailed information. Please let me know which information is needed and in which system (systemd or sysvinit) the computer shell boot. Best regards Norbert Schulz -- Package-specific info: -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u4 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2+deb8u1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1+deb8u1+b1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u4 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u4 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.20-0+deb8u1 ii libpam-systemd 215-17+deb8u4 Versions of packages systemd suggests: pn systemd-ui -- no debconf information 0 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/ssh.service /etc/systemd/system/sshd.service ==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/cron.service ==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service ==> /var/lib/systemd/deb-systemd-helper-enabled/hibernate.target.wants/anacron-resume.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/ssh.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/atd.service ==> /var/lib/systemd/deb-systemd-helper-enabled/paths.target.wants/acpid.path <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.path.dsh-also <== /etc/systemd/system/paths.target.wants/acpid.path ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/acpid.service ==> /var/lib/systemd/deb-systemd-helper-enabled/suspend.target.wants/anacron-resume.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/hybrid-sleep.target.wants/anacron-resume.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/anacron.service ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/anacron-resume.service.dsh-also <== /etc/systemd/system/suspend.target.wants/anacron-resume.service /etc/systemd/system/hibernate.target.wants/anacron-resume.service /etc/systemd/system/hybrid-sleep.target.wants/anacron-resume.service ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/acpid.socket # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added a
