Bug#351909: 2.6.14 boots, but not 2.6.15
severity 351909 important
retitle 351909 [powerpc,oldworld] 2.6.14 boots, but not 2.6.15
reassign 351909 linux-2.6
thanks
Thanks Hans for your report, i lowered the severity since we are about to move
2.6.15 to testing, and oldworld has been a not fully working subarch
previously, but this does not mean we don't want to fix this for etch.
Friendly,
Sven Luther
On Wed, Feb 08, 2006 at 01:33:21PM +0100, Hans Ekbrand wrote:
> Package: linux-image-2.6-powerpc-miboot
> Severity: grave
>
> I tried the following images on a performa 5400. This box normally
> runs sid and has no problem with any 2.6.15-kernel when booted by
> quik.
>
> So the problem is specific to miboot and 2.6.15.
>
> http://people.debian.org/~luther/d-i/sid/images/2005-12-28/powerpc/floppy/boot.img
> 2.6.14
> Works!
>
> http://people.debian.org/~luther/d-i/sid/images/2005-01-10/powerpc/floppy/boot.img
> 2.6.14
> Works!
>
> http://people.debian.org/~luther/d-i/sid/images/2006-01-16/powerpc/floppy/boot.img
> 2.6.15
> Hangs also, now with
>
> ide0: Found Apple Ohare ATA controller, bus ID 0, irq13
> ADB keyboard at 2, handler set to 3
> Serial port locked ON by debugger!
> ABD HID on ID 3 not yet registered
>
> http://people.debian.org/~luther/d-i/sid/images/2006-01-25/powerpc/floppy/boot.img
> 2.6.15
> This kernel hangs with
>
> ide0: Found Apple Ohare ATA controller, bus ID 0, irq13
> ADB keyboard at 2, handler set to 3
> Serial port locked ON by debugger!
>
> http://people.debian.org/~luther/d-i/sid/images/2006-02-07/powerpc/floppy/boot.img
> 2.6.15
> This kernel hangs with same as the 2006-01-25
>
> So to sum up: 2.6.14 works, but 2.6.15 does not.
>
> Kind regards,
> Hans Ekbrand
>
>
> --
> To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
> ---------------------------------------------------------------------------------------
> Wanadoo vous informe que cet e-mail a ete controle par l'anti-virus mail.
> Aucun virus connu a ce jour par nos services n'a ete detecte.
>
>
>
Reply to: