|Summary:||Kudzu hangs on startup|
|Product:||[Fedora] Fedora||Reporter:||Jean-Marc Valin <jean-marc.valin>|
|Component:||kernel||Assignee:||Dave Jones <davej>|
|Status:||CLOSED DUPLICATE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2004-11-03 03:43:49 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Jean-Marc Valin 2004-05-28 01:49:59 UTC
Description of problem: When removing the CDROM drive from my laptop, Fedora Core 2 wouldn't boot because it was stuck in kudzu forever Version-Release number of selected component (if applicable): How reproducible: As soon as hardware is changed Steps to Reproduce: 1. Remove some hardware 2. Boot Fedora 3. Hang Actual results: Hang Expected results: No Hang Additional info: I have a Dell Latitude D600 laptop, I've never experienced that problem with other distros before. Right now, I have kudzu removed from rc5.d because otherwise it won't boot.
Comment 1 Bill Nottingham 2004-05-28 16:23:01 UTC
What happens if you strace it post-boot?
Comment 2 Jean-Marc Valin 2004-05-28 17:12:22 UTC
saw nothing in the /var/log/messages. Note that this happens with a custom kernel (2.6.5-mm6) which otherwise (no kudzu) runs fine.
Comment 3 Bill Nottingham 2004-05-28 17:58:23 UTC
So, post-boot, it works?
Comment 4 Jean-Marc Valin 2004-05-28 19:58:11 UTC
Post-boot is also hangs. When I do a ps, the thing that seems to hang is: /sbin/modprobe -q -r ohci1394 and the logs have: ieee1394: Initialized config rom entry `ip1394' Note that I do NOT have a firewire controller on this laptop.
Comment 5 Bill Nottingham 2004-05-28 21:16:06 UTC
This is a bug in the kernel firewire layer.
Comment 6 Jean-Marc Valin 2004-05-28 21:32:53 UTC
Note that I used exactly the same kernel (2.6.5-mm5) with FC1 with no such problem.
Comment 7 Arjan van de Ven 2004-05-29 08:13:57 UTC
Ehhh FC2 has no firewire so how can it be a kernel firewire layer problem ?
Comment 8 Jean-Marc Valin 2004-05-29 08:29:31 UTC
Dunno if that's relevent, but I think the problem only occurs with a custom kernel, not the default FC2 kernel. Still annoying though.