From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: kernel panic while using alloc_bootmem()
Date: Wed, 23 Jul 2008 00:22:26 -0700 (PDT) [thread overview]
Message-ID: <18605311.post@talk.nabble.com> (raw)
Hi all ,
I am getting kernel panic while allocating memory at boottime in my driver
which is linked to the kernel following is the code snapshort from driver
init module .
buf_area = alloc_bootmem_low(0x900000);
if(buf_area == NULL)
{
printk(" ################## Memory allocation failed \n");
return -1;
}
following is the error message :-
###################### bootmem driver init call start #################
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 5 [#1]
Modules linked in:
CPU: 0
PC is at _find_first_zero_bit_le+0xc/0x2c
LR is at __alloc_bootmem_core+0x138/0x334
pc : [<c0152b58>] lr : [<c00132d0>] Not tainted
sp : c043df38 ip : 00000000 fp : c043df74
r10: 00000000 r9 : 00000900 r8 : 00900000
r7 : 00000001 r6 : 00000020 r5 : c02fa9e0 r4 : 000fffff
r3 : 00007700 r2 : 00000000 r1 : 00007700 r0 : 00000000
Flags: nZcv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C5387F
Table: 80004000 DAC: 00000017
Process swapper (pid: 1, stack limit = 0xc043c250)
Stack: (0xc043df38 to 0xc043e000)
df20: c018195c
ffffffe0
df40: 00007700 00000000 c043df84 c02fa9e0 00900000 00000000 00000020
00000000
df60: 00000000 00000000 c043df9c c043df78 c0013538 c00131a4 ffffffff
c043df94
df80: c001e504 c001dfd8 c043c000 00000001 c043dfac c043dfa0 c001ae98
c0013500
dfa0: c043dff4 c043dfb0 c00200c8 c001ae80 00000000 00000000 c002002c
c0041eb8
dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
dfe0: 00000000 00000000 00000000 c043dff8 c0041eb8 c0020038 c021c9dc
c021cb50
Backtrace:
[<c0013198>] (__alloc_bootmem_core+0x0/0x334) from [<c0013538>]
(__alloc_bootmem_low+0x44/0x94)
[<c00134f4>] (__alloc_bootmem_low+0x0/0x94) from [<c001ae98>]
(FlukeDriverInit+0x24/0x7c)
r7 = 00000001 r6 = C043C000 r5 = C001DFD8 r4 = C001E504
[<c001ae74>] (FlukeDriverInit+0x0/0x7c) from [<c00200c8>] (init+0x9c/0x27c)
[<c002002c>] (init+0x0/0x27c) from [<c0041eb8>] (do_exit+0x0/0x93c)
r7 = 00000000 r6 = 00000000 r5 = 00000000 r4 = 00000000
Code: e49df008 e3310000 0a000006 e3a02000 (e7d031a2)
<0>Kernel panic - not syncing: Attempted to kill init!
---Misbah <><
--
View this message in context: http://www.nabble.com/kernel-panic-while-using-alloc_bootmem%28%29-tp18605311p18605311.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
reply other threads:[~2008-07-23 7:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=18605311.post@talk.nabble.com \
--to=misbah_khan@engineer.com \
--cc=linuxppc-embedded@ozlabs.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.