Bug#565639: SunBlade 1000 installation report - boot fails after installation
reassign 565639 linux-2.6 2.6.30-8 severity 565639 serious affects 565639 debian-installer On Sunday 24 January 2010, Jurij Smakov wrote: Adding kernel team for comment: it looks like the value returned by uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in 2.6.30 (and, probably, later ones). This breaks SILO, which uses this value to determine what first-stage bootloader to install, as a result the sparc machines installed with current daily installer builds turn unbootable by the end of installation. Thanks for tracing the cause to this. Reassigning to the kernel team for further investigation. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Re: Bug#565639: SunBlade 1000 installation report - boot fails after installation
Processing commands for cont...@bugs.debian.org: reassign 565639 linux-2.6 2.6.30-8 Bug #565639 [installation-reports] SunBlade 1000 installation report - boot fails after installation Bug reassigned from package 'installation-reports' to 'linux-2.6'. Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after installation There is no source info for the package 'linux-2.6' at version '2.6.30-8' with architecture '' Unable to make a source version for version '2.6.30-8' Bug Marked as found in versions 2.6.30-8. severity 565639 serious Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after installation Severity set to 'serious' from 'normal' affects 565639 debian-installer Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after installation Added indication that 565639 affects debian-installer On Sunday 24 January 2010, Jurij Smakov wrote: Unknown command or malformed arguments to command. Adding kernel team for comment: it looks like the value returned by Unknown command or malformed arguments to command. uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in Unknown command or malformed arguments to command. 2.6.30 (and, probably, later ones). This breaks SILO, which uses this Unknown command or malformed arguments to command. value to determine what first-stage bootloader to install, as a result Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565639: SunBlade 1000 installation report - boot fails after installation
On Sun, Jan 17, 2010 at 05:08:55PM +0100, Frans Pop wrote: On Sunday 17 January 2010, Jurij Smakov wrote: Comments/Problems: Now that http://bugs.debian.org/562594 is fixed, I was able to continue the installation and it all went fine until the end. However, after finishing the installation machine fails to boot [...] As the installation itself works fine I would guess this is not an installer problem, but a kernel issue. Maybe it leaves the hardware in an incorrect state for the reboot. Have you tried a cold boot of the installed system? Adding kernel team for comment: it looks like the value returned by uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in 2.6.30 (and, probably, later ones). This breaks SILO, which uses this value to determine what first-stage bootloader to install, as a result the sparc machines installed with current daily installer builds turn unbootable by the end of installation. Please confirm that this change is not a result of some Debian-specific patch or build procedure, as it should be reported upstream if that's not the case. For reference: ju...@debian:~$ uname -a Linux debian 2.6.26-2-sparc64-smp #1 SMP Thu Nov 5 03:34:29 UTC 2009 sparc64 GNU/Linux ju...@debian:~$ uname -m sparc64 ~ # uname -a Linux debian 2.6.30-2-sparc64 #1 Sat Sep 26 07:26:31 UTC 2009 sparc GNU/Linux ~ # uname -m sparc I've confirmed that forcing the machine type by running 'silo -u -f' makes the machine bootable again. Best regards, -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565639: SunBlade 1000 installation report - boot fails after installation
Package: installation-reports
Boot method: Jan 14th netinst daily image for sparc
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/sparc/iso-cd/debian-testing-sparc-netinst.iso
Date: Sun Jan 17 15:37:37 GMT 2010
Machine: SunBlade 1000, same as in http://bugs.debian.org/562594
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[O]
Configure network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Clock/timezone setup: [O]
User/password setup:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[E]
Comments/Problems:
Now that http://bugs.debian.org/562594 is fixed, I was able to
continue the installation and it all went fine until the end.
However, after finishing the installation machine fails to boot with
messages:
SUNW,Sun-Blade-1000 (2 X UltraSPARC-III) , No Keyboard
Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.16.4, 2048 MB memory installed, Serial #51831895.
Ethernet address 0:3:ba:16:e4:57, Host ID: 8316e457.
Rebooting with command: boot
Boot device: disk File and args:
ERROR: Last Trap: Fast Data Access MMU Miss
Error -256
{0} ok
I thought it was some kind of random hardware quirk, so I tried
reinstalling a few times, but always got the same result, even if I
was zero-filling the first 200M of the hard drive before partitioning.
I then tried Lenny netinst CD (debian-503-sparc-netinst.iso), and it
worked without problems, so it must be some regression in the recent
CD images. At this point I have no clue what might be causing it, as
both Lenny and the current CD builds install the same SILO version and
partitions are set up identically (~100MB ext2 /boot partition is set
up to hold the boot files in both cases). I'm going to ask on
debian-sparc whether anyone can reproduce it.
Another minor detail: serial console output in daily builds is
black-and-white, while Lenny installer was showing up in color (at
least, red/blue where appropriate).
--
Jurij Smakov ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565639: SunBlade 1000 installation report - boot fails after installation
On Sunday 17 January 2010, Jurij Smakov wrote: Comments/Problems: Now that http://bugs.debian.org/562594 is fixed, I was able to continue the installation and it all went fine until the end. However, after finishing the installation machine fails to boot [...] As the installation itself works fine I would guess this is not an installer problem, but a kernel issue. Maybe it leaves the hardware in an incorrect state for the reboot. Have you tried a cold boot of the installed system? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565639: SunBlade 1000 installation report - boot fails after installation
On Sun, Jan 17, 2010 at 05:08:55PM +0100, Frans Pop wrote: On Sunday 17 January 2010, Jurij Smakov wrote: Comments/Problems: Now that http://bugs.debian.org/562594 is fixed, I was able to continue the installation and it all went fine until the end. However, after finishing the installation machine fails to boot [...] As the installation itself works fine I would guess this is not an installer problem, but a kernel issue. Maybe it leaves the hardware in an incorrect state for the reboot. Have you tried a cold boot of the installed system? Yeah, neither cold-boot nor reinstalling/rerunning silo in the /target after installation is done help. I'll try to investigate next week. -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
