reassign 404951 linux-2.6 retitle 404951 linux-2.6: sb1-bcm91250a kernel does not boot found 404951 2.6.18.dfsg.1-12 severity 404951 critical thanks
On Fri, Mar 23, 2007 at 09:01:53PM +0100, Karsten Merker wrote: > The problem (kernel does not start on SWARM) still exists in d-i rc2, > downloaded on 2007/03/23 from > > http://ftp.nl.debian.org/debian/dists/testing/main/installer-mips/current/images/sb1-bcm91250a/netboot/ > > Boot log is as follows: > > CFE> boot -tftp 192.168.2.14:/tftpboot/swarm-rc2/sibyl > Loader:raw Filesys:tftp Dev:eth0 File:192.168.2.14:/tftpboot/swarm-rc2/sibyl > Options:(null) > Loading: ....... 130116 bytes read > Entry at 0x0000000020000000 > Closing network. > Starting program at 0x0000000020000000 > SiByte Loader, version 2.4.2 > Built on Oct 4 2005 > Network device 'eth0' configured > Getting configuration file > tftp:192.168.2.14:/tftpboot/swarm-rc2/sibyl.conf... > Config file retrieved. > Available configurations: > install > rescue > Boot which configuration [install]: > Loading kernel (ELF64): > [EMAIL PROTECTED] > done > Loading ramdisk at 0x8057e000...3868329 bytes loaded > Set up command line arguments to: root=/dev/ram console=duart0 > ramdisk_size=3816 rd_start=0x8057E000 rd_size=0x3B06A9 > Setting up initial prom_init arguments > Cleaning up state... > Transferring control to the kernel. > Kernel entry point is at 0x804f7000 > Broadcom SiByte BCM1250 B2 @ 800 MHz (SB1 rev 2) > Board type: SiByte BCM91250A (SWARM) > > After that, the system starts CFE again. > This is actually a kernel bug that is reproducible on ball (Debian mips build daemon). I am therefore reassigning the package to linux-2.6. I am bumping the severity of this bug to critical as: - This make this kernel flavour totally useless - All Debian mipsen build daemons are bcm91250a boards -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]