From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org
Subject: Re: 2.6.17-rc4-mm2
Date: Sun, 21 May 2006 15:29:25 -0700 [thread overview]
Message-ID: <4470E9C5.3080206@mbligh.org> (raw)
In-Reply-To: <20060521150259.3a1bdc9e.akpm@osdl.org>
Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@mbligh.org> wrote:
>
>>Panic on boot on 2-way PPC64
>> http://test.kernel.org/abat/32360/debug/console.log
>>
>> Bad page state in process 'idle'
>> page:c0000000010c3100 flags:0x0003300000000000 mapping:0000000000000000
>> mapcount:0 count:0
>> Trying to fix it up, but a reboot is needed
>> Backtrace:
>> Call Trace:
>> [C0000000004CBB70] [C00000000000EEE8] .show_stack+0x74/0x1b4 (unreliable)
>> [C0000000004CBC20] [C000000000098D04] .bad_page+0x80/0x134
>> [C0000000004CBCB0] [C000000000099F28] .__free_pages_ok+0x134/0x280
>> [C0000000004CBD70] [C00000000039C4F8] .free_all_bootmem_core+0x15c/0x320
>> [C0000000004CBE50] [C0000000003923AC] .mem_init+0xc0/0x294
>> [C0000000004CBEF0] [C000000000385700] .start_kernel+0x208/0x300
>> [C0000000004CBF90] [C000000000008594] .start_here_common+0x88/0x8c
>
>
> I dunno, Martin. I obviously need to resurrect the
> takes-seven-minutes-to-boot pseries machine here, but I need to get -mm3
Don't kill yourself over it - the blade seems to do it, but the p650
(8x) doesn't, so it may not help.
> out without Mel's patches to see how much that fixes. So if you could test
> -mm3 and if that fixes it then we have a likely culprit.
Sure, no problem. I suppose I should really make this thing do automated
bisection chopsearch ... I had that half-working when at IBM, but it'll
have to wait for the next generation now ... shouldn't take all that long.
M.
next prev parent reply other threads:[~2006-05-21 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 16:01 2.6.17-rc4-mm2 Martin J. Bligh
2006-05-21 22:02 ` 2.6.17-rc4-mm2 Andrew Morton
2006-05-21 22:29 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-21 0:58 2.6.17-rc4-mm2 Carl-Daniel Hailfinger
2006-05-21 1:32 ` 2.6.17-rc4-mm2 Andrew Morton
2006-05-21 3:00 ` 2.6.17-rc4-mm2 Roman Zippel
2006-05-21 15:07 ` 2.6.17-rc4-mm2 Serge E. Hallyn
2006-05-20 12:41 2.6.17-rc4-mm2 Andrew Morton
2006-05-20 16:24 ` 2.6.17-rc4-mm2 Jindrich Makovicka
2006-05-21 4:28 ` 2.6.17-rc4-mm2 Valdis.Kletnieks
2006-05-21 5:19 ` 2.6.17-rc4-mm2 James Morris
2006-05-21 5:38 ` 2.6.17-rc4-mm2 Valdis.Kletnieks
2006-05-21 15:30 ` 2.6.17-rc4-mm2 James Morris
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=4470E9C5.3080206@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--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