[Debootloaders-silo] Bug#570264: Boot failure with "Last Trap: Fast Data Access MMU Miss"

[Jurij Smakov]

On Wed, Feb 17, 2010 at 01:47:59PM -0500, John Cater wrote:
> Package: silo
> Version: 1.4.14+git20100207-1
> 
> (I assume this is the correct version number, it's from a fresh install of
> sid).
> 
> I have a SunFire T1000 sparc server running the LDom virtualization
> software. Last night I created a new VM, with the following stats:
> CPU: 4x1000GHz
> RAM: 1GB
> Disk: 10GB
> 
> I used the sid sparc netboot image (from
> http://ftp.nl.debian.org/debian/dists/sid/main/installer-sparc/current/images/netboot/boot.img),
> and booted the VM. Install proceeded normally, and I selected to install
> sid.
> 
> After install completed, I rebooted the VM, and received this message:
> {0} ok boot disk
> Boot device: /virtual-devices at 100/channel-devices at 200/disk at 0  File and args:
> 
> ERROR: Last Trap: Fast Data Access MMU Miss
> 
> I am able to use the netboot image and boot the system and re-mount the
> disks. The system itself seems fine, but Silo will not allow the boot.
> 
> Let me know if there is anything further I can do to test or debug this.

Hi John,

A couple of things which may be going on here:

* I've recently noticed a similar problem, where SILO would fail to 
boot the system after fresh install (http://bugs.debian.org/565639).
It was caused by kernel 2.6.30 (which is currently used in development 
installer builds) incorrectly reporting the machine type via uname, so 
SILO was installing the 32-bit second stage bootloader instead of 
64-bit one, which leads to a failure like that. You can work around it
by starting a shell from the installer, and running something like 
this (assuming that your already-installed system resides on 
/dev/sda):

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
mount /dev /mnt/dev -o bind
chroot /mnt
mount -t proc proc /proc
silo -u -f

Then unmount everything, and reboot. The -u flag to SILO forces 
installation of 64-bit bootloader, irrespectively of what the kernel 
reports. The problem will go away automatically once the kernel on the 
installation media will be updated to 2.6.32, which should happen real 
soon now, according to the installer team.

* Another possible breakage is related to installation into LDOMs. 
Please see http://bugs.debian.org/512740 for discussion and run a test 
install using the mini.iso image which I've mentioned in my Feb 14 
message in the bug trail. 

Please let me know if you have any further questions.

Thanks.
-- 
Jurij Smakov                                           jurij at wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC