kernel-debug
 

I have a bug, which I reported to Redhat bugzilla. Everytime I unplug the dsl cable, my laptop crashes.

https://bugzilla.redhat.com/show_bug.cgi?id=781217

They said I might try to run the kernel-debug package. I don't know what that is or how to run it.

Any tips out there?

Thanks for reporting a bug. Run 'yum install kernel-debug' to install the debug version for your current kernel.

Thanks!

Will that cure this? Or what should I do? I really don't know what I should do with kernel-debug. Read the man page?

F 16 is the worst version of Fedora I ever installed! I never had so many crashes!

Installing the package provides kernel, config, initramfs. I only install it for debug (dump) purposes, but presumably it also creates the entry in the boot menu (never really looked ...). Simply boot it.

I would be surprised if it helped, but ya gotta try ...

No, it will not cure this. If you 'yum info kernel-debug' it displays the purpose of the package in short. As posted in the ticket they want the 'dmesg' output to begin with.


What kind of crashes? The reasons are important to know.

unplug the dsl cable, laptop crashes, or rather, freezes, only the power button can switch it off.

use an overhead projector, laptop won't switch off, screen stays alight.

I have posted what they asked for in bugzilla, but I am none the wiser, and the bug goes on! I have updated almost every day, hoping it would go away! This affects the laptop such that, the only way to get Fedora, or Ubuntu to boot after a crash, is to start Windows. Windows must do a basic reset of the hardware I presume. Then reboot and Linux works! This is a case of Windows saves Linux! I never use Windows, but I left it on the laptop just in case. Good thing I did!

No, you have not posted the 'dmesg' output running the debug kernel. That is what they asked for.

Ok, that wasn't clear to me.

Neither is 'we need to see the backtrace when it crashes.' What do they want?

See http://www.64k-tec.de/2010/10/gettin...-kernel-panic/ the "Post the panic" part for what a kernel panic will looks like. They'd like that output. (Also see http://www.mulix.org/lectures/kernel...el_oopsing.pdf for an example of what a kernel OOPS might involve but don't let yourself be intimidated by that as it's just an example.) If it's not a kernel issue they'll want you to move to the application level but let's not get ahead of things.

Thanks, I'll get the debug kernel running later today, then unplug the dsl cable, then post the dmesg again.