I have a hack that works. Perhaps it will give a bit more understanding so that
a proper patch can be created. My changes were applied on top of 4.9-rc1 with
the patch from
https://www.linux-mips.org/archives/linux-mips/2016-10/msg00130.html, and were
as follows:
Index: linux/kernel/printk/pr
On 10/24/2016 11:29 AM, Paul Burton wrote:
On Monday, 24 October 2016 11:04:58 BST Larry Finger wrote:
On 10/23/2016 05:48 AM, Thorsten Leemhuis wrote:
Hi! On 20.10.2016 07:55, Larry Finger wrote:
Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC)
with the following spla
On Monday, 24 October 2016 11:04:58 BST Larry Finger wrote:
> On 10/23/2016 05:48 AM, Thorsten Leemhuis wrote:
> > Hi! On 20.10.2016 07:55, Larry Finger wrote:
> >> Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC)
> >> with the following splat:
> >> Kernel Panic - not synch
On 10/23/2016 05:48 AM, Thorsten Leemhuis wrote:
Hi! On 20.10.2016 07:55, Larry Finger wrote:
Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC) with
the following splat:
Kernel Panic - not synching: Attempted to kill init: exitcode = 0x0200
Thx for CCing regressi..
Hi! On 20.10.2016 07:55, Larry Finger wrote:
> Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC)
> with
> the following splat:
> Kernel Panic - not synching: Attempted to kill init: exitcode = 0x0200
>
Thx for CCing regressi...@leemhuis.info I added this report to the
On 10/20/2016 12:55 AM, Larry Finger wrote:
Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC) with
the following splat:
Kernel Panic - not synching: Attempted to kill init: exitcode = 0x0200
Call trace:
dump_stack+0x24/0x34 (unreliable)
panic+0x110/0x2ac
do_exit+0x4
6 matches
Mail list logo