suse 11 kernel panic

[tingwei liu]

On Tue, Jul 24, 2012 at 12:39 PM, Mulyadi Santosa
<mulyadi.santosa at gmail.com> wrote:
> Hi....
>
> On Tue, Jul 24, 2012 at 6:38 AM, tingwei liu <tingw.liu at gmail.com> wrote:
>> Suse 11 SP1 kernel panic。
>>
>> I can't debug it without debuginfo. Who can give me a link of sels
>> 2.6.32.12-0.7.default.debug or give some advise.
>
> Better just report it to the SuSE novell team about this bug...so that
> they are aware of this bug....
>
> But anyway, see below...
>
>> kernel: [3077010.856280] BUG: unable to handle kernel NULL pointer
>> dereference at 0000000000000008
>
> OK, sounds like nasty pointer bug....it could be anything...even exploit...
>
>> kernel: [3077010.856291] IP: [<ffffffff81046958>] find_busiest_group+0x348/0x8b0
>
> hmm, maybe a  scheduler bug...
>
> just asking, how many core you have?
24 cores
>
>> kernel: [3077010.856375] Pid: 5762, comm: program_t Not tainted
>> 2.6.32.12-0.7-default #1 ProLiant DL380 G7
>
> program_t??? never heard of it...is it your user space application?
Right, This is my user space application.
>
>> kernel: [3077010.856438] Stack:
>> kernel: [3077010.856441]  0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000
>> kernel: [3077010.856445] <0> 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000
>> kernel: [3077010.856450] <0> 0000000000000000 0000000000000000
>> 0000000000000000 0000000000000000
>
> seems like your stack is "wiped".... if that's so, it's almost
> impossible to get valid stack trace in my opinion...
User space program can affect kernel stack? I thought this is a kernel bug!
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com

Thanks!