From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, qcui@redhat.com,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel
Date: Sun, 29 May 2011 23:19:48 -0700 [thread overview]
Message-ID: <20110529231948.e1439ce5.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-36192-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 30 May 2011 02:38:33 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=36192
>
> Summary: Kernel panic when boot the 2.6.39+ kernel based off of
> 2.6.32 kernel
> Product: Memory Management
> Version: 2.5
> Kernel Version: 2.6.39+
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Page Allocator
> AssignedTo: akpm@linux-foundation.org
> ReportedBy: qcui@redhat.com
> Regression: Yes
>
>
> Created an attachment (id=60012)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=60012)
> kernel panic console output
>
> When I updated the kernel from 2.6.32 to 2.6.39+ on a server with AMD
> Magny-Cours CPU, the server can not boot the 2.6.39+ kernel successfully. The
> console ouput showed 'Kernel panic - not syncing: Attempted to kill the idle
> task!' I have tried to set the kernel parameter idle=poll in the grub file. It
> still failed to reboot due to the same error. But it can reboot successfully on
> the server with Intel CPU. The full console output is attached.
>
> Steps to reproduce:
> 1. install the 2.6.32 kernel
> 2. compile and install the kernel 2.6.39+
> 3. reboot
>
hm, this is not good. Might be memcg-related?
> BUG: unable to handle kernel paging request at 0000000000001c08
> IP: [<ffffffff811076cc>] __alloc_pages_nodemask+0x7c/0x1f0
> PGD 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> CPU 0
> Modules linked in:
>
> Pid: 0, comm: swapper Not tainted 2.6.39+ #1 AMD DRACHMA/DRACHMA
> RIP: 0010:[<ffffffff811076cc>] [<ffffffff811076cc>] __alloc_pages_nodemask+0x7c/0x1f0
> RSP: 0000:ffffffff81a01e48 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000008 RDI: 00000000000002d0
> RBP: ffffffff81a01ea8 R08: ffffffff81c03680 R09: 0000000000000000
> R10: 0000000000000001 R11: 0000000000000001 R12: 00000000000002d0
> R13: 0000000000001c00 R14: ffffffff81a01fa8 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffff880437800000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000001c08 CR3: 0000000001a03000 CR4: 00000000000006b0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process swapper (pid: 0, threadinfo ffffffff81a00000, task ffffffff81a0b020)
> Stack:
> 0000000000000000 0000000000000000 ffffffff81a01eb8 000002d000000008
> ffffffff00000020 ffffffff81a01ec8 ffffffff81a01e88 0000000000000008
> 0000000000100000 0000000000000000 ffffffff81a01fa8 0000000000093cf0
> Call Trace:
> [<ffffffff81107d7f>] alloc_pages_exact_nid+0x5f/0xc0
> [<ffffffff814b2dea>] alloc_page_cgroup+0x2a/0x80
> [<ffffffff814b2ece>] init_section_page_cgroup+0x8e/0x110
> [<ffffffff81c4a2f1>] page_cgroup_init+0x6e/0xa7
> [<ffffffff81c22de4>] start_kernel+0x2ae/0x366
> [<ffffffff81c22346>] x86_64_start_reservations+0x131/0x135
> [<ffffffff81c2244d>] x86_64_start_kernel+0x103/0x112
> Code: e0 08 83 f8 01 44 89 e0 19 db c1 e8 13 f7 d3 83 e0 01 83 e3 02 09 c3 8b 05 22 e5 af 00 44 21 e0 a8 10 89 45 bc 0f 85 c4 00 00 00
> 83 7d 08 00 0f 84 dd 00 00 00 65 4c 8b 34 25 c0 cc 00 00 41
> RIP [<ffffffff811076cc>] __alloc_pages_nodemask+0x7c/0x1f0
> RSP <ffffffff81a01e48>
> CR2: 0000000000001c08
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2011-05-30 6:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-36192-10286@https.bugzilla.kernel.org/>
2011-05-30 6:19 ` Andrew Morton [this message]
2011-05-30 7:01 ` [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel KAMEZAWA Hiroyuki
2011-05-30 7:12 ` Minchan Kim
2011-05-30 7:29 ` KAMEZAWA Hiroyuki
2011-05-30 7:54 ` KAMEZAWA Hiroyuki
2011-05-30 8:51 ` KAMEZAWA Hiroyuki
2011-06-06 12:54 ` Johannes Weiner
2011-06-06 21:45 ` Andrew Morton
2011-06-06 23:45 ` KAMEZAWA Hiroyuki
2011-06-07 8:45 ` Mel Gorman
2011-06-07 8:43 ` KAMEZAWA Hiroyuki
2011-06-07 9:09 ` Mel Gorman
2011-06-07 9:33 ` KAMEZAWA Hiroyuki
2011-06-07 10:18 ` Mel Gorman
2011-06-07 23:40 ` KAMEZAWA Hiroyuki
2011-06-08 0:42 ` KAMEZAWA Hiroyuki
2011-06-08 7:43 ` Mel Gorman
2011-06-08 8:45 ` KAMEZAWA Hiroyuki
2011-06-08 9:03 ` Mel Gorman
2011-06-08 10:15 ` Johannes Weiner
2011-06-09 1:04 ` KAMEZAWA Hiroyuki
2011-06-09 1:42 ` [PATCH] [BUGFIX] Avoid getting nid from invalid struct page at page_cgroup allocation (as " KAMEZAWA Hiroyuki
2011-06-07 0:57 ` KAMEZAWA Hiroyuki
2011-06-07 7:51 ` Johannes Weiner
2011-06-07 7:55 ` KAMEZAWA Hiroyuki
2011-06-07 10:26 ` Johannes Weiner
2011-06-07 23:45 ` KAMEZAWA Hiroyuki
2011-06-08 9:33 ` Johannes Weiner
2011-06-07 9:03 ` Mel Gorman
2011-06-07 9:06 ` KAMEZAWA Hiroyuki
2011-06-07 10:13 ` Mel Gorman
2011-06-07 8:37 ` Mel Gorman
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=20110529231948.e1439ce5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=qcui@redhat.com \
/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.