From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.0-rc1: powerpc hangs at Kernel virtual memory layout
Date: Wed, 01 Jun 2011 10:25:42 +1000 [thread overview]
Message-ID: <1306887942.29297.10.camel@pasglop> (raw)
In-Reply-To: <alpine.DEB.2.01.1105311644010.21697@trent.utfs.org>
On Tue, 2011-05-31 at 16:50 -0700, Christian Kujau wrote:
> Hi,
>
> trying to boot 3.0-rc1 on powerpc32 only progresses until:
>
> > Kernel virtual memory layout:
> > * 0xfffcf000..0xfffff000 : fixmap
>
> And then the system hangs, does not respond to keyboard (sysrq does not
> seem to work on this PowerBook G4). But after a while the system reboots
> itself, so I guess the machine panicked but did not print anything on the
> screen.
>
> Full messages (picture), config & (working) dmesg:
>
> http://nerdbynature.de/bits/3.0-rc1/
>
> I'm currently trying to bisect this, so far I have:
Hrm, I had it working on a pair of powerbooks yesterday. Can you try
something like "udbg-immortal" on your kernel command line to see if
that makes a difference in the output ?
Cheers,
Ben.
> ----------------------
> git bisect start
> # good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39
> git bisect good 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf
> # bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1
> git bisect bad 55922c9d1b84b89cb946c777fddccb3247e7df2c
> # bad: [c44dead70a841d90ddc01968012f323c33217c9e] Merge branch 'usb-next'
> of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> git bisect bad c44dead70a841d90ddc01968012f323c33217c9e
> # bad: [d93515611bbc70c2fe4db232e5feb448ed8e4cc9] macvlan: fix panic if
> lowerdev in a bond
> git bisect bad d93515611bbc70c2fe4db232e5feb448ed8e4cc9
> ----------------------
>
> Any ideas?
>
> Thanks,
> Christian.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux ppc dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: 3.0-rc1: powerpc hangs at Kernel virtual memory layout
Date: Wed, 01 Jun 2011 10:25:42 +1000 [thread overview]
Message-ID: <1306887942.29297.10.camel@pasglop> (raw)
In-Reply-To: <alpine.DEB.2.01.1105311644010.21697@trent.utfs.org>
On Tue, 2011-05-31 at 16:50 -0700, Christian Kujau wrote:
> Hi,
>
> trying to boot 3.0-rc1 on powerpc32 only progresses until:
>
> > Kernel virtual memory layout:
> > * 0xfffcf000..0xfffff000 : fixmap
>
> And then the system hangs, does not respond to keyboard (sysrq does not
> seem to work on this PowerBook G4). But after a while the system reboots
> itself, so I guess the machine panicked but did not print anything on the
> screen.
>
> Full messages (picture), config & (working) dmesg:
>
> http://nerdbynature.de/bits/3.0-rc1/
>
> I'm currently trying to bisect this, so far I have:
Hrm, I had it working on a pair of powerbooks yesterday. Can you try
something like "udbg-immortal" on your kernel command line to see if
that makes a difference in the output ?
Cheers,
Ben.
> ----------------------
> git bisect start
> # good: [61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf] Linux 2.6.39
> git bisect good 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf
> # bad: [55922c9d1b84b89cb946c777fddccb3247e7df2c] Linux 3.0-rc1
> git bisect bad 55922c9d1b84b89cb946c777fddccb3247e7df2c
> # bad: [c44dead70a841d90ddc01968012f323c33217c9e] Merge branch 'usb-next'
> of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> git bisect bad c44dead70a841d90ddc01968012f323c33217c9e
> # bad: [d93515611bbc70c2fe4db232e5feb448ed8e4cc9] macvlan: fix panic if
> lowerdev in a bond
> git bisect bad d93515611bbc70c2fe4db232e5feb448ed8e4cc9
> ----------------------
>
> Any ideas?
>
> Thanks,
> Christian.
next prev parent reply other threads:[~2011-06-01 0:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 23:50 3.0-rc1: powerpc hangs at Kernel virtual memory layout Christian Kujau
2011-06-01 0:25 ` Benjamin Herrenschmidt [this message]
2011-06-01 0:25 ` Benjamin Herrenschmidt
2011-06-01 0:48 ` Christian Kujau
2011-06-01 0:48 ` Christian Kujau
2011-06-01 1:08 ` Christian Kujau
2011-06-01 1:08 ` Christian Kujau
2011-06-01 3:02 ` Christian Kujau
2011-06-01 3:02 ` Christian Kujau
2011-06-01 3:49 ` Benjamin Herrenschmidt
2011-06-01 3:49 ` Benjamin Herrenschmidt
2011-06-02 0:16 ` Christian Kujau
2011-06-02 0:16 ` Christian Kujau
2011-06-02 0:47 ` Benjamin Herrenschmidt
2011-06-02 0:47 ` Benjamin Herrenschmidt
2011-06-02 2:57 ` Benjamin Herrenschmidt
2011-06-02 2:57 ` Benjamin Herrenschmidt
2011-06-02 3:06 ` Christian Kujau
2011-06-02 3:06 ` Christian Kujau
2011-06-02 4:27 ` Christian Kujau
2011-06-02 4:27 ` Christian Kujau
2011-06-02 7:33 ` Benjamin Herrenschmidt
2011-06-02 7:33 ` Benjamin Herrenschmidt
2011-06-06 2:11 ` Christian Kujau
2011-06-06 2:11 ` Christian Kujau
2011-06-06 3:46 ` Benjamin Herrenschmidt
2011-06-06 3:46 ` Benjamin Herrenschmidt
2011-06-10 22:54 ` Christian Kujau
2011-06-10 22:54 ` Christian Kujau
2011-06-10 22:59 ` Rafał Miłecki
2011-06-10 22:59 ` Rafał Miłecki
2011-06-02 6:00 ` Rafał Miłecki
2011-06-02 6:00 ` Rafał Miłecki
2011-06-02 6:07 ` Rafał Miłecki
2011-06-02 6:07 ` Rafał Miłecki
2011-06-02 6:16 ` Christian Kujau
2011-06-02 6:16 ` Christian Kujau
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=1306887942.29297.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
/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.