Bug#649673: [powerpc] fails to boot - immediate oops

2012-02-15 Thread Jonathan Nieder
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 b

Bug#649673: [powerpc] fails to boot - immediate oops

2011-11-23 Thread Jonathan Nieder
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" par

Bug#649673: [powerpc] fails to boot - immediate oops

2011-11-23 Thread Jonathan Nieder
retitle 649673 [powerpc] immediate oops on boot (Kernel access of bad area, sig: 11) severity 649673 important quit Clea F. Rees wrote: > On 23 November 2011 03:14, Jonathan Nieder wrote: >> cfr wrote: >>> Kernel oops. Boot failed. Turned machine off at switch. Restarted >>> choosing to boot th

Bug#649673: [powerpc] fails to boot - immediate oops

2011-11-22 Thread Jonathan Nieder
Hi, cfr wrote: > Kernel oops. Boot failed. Turned machine off at switch. Restarted > choosing to boot the 2.6 kernel at the second prompt. [...] > I don't have access to a digital camera right now though I can try to > get a shot with one if required. I don't have any idea how to use a > serial o