Red Hat Bugzilla – Bug 458901
cannot start udev - computer cannot start with 2.6.26 kernels
Last modified: 2008-09-30 20:21:51 EDT
Created attachment 314168 [details]
Description of problem:
My computer freezes.
All kernels from 2.6.26 tree seems to "lock" themselves. They all stop after "Starting udev:". The dmesg doesn't show any oopses or other problems. The only change in comparison to 2.6.25 is "ACPI: Core revision 20080321"
In order to go further i have to keep the backspace key pressed. then everything works normal. if i let the key everything stops again. For example
in konsole, after i type a command and press enter nothing happens until i press and keep backspace pressed.
Everything works fine only with the backspace pressed.
The problem doesn't exist with 2.6.25 kernels.
Version-Release number of selected component (if applicable):
is the kernel on aspire 5051
Steps to Reproduce:
Everything freezes until the backspace is pressed
make it work
Created attachment 314182 [details]
With acpi=off the system boots normally (as far as possible). I'll try another acpi options and report later.
Actually I need to keep pressed at least one key for it to work flawlesly. Not just the backspace. MAybe irq problems with keyboard?
Maybe the problem is not acpi related. the dmesg doesn't show any problems and the kernel loads fine. Maybe it is something in fedora that waits for a key stroke in order to procede. Maybe DCOP. I tested (a while ago on FC8) 2.6.27-0.173.rc0.git11.fc8.i686 (ACPI Corerevision 20080609)and everything was fine. Version 2.6.27-0.254.rc3.fc9.i686 freezes.
Any Ideas? OS or Kernel?
I patched the 184.108.40.206 kernel with acpi-test-20080609-rc8 from http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.26/acpi-test-20080609-2.6.26-rc8.diff.gz but the problem is still there.
Kernels that work:
220.127.116.11-108.fc9 and previous
Kernels that don't work:
So there should be something between 0.173.rc0.git11 and 0.254.rc3 that doesn't work for me.
Anyone, any ideas?
I kept trying the other kernels to see if they hang. This is what I found (from the 2.6.27 series)
up to 2.6.27-0.238.rc2.fc9.i686 everything is fine but with 0.238 I have no display. Just a black screen. I tried removing the noeuvo + drm patch but it didn't help. applyung acpica-20080608 doesn't resolve the problem too.
So i decided to try the 18.104.22.168-14-fc9 with udevdebug - virtually millions of messages were shown on the screen and nothing else.
I changed the wait_for_queue() in /sbin/start_udev to return 0 after local ret=0 and this helped me to overcome the freeze at startup. but lots of devices weren't working after this.
My assumption is that udev isn't initializing something properly, or it is blocked by selinux (see the dmesg-debug-udev) and therefore it waits indefinitely at startup.
Created attachment 314815 [details]
The udev works fine with the 22.214.171.124-108 kernel. Why shouldn't it do the same with 2.6.26?
I read on phoronix and other forums that the TTM was replaced by GEM in the kernel. At the same time D. Airlie has merged many drm patches in the fedora kernel. And this is the common thing between the 126.96.36.199 kernel and the 2.6.27-0.284.rc4.git6.fc10. With the latest I see "starting udev" and then I got black and white stips on the display. Nothing else can be seen or done.
Therefore I think not the udev but something in the kernel conserning the modesetting on my radeon RS482 is causing the problem.It all started with the kernel update.
Let's see what the drm-devels think.
kernel-188.8.131.52-27.fc9 has been submitted as an update for Fedora 9.
Created attachment 315492 [details]
This patch fixes the problem. I tried it with 184.108.40.206-17.fc9 and 2.6.27-0.290.rc5.fc10. Everything is fine. Maybe it hould be integrated in the 2.6.27 branch. The bug is resolved.
kernel-220.127.116.11-29.fc9 has been submitted as an update for Fedora 9.
kernel-18.104.22.168-29.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
kernel-22.214.171.124-29.fc9.i686 hangs at "Starting UDEV:"
older kernels work just fine.
What else should I include about system that would help?
kernel-126.96.36.199-29.fc9.i686 hangs after decompression
my 188.8.131.52-29 started hanging after i installed vmware server 2. could be a coincidence, but...