From: Mandar Thite <mandarthite@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: NULL ptr dereference in __remove_hrtimer()
Date: Mon, 26 Jan 2009 08:47:16 +0530 [thread overview]
Message-ID: <8e2adebc0901251917q2b84dd2ag17254a92bd526262@mail.gmail.com> (raw)
In-Reply-To: <8e2adebc0901251915r7dc19c6bn1c9c8ad737039894@mail.gmail.com>
Hi,
I am really very sorry, I forgot to say, my kernel version is 2.6.26,
and patched with ADEOS ipipe. I know, I should put this query in ADEOS
mailing list, but I think, here I may get some good kickstart.
On Sun, Jan 25, 2009 at 11:32 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Sun, 2009-01-25 at 15:48 +0530, Mandar Thite wrote:
>> Hello everyone,
>>
>> I am trying to boot Linux kernel on OMAP5912 CPU(arch/arm/mach-omap1)
>> containing ARM926 core.
>> I have configured my Linux kernel to run in tickless mode. In the
>> final steps of booting, kernel is encountering " NULL pointer
>> dereference " in the function " rb_erase() " called from " __remove_hrtimer() ".
>> Following is the backtrace log emitted by the kernel.
>>
>> Backtrace:
>> [<c012ed1c>] (rb_erase+0x0/0x358) from [<c0053f48>] (__remove_hrtimer+0x88/0x94)
>> r9:00000080 r8:c0285530 r7:00000000 r6:00000001 r5:c0285530
>> r4:c02a6298
>> [<c0053ec0>] (__remove_hrtimer+0x0/0x94) from [<c00548a8>] (hrtimer_start+0x74/0x108)
r7:00000006 r6:02625a00 r5:00000000 r4:2d4cae00
>> [<c0054834>] (hrtimer_start+0x0/0x108) from [<c005af18>](tick_nohz_stop_sched_tick+0x2bc/0x3a4)
>> [<c005ac5c>] (tick_nohz_stop_sched_tick+0x0/0x3a4) from [<c0023318>](cpu_idle+0x38/0x60)
>> [<c00232e0>] (cpu_idle+0x0/0x60) from [<c01f7d58>] (rest_init+0x58/0x6c)
r5:c001cdc4 r4:c02bc754
>> [<c01f7d00>] (rest_init+0x0/0x6c) from [<c0008ad0>] (start_kernel+0x244/0x290)
>>[<c000888c>] (start_kernel+0x0/0x290) from [<10008034>] (0x10008034)
r6:c001cdc0 r5:c029af88 r4:00053175
>> Code: e3580001 01a04005 189dabf0 ea000082 (e5941008)
>> ---[ end trace b0a66fe3e48abdda ]---
>> Kernel panic - not syncing: Attempted to kill the idle task!
>>
>> What I understand is, address of nonexistent node is passed to rb_erase()?
>> Can anybody please direct me, how to investigate further into this problem?
>
> For one, provide the kernel version you're trying to boot. Secondly,
> it's much easier to read backtraces when they're not mangled.
>
>
prev parent reply other threads:[~2009-01-26 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e2adebc0901250211m218b5c35i7153b0a6548c2079@mail.gmail.com>
2009-01-25 10:18 ` Mandar Thite
2009-01-25 18:02 ` Peter Zijlstra
[not found] ` <8e2adebc0901251915r7dc19c6bn1c9c8ad737039894@mail.gmail.com>
2009-01-26 3:17 ` Mandar Thite [this message]
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=8e2adebc0901251917q2b84dd2ag17254a92bd526262@mail.gmail.com \
--to=mandarthite@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®