Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Linux - Kernel This forum is for all discussion relating to the Linux kernel.


  Search this Thread
Old 01-05-2009, 11:55 PM   #1
LQ Newbie
Registered: Jan 2009
Posts: 1

Rep: Reputation: 0
kexec crash kernel oddity/insanity

I've been getting this horribly annoying kernel panic in X recently, so I decided to use kdump/kexec to try and get at my vmcore.

I've set up kexec as per the instructions in /Documentation/kdump/kdump.txt

I've enabled sysrq in both the kernel, AND, in the /etc/sysctl.conf

The system responds to sysrq-C when I'm in the console and before startx, which properly loads the dump kernel and I can get access to my /proc/vmcore

However, when I'm in X (after startx), sysrq-c does NOT load up the crash kernel, and INSTEAD responds by hanging my system (NO blinking capslock though).

I'm on a Intel Core 2 Duo, 64-bit, 2GB of memory, NVIDIA QUADRO FX 570M, and note that my CONFIG_PHYSICAL_START is 0x200000, NOT 0x100000, (I wasn't sure if this should be changed as the default was 0x200000). But this shouldn't matter because the kernel is RELOCATABLE(=y)

I've attached my:

.config :
lspci :
lsmod :
dmesg :
grub.conf :

my kexec command is "sudo kexec -p /usr/src/linux-2.6.28-gentoo/arch/x86/boot/bzImage --append=root=/dev/sda3 1 irqpoll maxcpus=1 reset_devices"

Please help.
Old 08-10-2009, 10:42 AM   #2
Registered: Apr 2005
Location: BC
Distribution: Centos
Posts: 34

Rep: Reputation: 16
kexec vmcore


Are you still facing the same issue? I also faced similar issue but working around with the values of crashkernel=x@y solved my issue.

Now I am facing issues in reading the /proc/vmcore ... /dev/oldmem.
Can you please share how to read the memory using /proc/vmcore interface?

or any application program?

Like if I want to read a perticual page fram number etc.

Moreover, if you have any idea regarding reading data to 32 bit user space from 64 bit kernel space.
Old 08-12-2009, 11:35 AM   #3
Registered: Oct 2007
Location: Eastern Seaboard
Distribution: CentOS
Posts: 162

Rep: Reputation: 15

How did you resolve the issues with the crashkernel setting? I am currently having an issue with that myself but havent been able to resolve them. I have set crashkernel=128M@64M in my grub.conf file but kdump still complains it hasnt been set when restarting kdump.
Old 08-12-2009, 11:53 AM   #4
Registered: Apr 2005
Location: BC
Distribution: Centos
Posts: 34

Rep: Reputation: 16

Please make sure that you have set kexec in your .config file.


and then remember to pass crashkernl=Y@X into your primary kernel. Moreover, please check the .config file of the kdum in /etc.

Currently I am facing issues with generating the /proc/vmcore file. Its getting generated but of zero size. and working on it.

Hope it helps.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
How do I hibernate Slackware? Also: 2.6.27 kexec kernel hibernation? Romanus81 Slackware 8 10-27-2008 11:26 AM
compiling kernel oddity - in function Furlinastis Linux - Software 2 01-06-2007 08:42 PM
RH9.0 Kernel rebuild oddity Paul_assheton Linux - General 4 06-02-2004 04:18 PM
More Kernel Rebuild Trouble --- insanity looms. mudelf Linux - General 1 10-09-2003 06:56 PM
kernel compile insanity... xdrainox Slackware 5 09-30-2003 07:02 PM > Forums > Linux Forums > Linux - Software > Linux - Kernel

All times are GMT -5. The time now is 03:27 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration