Machine: linux centos 5.4 with 2 hdds and raid 5 (yes, 3rd disk missing).
Situation:
all running fine (3rd disk missing)
then a power off (system shut down itself when battery power ended).
machine not coming back
message on screen:
photo of it: http://postimage.org/image/9jc16755h/ (not allowed to post photo here, new user)
typed text:
Memory for crash kernel (0x0 to 0x0) notwithin permi
I recently installed Ubuntu 10.4 onto an older computer. Upon trying to boot off the live CD, my monitor would go "out of range" (screen would turn black and display a hardware error message "out of range").
I am currently running Ubuntu 12.10.
Both in 12.04, and 12.10, I have been noticing random Kernel Panics that seem to happen only when I am not using the laptop.
I went to follow the guide for getting the crash dump, but after a simulated crash (using sysreq c), /var/crash is empty.
I did a dumb thing... I forgot that Ubuntu 10.04 (Lucid) switched to Grub2 which puts a ton of *.mod files (kernel modules) in /boot/grub. I thought they were soundtrack files put there erroneously and moved them. Needless to say, the next reboot was traumatic. I was presented with something I had no memory of ever seeing...
No, it's not the same as that guy's issue (not using intel graphics + can also reproduce the issue without X running).Haven't really gotten very far with it yet (besides that I can now make it crash instantly by using a script to fill up my memory, disabled swap for now). The issue only happens when running kernel 3.3.4; downgrading to 3.3.3 (or older obviously) makes it go away.
Hello,I try to use kdump and crash to analyse kernel failures and I have troubles to analyse core dump with crash:$ crash -s -S /boot/Syste... [by jerome42]
Is there a way I can edit the Grub Menu so I can make grub list Damn Small Linux and then have it proceed to boot DSL from a memory stick (NOT Flashrdive). Where do I begin? I'm stuck on the "root to" entry.
# This entry links to the DSL installation on my 2GB Memory stick
title Damn Small Linux
root (hd1,0)
Best_ wrote:I thought it was my hardware that was failing...That's exactly what I thought because the crash is hard and totally unpredictable, and then I remembered this thread (and finally caught a backtrace showing that the X "lockups" I've been having for several days were really kernel panics on "illegal opcode", my system was attempting some i/o on a jfs filesyst
I foolishly installed the newest kernel update... now I can't boot anymore.
Once I rebooted, grub presented me it's friendly console.
Email this page
