Comment 40 for bug 1016556
Revision history for this message
| Brendan McLearie (bren-internode) wrote | #40 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@joseph
I have tested the 3.5 release candidte and can confirm that the same problem exists. the problem definitiely started between 2.6.35 and 2.6.38 and has been present in all Ubuntu and mainline kerels since.
The occurence of the panic is random, however always within the first minute or so of linux boot. Sometimes I get a panic screen, at other times its a reset with no panic, and I also get straight system freezes. I imagine it depends what code is running at the time as to whether the exception handler can acutally run and report the panic.
In the case of the 3.5 kernel, I am yet to receive a panic message - it alwyas simply freezes. This is currently occuring just after initialising USB drivers aqnd may be simply coincident on the fact that the USB initialisation takes an extended time before giving up on talking to my apple keyboard or logitech bluetooth mouse. I imagine installation of the rest of the architecture driver files would resolve this.
If 1394 is diabled in BIOS then 3.5 boots sucessfully through to the gnome login screen and seems happy (although no mouse, keyboard or network functional so I havent been able to test further).
I woud tend to just write the problem off and not use 1394, except however for the fact that it was totally rock solid up until 2.6.38 and having pursued this bug now for some time, I have a gut feel that there is some MB/kernel timing issue interacting with the problem. If that is indeed the case and it can be identified and fixed would be a good thing to have sorted out for the Ubuntu and linux projects generally.