From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: Can't create pid_1 cachep
Date: Wed, 22 Aug 2007 19:22:20 +0530 [thread overview]
Message-ID: <46CC3F94.4050609@linux.vnet.ibm.com> (raw)
Hi Andrew,
Following Kernel panic is raised while booting up with 2.6.23-rc3-mm1
kernel.
============================================================
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Initializing HighMem for node 0 (00038000:001fbe00)
Initializing HighMem for node 1 (00200000:003fbe00)
Initializing HighMem for node 2 (00400000:005fbe00)
Initializing HighMem for node 3 (00600000:007fbe00)
Memory: 32480436k/33554432k available (2146k kernel code, 278984k
reserved, 1203k data, 216k init, 31842304k highmem)
virtual kernel memory layout:
fixmap : 0xffe1a000 - 0xfffff000 (1940 kB)
pkmap : 0xffc00000 - 0xffe00000 (2048 kB)
vmalloc : 0xf8800000 - 0xffbfe000 ( 115 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc134c000 - 0xc1382000 ( 216 kB)
.data : 0xc12189e1 - 0xc1345758 (1203 kB)
.text : 0xc1000000 - 0xc12189e1 (2146 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=16, CPUs=16, Nodes=16
Calibrating delay using timer specific routine.. 1401.55 BogoMIPS
(lpj=2803105)
Kernel panic - not syncing: Can't create pid_1 cachep
Thanks & Regards,
Kamalesh Babulal.
next reply other threads:[~2007-08-22 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 13:52 Kamalesh Babulal [this message]
2007-08-22 14:17 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: Can't create pid_1 cachep Kamalesh Babulal
2007-08-22 14:40 ` Pavel Emelyanov
2007-08-22 20:57 ` Kamalesh Babulal
2007-08-22 21:25 ` Andrew Morton
2007-08-22 21:25 ` Andrew Morton
2007-08-23 9:12 ` Kamalesh Babulal
2007-08-23 9:26 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CC3F94.4050609@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.