Re: Blue screen of death

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2010-07-30 at 14:48 -0700, suvayu ali wrote:
> On 30 July 2010 14:31, Alex <mysqlstudent@xxxxxxxxx> wrote:
> > Hi,
> >
> >> I talked to the plymouth maintainer and he said this is a known bug; I
> >> don't know if the fix is in F13 yet but let me explain what's going on:
> >>
> >> You've got two bugs. One is a kernel panic. The other is that when the
> >> kernel is panicking, rather than showing useful debug information, it is
> >
> > Good to know, thanks. It's just good to know there is a confirmed bug,
> > so I'm confident it is being worked on, and a fix will be available in
> > the near future.
> >
> 
> >From what I understood from Máirín's response, the bug in plymouth is
> worked upon. But there is no way to tell the reason for the kernel
> panic. I think you should still try to investigate the reason for
> that. I am sorry I don't have any suggestions for you to try. Luckily
> I have never faced a kernel panic myself. :(

You're right, Suyayu - the bug that's being worked on is the plymouth
bug (well actually, I think it's a kernel bug, but it displays plymouth
so plymouth is the visible part.) But that won't fix the core problem -
the kernel panic - because we don't yet know what's causing Alex's
system to panic in the first place.

I think kernel panics are usually because of hardware issues, device
driver issues, or a genuine kernel bug (but I think the latter is by far
more rare.) Do you have any hardware that might be suspect, Alex? Maybe
a RAM module you recently swapped into the machine? 

One tool that might be useful is called kdump. It's part of Fedora and
it loads a second uncrashed kernel to capture data from the crashed
kernel to help figure out what's going on. There's some instructions on
how to use kdump in the Fedora wiki:

http://fedoraproject.org/wiki/Kernel/kdump

I would imagine if the output of running kdump after triggering a crash
doesn't indicate the problem in an obvious way (e.g., might be
obvious-ish if there was mention of the brand name of a piece of hw
you're aware of in the output), I think the output would certainly make
for a good bug report.

Hope this helps,
~m


-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux