Bug#649673: [powerpc] fails to boot - immediate oops
- To: "Clea F. Rees" <reescf@gmail.com>
- Cc: 649673@bugs.debian.org
- Subject: Bug#649673: [powerpc] fails to boot - immediate oops
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Wed, 15 Feb 2012 15:51:20 -0600
- Message-id: <[🔎] 20120215215120.GA28193@burratino>
- Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 649673@bugs.debian.org
- In-reply-to: <20111124000822.GF11614@elie.hsd1.il.comcast.net>
- References: <20111123010845.4673.41330.reportbug@CyfrifiadurCFR.local> <20111123031433.GA15510@elie.hsd1.il.comcast.net> <CA+n4xYbYVxu6Zt7A2=jHqSPw0DrXrwgcUTMmo2ghim6=MpWkjw@mail.gmail.com> <20111123235912.GE11614@elie.hsd1.il.comcast.net> <20111124000822.GF11614@elie.hsd1.il.comcast.net>
tags 649673 + moreinfo
# ??
found 649673 linux-2.6/3.1.1-1
quit
Hi,
Jonathan Nieder wrote:
> Clea F. Rees wrote:
>> | TASK = e4c05130[5113] 'modprobe' THREAD: e4c38000
>
> So, this good news. It means it might be possible to track down which
> module is responsible for the oops by entering a minimal environment
> and loading them with "modprobe" one at a time. See the "break"
> parameter in the initramfs-tools(8) manual and [1] for hints.
Ping. Did you get a chance to try this?
>> Yes, it says it is booted into a v3.0.y kernel. Maybe your bootloader
>> didn't notice the updated installed image.
>
> This part would still be good to figure out. The "printk_delay"
> kernel commandline parameter might be helpful if the early messages
> scroll past too quickly.
Finding out which kernel is booting would be interesting, too.
Happy new year,
Jonathan
Reply to: