Bug#925944: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Hi, I found that the gnome-shell extension can not show the status of laptop cell charging. So I reinstalled the laptop-mode-tools, and changed the wired interface name from "eth0" to "enp0s31f6" in the file /etc/laptop-mode/conf.d/ethernet.conf as advice from Ritesh. Then, I reboot several times, it seems running OK. I will try more times. > -原始邮件- > 发件人: "Ritesh Raj Sarraf" > 发送时间: 2020-02-27 01:56:04 (星期四) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: 925...@bugs.debian.org > 主题: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name > maybe changed when reboot > > Control: serverity -1 important > > > I am lowering the severity as this is common reflection of problems > elsewhere disguising as a problem with laptop-mode-tools. > > > Couple of things to mention: > > * If you know of the persistent name for your interface, can you > populate that into the /etc/laptop-mode/conf.d/ethernet.conf and see if > that helps > > * From the logs that you've shared on the bug report, I'm lost. That > log is huge. laptop-mode-tools will apply power savings to ethernet > device. On boot, this happens quite early on. And probably that is > causing the problem. But I'd still like to see what holds the device so > long that NetworkManager fails to rename it. Does disabling the > `ethernet` module in laptop-mode-tools solve your problem ? If so, as a > workaround you can start with disabling it. And then try to investigate > what may be causing the device to remain busy for so long. > > * There's a valid bug report #925944, where a side-effect of enabling > power savings on the ethernet device results in NetworkManager not > considering the device. I am not sure how that should be solved because > how other tools (like NetworkManager, avahi etc) behave is beyond the > scope. But, if the integration of these tools do not work proper, > disabling one of the tools (like laptop-mode-tools) or a particular > hardware power savings (like ethernet module), could be a viable > option. > > > Coming up with an ideal default is challenging and I struggle to find a > balance. We do have /etc/laptop-mode/conf.d/board-specific/ . It is > documented in the manpage. > > > For the case of #925944, I think we should remove eth0 from the default > list. Because most devices these days have a unique persistent name and > it is best left to the user to find out the name and populate it in the > configuration file. That is what my upload today, 1.73.1-2 does. > > > On Wed, 2020-02-26 at 23:32 +0800, wg...@china.com wrote: > > OK, thank you very much! I will wait for all things are fine again! > > Thank you again! > > > > > > > > > -原始邮件----- > > > 发件人: "Michael Biebl" > > > 发送时间: 2020-02-26 23:09:22 (星期三) > > > 收件人: wg...@china.com, 952...@bugs.debian.org, > > > laptop-mode-to...@packages.debian.org > > > 抄送: > > > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe > > > changed when reboot > > > > > > Control: reassign -1 laptop-mode-tools > > > Control: retitle -1 lmt breaks network interface renaming > > > Control: severity -1 serious > > > > > > Am 26.02.20 um 16:01 schrieb wg...@china.com: > > > > As your recommendation, I removed the laptop-mode-tools, it seems > > > > that wired interface' name is correct for several boot. But if > > > > there is no laptop-mode-tools, how I using its function for > > > > saving power to laptop? > > > > > > Don't use laptop-mode-tools. The kernel does it sufficiently well > > > on > > > it's own these days. I'm not actually sure what business > > > laptop-mode-tools has with your network interfaces. > > > > > > I'm going to reassign this bug report to laptop-mode-tools and > > > bumping > > > the severity to RC. > > > > > > Michael > > > > > > > > > > > > > -- > Ritesh Raj Sarraf | http://people.debian.org/~rrs > Debian - The Universal Operating System
Bug#952506: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
> -原始邮件- > 发件人: "Ritesh Raj Sarraf" > 发送时间: 2020-02-27 01:56:04 (星期四) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: 925...@bugs.debian.org > 主题: Re: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name > maybe changed when reboot > > Control: serverity -1 important > > > I am lowering the severity as this is common reflection of problems > elsewhere disguising as a problem with laptop-mode-tools. > > > Couple of things to mention: > > * If you know of the persistent name for your interface, can you > populate that into the /etc/laptop-mode/conf.d/ethernet.conf and see if > that helps I think it is not useful because that the first name of wired interface is eth0, and systemd change it to enpXXX soon. So laptop may set the interface by eth0 or enpXXX. > > * From the logs that you've shared on the bug report, I'm lost. That > log is huge. laptop-mode-tools will apply power savings to ethernet > device. On boot, this happens quite early on. And probably that is > causing the problem. But I'd still like to see what holds the device so > long that NetworkManager fails to rename it. Does disabling the > `ethernet` module in laptop-mode-tools solve your problem ? If so, as a > workaround you can start with disabling it. And then try to investigate > what may be causing the device to remain busy for so long. > > * There's a valid bug report #925944, where a side-effect of enabling > power savings on the ethernet device results in NetworkManager not > considering the device. I am not sure how that should be solved because > how other tools (like NetworkManager, avahi etc) behave is beyond the > scope. But, if the integration of these tools do not work proper, > disabling one of the tools (like laptop-mode-tools) or a particular > hardware power savings (like ethernet module), could be a viable > option. > > > Coming up with an ideal default is challenging and I struggle to find a > balance. We do have /etc/laptop-mode/conf.d/board-specific/ . It is > documented in the manpage. > > > For the case of #925944, I think we should remove eth0 from the default > list. Because most devices these days have a unique persistent name and > it is best left to the user to find out the name and populate it in the > configuration file. That is what my upload today, 1.73.1-2 does. > > > On Wed, 2020-02-26 at 23:32 +0800, wg...@china.com wrote: > > OK, thank you very much! I will wait for all things are fine again! > > Thank you again! > > > > > > > > > -原始邮件- > > > 发件人: "Michael Biebl" > > > 发送时间: 2020-02-26 23:09:22 (星期三) > > > 收件人: wg...@china.com, 952...@bugs.debian.org, > > > laptop-mode-to...@packages.debian.org > > > 抄送: > > > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe > > > changed when reboot > > > > > > Control: reassign -1 laptop-mode-tools > > > Control: retitle -1 lmt breaks network interface renaming > > > Control: severity -1 serious > > > > > > Am 26.02.20 um 16:01 schrieb wg...@china.com: > > > > As your recommendation, I removed the laptop-mode-tools, it seems > > > > that wired interface' name is correct for several boot. But if > > > > there is no laptop-mode-tools, how I using its function for > > > > saving power to laptop? > > > > > > Don't use laptop-mode-tools. The kernel does it sufficiently well > > > on > > > it's own these days. I'm not actually sure what business > > > laptop-mode-tools has with your network interfaces. > > > > > > I'm going to reassign this bug report to laptop-mode-tools and > > > bumping > > > the severity to RC. > > > > > > Michael > > > > > > > > > > > > > -- > Ritesh Raj Sarraf | http://people.debian.org/~rrs > Debian - The Universal Operating System
Bug#925944: Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Control: serverity -1 important I am lowering the severity as this is common reflection of problems elsewhere disguising as a problem with laptop-mode-tools. Couple of things to mention: * If you know of the persistent name for your interface, can you populate that into the /etc/laptop-mode/conf.d/ethernet.conf and see if that helps * From the logs that you've shared on the bug report, I'm lost. That log is huge. laptop-mode-tools will apply power savings to ethernet device. On boot, this happens quite early on. And probably that is causing the problem. But I'd still like to see what holds the device so long that NetworkManager fails to rename it. Does disabling the `ethernet` module in laptop-mode-tools solve your problem ? If so, as a workaround you can start with disabling it. And then try to investigate what may be causing the device to remain busy for so long. * There's a valid bug report #925944, where a side-effect of enabling power savings on the ethernet device results in NetworkManager not considering the device. I am not sure how that should be solved because how other tools (like NetworkManager, avahi etc) behave is beyond the scope. But, if the integration of these tools do not work proper, disabling one of the tools (like laptop-mode-tools) or a particular hardware power savings (like ethernet module), could be a viable option. Coming up with an ideal default is challenging and I struggle to find a balance. We do have /etc/laptop-mode/conf.d/board-specific/ . It is documented in the manpage. For the case of #925944, I think we should remove eth0 from the default list. Because most devices these days have a unique persistent name and it is best left to the user to find out the name and populate it in the configuration file. That is what my upload today, 1.73.1-2 does. On Wed, 2020-02-26 at 23:32 +0800, wg...@china.com wrote: > OK, thank you very much! I will wait for all things are fine again! > Thank you again! > > > > > -原始邮件- > > 发件人: "Michael Biebl" > > 发送时间: 2020-02-26 23:09:22 (星期三) > > 收件人: wg...@china.com, 952...@bugs.debian.org, > > laptop-mode-to...@packages.debian.org > > 抄送: > > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe > > changed when reboot > > > > Control: reassign -1 laptop-mode-tools > > Control: retitle -1 lmt breaks network interface renaming > > Control: severity -1 serious > > > > Am 26.02.20 um 16:01 schrieb wg...@china.com: > > > As your recommendation, I removed the laptop-mode-tools, it seems > > > that wired interface' name is correct for several boot. But if > > > there is no laptop-mode-tools, how I using its function for > > > saving power to laptop? > > > > Don't use laptop-mode-tools. The kernel does it sufficiently well > > on > > it's own these days. I'm not actually sure what business > > laptop-mode-tools has with your network interfaces. > > > > I'm going to reassign this bug report to laptop-mode-tools and > > bumping > > the severity to RC. > > > > Michael > > > > > > > > -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
OK, thank you very much! I will wait for all things are fine again! Thank you again! > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 23:09:22 (星期三) > 收件人: wg...@china.com, 952...@bugs.debian.org, > laptop-mode-to...@packages.debian.org > 抄送: > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when > reboot > > Control: reassign -1 laptop-mode-tools > Control: retitle -1 lmt breaks network interface renaming > Control: severity -1 serious > > Am 26.02.20 um 16:01 schrieb wg...@china.com: > > As your recommendation, I removed the laptop-mode-tools, it seems that > > wired interface' name is correct for several boot. But if there is no > > laptop-mode-tools, how I using its function for saving power to laptop? > > Don't use laptop-mode-tools. The kernel does it sufficiently well on > it's own these days. I'm not actually sure what business > laptop-mode-tools has with your network interfaces. > > I'm going to reassign this bug report to laptop-mode-tools and bumping > the severity to RC. > > Michael > > > >
Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Control: reassign -1 laptop-mode-tools Control: retitle -1 lmt breaks network interface renaming Control: severity -1 serious Am 26.02.20 um 16:01 schrieb wg...@china.com: > As your recommendation, I removed the laptop-mode-tools, it seems that wired > interface' name is correct for several boot. But if there is no > laptop-mode-tools, how I using its function for saving power to laptop? Don't use laptop-mode-tools. The kernel does it sufficiently well on it's own these days. I'm not actually sure what business laptop-mode-tools has with your network interfaces. I'm going to reassign this bug report to laptop-mode-tools and bumping the severity to RC. Michael signature.asc Description: OpenPGP digital signature
Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
As your recommendation, I removed the laptop-mode-tools, it seems that wired interface' name is correct for several boot. But if there is no laptop-mode-tools, how I using its function for saving power to laptop? Thank you! > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 22:22:44 (星期三) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when > reboot > > Am 26.02.20 um 15:18 schrieb Michael Biebl: > > Am 26.02.20 um 14:40 schrieb wg...@china.com: > >> > >> The attachment file 111.txt is the ouput of command "journalctl -alb". > >> Thank you! > > > > Ok, thanks. > > Here's the relevant part of the log: > > > > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to rename > > network interface 2 from 'eth0' to 'enp0s31f6': Device or resource busy > > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to process > > device, ignoring: Device or resource busy > > > > So, systemd-udevd does attempt to rename the interface but something is > > trying to use the network interface before it has been renamed, which is > > why the rename fails. > > > > Now you need to find out what part of the system is using eth0 early in > > the boot process. > > Looking at the log, right before the rename happens, you have several > laptop-mode-tools calls. laptop-mode-tools does a lot of weird and > broken stuff. > My recommendation: apt purge laptop-mode-tools > and then try again. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925944 looks very much > related. > > Michael >
Bug#952506: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Yes, I have noticed it, but I don't know what thing is using eth0 early in the boot process. This bug did not exist several days ago. > -原始邮件- > 发件人: "Michael Biebl" > 发送时间: 2020-02-26 22:18:47 (星期三) > 收件人: wg...@china.com, 952...@bugs.debian.org > 抄送: > 主题: Re: Bug#952506: Re: Bug#952506: Wired interface name maybe changed when > reboot > > Am 26.02.20 um 14:40 schrieb wg...@china.com: > > > > The attachment file 111.txt is the ouput of command "journalctl -alb". > > Thank you! > > Ok, thanks. > Here's the relevant part of the log: > > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to rename > network interface 2 from 'eth0' to 'enp0s31f6': Device or resource busy > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to process > device, ignoring: Device or resource busy > > So, systemd-udevd does attempt to rename the interface but something is > trying to use the network interface before it has been renamed, which is > why the rename fails. > > Now you need to find out what part of the system is using eth0 early in > the boot process. > >
Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Am 26.02.20 um 15:18 schrieb Michael Biebl: > Am 26.02.20 um 14:40 schrieb wg...@china.com: >> >> The attachment file 111.txt is the ouput of command "journalctl -alb". Thank >> you! > > Ok, thanks. > Here's the relevant part of the log: > > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to rename > network interface 2 from 'eth0' to 'enp0s31f6': Device or resource busy > 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to process > device, ignoring: Device or resource busy > > So, systemd-udevd does attempt to rename the interface but something is > trying to use the network interface before it has been renamed, which is > why the rename fails. > > Now you need to find out what part of the system is using eth0 early in > the boot process. Looking at the log, right before the rename happens, you have several laptop-mode-tools calls. laptop-mode-tools does a lot of weird and broken stuff. My recommendation: apt purge laptop-mode-tools and then try again. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925944 looks very much related. Michael signature.asc Description: OpenPGP digital signature
Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Am 26.02.20 um 14:40 schrieb wg...@china.com: > > The attachment file 111.txt is the ouput of command "journalctl -alb". Thank > you! Ok, thanks. Here's the relevant part of the log: 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to rename network interface 2 from 'eth0' to 'enp0s31f6': Device or resource busy 2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to process device, ignoring: Device or resource busy So, systemd-udevd does attempt to rename the interface but something is trying to use the network interface before it has been renamed, which is why the rename fails. Now you need to find out what part of the system is using eth0 early in the boot process. signature.asc Description: OpenPGP digital signature
Bug#952506: Re: Bug#952506: Wired interface name maybe changed when reboot
Am 26.02.20 um 12:42 schrieb wg...@china.com: > > some of contents kern.log is attached. Thank you! > A verbose debug log (journalctl -alb) please from a failed boot as described in the wiki. signature.asc Description: OpenPGP digital signature
Bug#952506: Wired interface name maybe changed when reboot
Am 26.02.2020 um 05:26 schrieb wg...@china.com: > When the wired interface was be named enp0s31f6: > The journal logs as well please. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#952506: Wired interface name maybe changed when reboot
When the wired interface was be named enp0s31f6: udevadm info /sys/class/net/enp0s31f6 P: /devices/pci:00/:00:1f.6/net/enp0s31f6 L: 0 E: DEVPATH=/devices/pci:00/:00:1f.6/net/enp0s31f6 E: INTERFACE=enp0s31f6 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=3512520 E: ID_NET_NAMING_SCHEME=v243 E: ID_NET_NAME_MAC=enx482ae3154ae1 E: ID_OUI_FROM_DATABASE=Wistron InfoComm(Kunshan)Co.,Ltd. E: ID_NET_NAME_PATH=enp0s31f6 E: ID_BUS=pci E: ID_VENDOR_ID=0x8086 E: ID_MODEL_ID=0x15bb E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: ID_MODEL_FROM_DATABASE=Ethernet Connection (7) I219-LM E: ID_MM_CANDIDATE=1 E: ID_PATH=pci-:00:1f.6 E: ID_PATH_TAG=pci-_00_1f_6 E: ID_NET_DRIVER=e1000e E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: ID_NET_NAME=enp0s31f6 E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp0s31f6 /sys/subsystem/net/devices/enp0s31f6 E: TAGS=:systemd: When the wired interface was be named eth0: udevadm info /sys/class/net/eth0 P: /devices/pci:00/:00:1f.6/net/eth0 L: 0 E: DEVPATH=/devices/pci:00/:00:1f.6/net/eth0 E: INTERFACE=eth0 E: IFINDEX=2 E: SUBSYSTEM=net Best regards, Gulfstream
Bug#952506: Wired interface name maybe changed when reboot
Control: tags -1 + moreinfo unreproducible Am 25.02.20 um 07:42 schrieb gulfstream: > Package: systemd > Version: 244.3-1 > Severity: normal > > > Hi, the wired interface name maybe changed when root. Sometimes the wired > interface's name is "enp0s31f6", sometimes it is "eth0". I think it should be > "enp0s31f6", and it made the Network Manager can not manage the wired > interface anymore. Please provide a verbose debug log of a boot where the interface is named eth0 and a second log of a boot where the interface is named enp0s31f6. [1] has instructions how to do that. Please also include the output of udevadm info /sys/class/net/eth0 respectively udevadm info /sys/class/net/enp0s31f6 [1] https://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1 -> If You Can Get a Shell signature.asc Description: OpenPGP digital signature
Bug#952506: Wired interface name maybe changed when reboot
To the wired net interface, "eth0" was named is more often than new style "enp0s31f6".
Bug#952506: Wired interface name maybe changed when reboot
btw, the wireless interface is correct, its name is always "wlp0s20f3".
