LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices



Reply
 
Search this Thread
Old 01-27-2010, 05:01 AM   #1
casualzone
Member
 
Registered: Jan 2010
Posts: 189

Rep: Reputation: 15
Memory for crash kernel (0x0 to 0x0) notwithin permissible range


I installed CentOS 5.4.. I saw this message:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range

Is it ok?
I google around it said that it is a known issue and harmless.


I installed CentOS 5.2 before. It was ok. Kernel is 2.6.18 too. Just wonder why

Kernel version:
Linux phot1-nec4 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
 
Old 01-27-2010, 05:19 AM   #2
Agrouf
Senior Member
 
Registered: Sep 2005
Location: France
Distribution: LFS
Posts: 1,591

Rep: Reputation: 79
Hello,
I have this message too on my critical production servers since one year at least. No problem here. Red Hat said it is harmless.
 
Old 11-15-2010, 02:00 AM   #3
Fracker
Member
 
Registered: Mar 2009
Posts: 77

Rep: Reputation: 0
Well, one of my critical server is doing anything after this message, what should i do?
 
Old 12-06-2011, 09:24 PM   #4
DucQuoc
LQ Newbie
 
Registered: Dec 2011
Posts: 5

Rep: Reputation: Disabled
I'm not sure if I should resurrect the topic, but for the ppl who met the similar problem to Fracker you can try either:

* Edit the GRUB boot menu to remove the "quiet" option in the line "kernel ..." , save it.
* If it's running inside a VM, enable the "APIC support" (IO-APIC) from the configuration.

Then next reboot may solve the issue .

hth,
Quote:
Originally Posted by Fracker View Post
Well, one of my critical server is doing anything after this message, what should i do?
 
Old 12-07-2011, 12:24 AM   #5
devUnix
Member
 
Registered: Oct 2010
Location: Bengaluru, India
Distribution: RHEL 5.1 on My PC, & SunOS / Sun Solaris, RHEL, SuSe, Debian, FreeBSD and other Linux flavors @ Work
Posts: 557

Rep: Reputation: 46
During installation if Dump Memory/Storage is created then the message would not show up. It is ignorable.
 
Old 12-07-2011, 01:20 PM   #6
Passmossis
LQ Newbie
 
Registered: Jul 2011
Location: USA
Distribution: RHEL 6.5
Posts: 28

Rep: Reputation: 2
I've done some research on this message as I have it on all of my RHEL 5.X systems. This is only an error if you are utilizing kdump, as kdump would need a sizable amount of allocated memory. If you are not using kdump, this alert does not apply to you.

A large number of people have spent time, including myself, researching this issue only to find it is not an issue for them.


Reference information:
https://bugzilla.redhat.com/show_bug.cgi?id=431584

I hope this helps.
 
Old 12-07-2011, 08:30 PM   #7
grim76
Member
 
Registered: Jun 2007
Distribution: Debian, SLES, Ubuntu
Posts: 283

Rep: Reputation: 47
This error is in regard to the crashkernel=xxx@yyy parameter on the grub boot line.

You can fix this by editing the line and changing it to crashkernel=128M or crashkernel=256M Those values have worked well in the environment I am in.

Also you will want to configure /etc/kdump.conf and uncomment the line that works for your configuration. In the event that you do not want kdump you can remove the crashkernel value from the grub line without issue.
 
  


Reply


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
memory for crash kernel not within permissible range jchidalgo Linux - General 1 02-09-2010 05:34 PM
Console fonts question: 0x0 = 0xC4? Mol_Bolom Programming 0 04-22-2009 01:05 AM
Sata1.00 : exception Emask 0x0 sAct 0x0.... Hitboxx Fedora 8 01-30-2009 01:10 AM
DWARF2 unwinder stuck at 0x0 rocket357 Linux - Security 4 04-15-2007 04:11 AM


All times are GMT -5. The time now is 06:01 AM.

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