Red Hat Bugzilla – Bug 391701
kernel crash on boot in firewire module
Last modified: 2008-02-21 12:24:38 EST
Usually the kernel boots fine (I boot from an external firewire drive), but
today I got a kernel crash on boot. After a poweroff/on everything went fine.
I'm using Fedora 8 with stock 18.104.22.168-42 kernel.
I have attached the screen shot with the trace. Let me know if this is enough or
further info is needed.
Created attachment 264661 [details]
screen shot of the kernel trace
Please try the latest stable Fedora 8 kernel, it has numerous firewire fixes.
Stefan Richter pointed out in bug# 428554 that this error looks very much like
my screenshot https://bugzilla.redhat.com/attachment.cgi?id=291491 in comment #3
of that bug.
The latest F8 stable is 22.214.171.124-85, which also has issues with my firewire drive.
It would be interesting to know if you have issues with that one as well Alex,
or if this error ever repeated itself for you at all.
I think I have only seen this problem once - the "orb reply timed out" was a
much more frequent problem for me. I have since switched to the rawhide kernels
(currently using 2.6.24-0.83.rc5.fc9), and the crash hasn't shown up yet with
them, and the orb timeouts seem to be fixed as well. I can downgrade to latest
f8 2.6.23 kernel, if you want, and see if the problem re-occurs, but it seems
like a quite rare one for me at least.
(In reply to comment #3)
> The latest F8 stable is 126.96.36.199-85, which also has issues with my firewire drive.
The F8 kernel to try out would be 188.8.131.52-106.fc8 or later, which is where a
significant amount of the firewire updates/fixes went in. I don't believe
anything that new is in updates or updates-testing yet though, so you have to
pull from koji at the moment. The latest build as of this writing can be found here:
Nb: see the tail end of bug 238606, I think we'll have the orb reply timeout
thing fixed shortly. :)
Re-assigning to you as per triage page.
Should be resolved in the latest updates-testing kernel (and the latest updates
kernel, iirc). Please reopen if its still a problem.