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" <bi...@debian.org> > 发送时间: 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. > >
