On Wed, 07 Apr 2010 18:18:16 +0100, Ben Hutchings wrote: > On Wed, 2010-04-07 at 11:45 -0400, Denis Laxalde wrote: > > Hi, > > > > On Sat, 03 Apr 2010 02:54:01 +0100, Ben Hutchings wrote: > > > On Tue, 2010-03-30 at 11:40 -0400, Denis Laxalde wrote: > > > > Package: linux-2.6 > > > > Version: 2.6.32-10 > > > > Severity: important > > > > > > > > Boot fails from time to time. A relevant dmesg is attached. > > > > Please let me know if you need more info. > > > > > > I don't think this has anything to do with the fuse module itself > > > since the 'oops' occurs while loading it. There seems to have > > > been some earlier memory corruption. Please try adding > > > 'blacklist radeon' to /etc/modprobe.d/blacklist. If that doesn't > > > make any difference, test the system's RAM with e.g. memtest86+. > > > > > > > Actually, this failure happened sporadically and has not occured > > for a week now (despite a daily shutdown) so it might be hard to > > investigate. Another failure just occured (dmesg attached). > > I also noticed an constant error related to radeon very early in the > > boot. AFAICT, nothing is recorded in any log. Is there any way to > > find more info about this ? > > First you'll have to tell use what the message is. Normally kernel > messages are saved to /var/log/dmesg (boot messages only) and > /var/log/messages (continually). > This error was about a missing firmware (5.484487 in the previous dmesg). Installing firware-linux-nonfree solved this issue. If boot failures occur again, I will give your previous advices a try and follow up. Thanks, Denis
Attachment:
bootfailure_2010-04-06_dmesg
Description: Binary data