Red Hat Bugzilla – Bug 700106
network interface renaming causes udev-settle to timeout
Last modified: 2012-08-07 15:10:07 EDT
Created attachment 495233 [details]
dmesg log with debug information
Description of problem:
sgallagh - 2011-04-26 15:07:01
This causes update causes a lot of boot issues for me. Previously my boot took ~12 seconds. With this update, it takes more than a minute before I am prompted for my filesystem crypto password, and then after that it takes another minute to reach the login screen. About one time in four, it freezes and never reaches the login screen.
lennart - 2011-04-27 00:43:42
sgallagh, can you please file a bug, and include the output of "dmesg" when booting with "systemd.log_level=debug" and "systemd.log_target=kmsg" after the boot finished?
Version-Release number of selected component (if applicable):
The time delay is consistent. I can't reproduce the total freeze consistently. I think I overstated the 25% though. It's less frequent than that.
Steps to Reproduce:
1. Boot with systemd-25 and an encrypted home dir (not encrypted root dir)
Much slower than version 24, occasionally hangs completely (or at least so long that it outlasts my patience.
Equivalent or better performance than version 24.
[Adding Harald to CC because of the udev-indicated problem]
The beginning of the log is lost. Next time please add "log_buf_len=1M".
udev-settle took a long time. It's somehow related to the network interface naming problem:
[ 5.429280] udev: renamed network interface eth1 to eth1-eth0
[ 95.637067] udevd-work: error changing net interface name eth1-eth0 to eth0: File exists
[ 95.699085] systemd: Job udev-settle.service/start finished, result=done
And there's also something wrong with your wireless card/driver:
[ 112.647958] iwl3945 0000:03:00.0: Microcode SW error detected. Restarting 0x82000008.
(This one looks like bug 683571.)
I see three network interfaces mentioned in the log:
- PCI 0000:00:19.0, Ethernet e1000e
- PCI 0000:03:00.0, WiFi iwl3945
- USB Ethernet ipheth (iPhone)
Is it reproducible with the iPhone disconnected?
Yupp, looks like a problem with some udev rule.
And the iphone-set-info tool is segfaulting:
[ 6.809499] iphone-set-info: segfault at 8 ip 000000389ce82971 sp 00007fffc49613c8 error 4 in libc-2.13.90.so[389ce00000+192000]
[ 6.810084] systemd: Received SIGCHLD from PID 561 (iphone-set-info).
[ 6.810121] systemd: Got SIGCHLD for process 561 (iphone-set-info)
[ 6.810184] systemd: Child 561 died (code=killed, status=11/SEGV)
The 1:30min wasted are the udev default timeout.
[ 95.637067] udevd-work: error changing net interface name eth1-eth0
yes, I could fix this with an udev update!
Stephen, any chance you could undo the negative bodhi voting of yours?
(In reply to comment #4)
> Stephen, any chance you could undo the negative bodhi voting of yours?
I'm a little confused why downgrading systemd back to version 24 didn't experience this problem, though.
I can't undo my negative vote, I can only change it to a positive vote. I'm not sure I'm ready to do this without an answer to the above.
Stephen, can't you downgrade it to neutral at least?
(In reply to comment #6)
> Stephen, can't you downgrade it to neutral at least?
Bodhi doesn't support this. Once karma is given, I can only toggle it from negative to positive (or vice-versa). I have switched it to positive now, since I had a chance to test this morning without the iPhone plugged in for charging.
It was just a coincidence I guess that I had it plugged in when testing -25 but not when using -24.
The problem is still exist.
Then it will be solve?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: