Red Hat Bugzilla – Bug 465684
Fedora 10 beta live cd crashes starting udev
Last modified: 2014-12-09 23:00:16 EST
Description of problem:
I downloaded and burned the Fedora 10 beta live cd. I popped into an old P3 Dell Inspiron 8000. The splash screen shows up, and I tell it to boot. It gets to the "Starting udev" message, then dumps a stack trace and goes into kernel panic (flashing caps and scroll lock lights). I used this same CD in a newer Inspiron 8600 (Pentium M), and it boots just fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get an old Dell laptop
2. Try to boot the F10 beta live cd in it
Haven't figured out yet how to provide the stack trace... if you know how to extract it from the frozen machine, let me know and I'll post it.
I downloaded the non-live install DVD. Install went fine, computer boots from HDD. Seems like it's just a live CD problem.
please add "modprobedebug" to the kernel command line, if you boot the live CD
I added modprobedebug to the kernel command line. The last module I can see before it dumps the stack and panics is yenta_socket. Another one right after it may be the actual cause, but it happens too fast after yenta_socket.
Let me know if you need more info, I'll try to help.
(In reply to comment #4)
> Haven't figured out yet how to provide the stack trace... if you know how to
> extract it from the frozen machine, let me know and I'll post it.
Take a picture with a digital camera and attach that.
or log the kernel messages via a serial console
The problem just got much weirder. I tried to log the message through a serial console, but I couldn't do it because it started booting properly. After trying several things, I realized that it only crashes when I DON'T add console=ttyS0,9600 to the kernel line in grub! If I use console=tty1 instead, it crashes. If I don't add anything, it crashes. If I add modprobedebug WITHOUT ttyS0, it crashes.
So the only way to get the output to you is what makes it not crash. Go figure. What would you suggest we do to get to the bottom of this now?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Did that happen with F10 as released too ?
Yes. Please also see bug 467556.
The "console=ttyS0,9600" workaround still works with the newest kernel, 220.127.116.11-170.2.5.fc10.i686.
*** Bug 467556 has been marked as a duplicate of this bug. ***
Could you add full dmesg output as _uncompressed text_ attachment to this bug ?
The output of "lspci -v" and "cat /proc/interrupts" would be useful as well.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.