From: ZhouPing Liu <zliu@redhat.com>
To: "Peter Zijlstra" <a.p.zijlstra@chello.nl>,
Andrea Arcangeli <aarcange@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Hillf Danton <dhillf@gmail.com>,
hi3766691@gmail.com, LKML <linux-kernel@vger.kernel.org>
Subject: Kernel panic - not syncing: Attempted to kill the idle task!
Date: Sat, 09 Jun 2012 01:13:23 +0800 [thread overview]
Message-ID: <4FD232B3.7040502@redhat.com> (raw)
hi,
kernel panic on mainline(commit: 48d212a2eecaca) with a large system, which
has 120Gb RAM & 8 numa nodes:
... [cut here] ...
[ 3.404017] Call Trace:
[ 3.404553] [<ffffffff810afd19>] find_busiest_group+0x39/0x4b0
[ 3.406188] [<ffffffff810b0295>] load_balance+0x105/0xa50
[ 3.407444] [<ffffffff810ce2ed>] ? trace_hardirqs_off+0xd/0x10
[ 3.408695] [<ffffffff810aa1cf>] ? local_clock+0x6f/0x80
[ 3.409789] [<ffffffff810b11b0>] idle_balance+0x130/0x2d0
[ 3.410879] [<ffffffff810b10d0>] ? idle_balance+0x50/0x2d0
[ 3.411996] [<ffffffff8167f340>] __schedule+0x910/0xa00
[ 3.413204] [<ffffffff8167f769>] schedule+0x29/0x70
[ 3.414324] [<ffffffff8102352f>] cpu_idle+0x12f/0x140
[ 3.415433] [<ffffffff81667765>] start_secondary+0x262/0x264
[ 3.416763] Code: 44 8b bd 7c ff ff ff 45 85 ff 0f 85 30 02 00 00 48
8b bd 48 ff ff ff 48 8b 4f 10 4c 8b 45 98 8b 71 04 31 d2 4c 89 c0 48 c1
e0 0a <48> f7 f6 48 8b 75 a0 48 85 f6 48 89 c7 49 89 c1 48 89 45 90 0f
[ 3.420335] RIP [<ffffffff810af93b>] update_sd_lb_stats+0x27b/0x620
[ 3.421664] RSP <ffff88041922fb48>
[ 3.422473] ---[ end trace 04b848dd1c06d585 ]---
[ 3.423472] Kernel panic - not syncing: Attempted to kill the idle task!
whole console log is here:
http://www.sanweiying.org/download/debug_kernel/kernel_panic_48d212a2eecaca
and config file is
http://www.sanweiying.org/download/debug_kernel/config_48d212a2eecaca
and I have tested different branches, more details is available in
https://lkml.org/lkml/2012/6/6/704
here I do a simple summary:
a), mainline,
v3.4: no such panic
b), mainline, v3.5-rc1(commit: 48d212a2eecaca), yes
c), Andrea's tree, autonuma15 yes
d), tip/master(commit:b2f5ce55c4e68370) no such panic
let me know if you need any info.
Thanks,
Zhouping
next reply other threads:[~2012-06-08 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 17:13 ZhouPing Liu [this message]
2012-06-08 18:46 ` Kernel panic - not syncing: Attempted to kill the idle task! Peter Zijlstra
2012-06-09 1:38 ` Zhouping Liu
2012-06-11 13:27 ` Peter Zijlstra
2012-06-11 13:51 ` Borislav Petkov
2012-06-12 3:54 ` Zhouping Liu
2012-06-12 6:39 ` Zhouping Liu
2012-06-12 8:49 ` Peter Zijlstra
[not found] ` <CA+55aFw=akW7B+vRkQRMojnP6_b1YXdKpNEjQ2EyBHcTe2_XLw@mail.gmail.com>
2012-06-12 10:27 ` Peter Zijlstra
2012-06-12 11:08 ` Peter Zijlstra
2012-06-12 16:45 ` Peter Zijlstra
[not found] <1158989060.155090.1306033067946.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-05-22 3:37 ` Qiannan Cui
2011-05-22 23:43 ` Minchan Kim
2011-05-23 10:08 ` Qiannan Cui
2011-05-23 15:46 ` Minchan Kim
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=4FD232B3.7040502@redhat.com \
--to=zliu@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=dhillf@gmail.com \
--cc=hi3766691@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.