HDAMA+FILO booting SUSE Linux

Craig C Forney cforney at opus.com
Wed May 12 14:34:00 CEST 2004

First, thanks for fixing the broken sourceforge LinuxBIOS tree earlier
this week.

I've been using LinuxBIOS successfully for some custom dense board
designs being used for hardware verification, primarily running
memtest86.  I only have a serial port available.  I'm using an Arima
HDAMA board as a known working testbed for trying software before
running it on our own boards.

At this point, I'd like to attempt to boot up Linux.  The first step is
getting it to work properly on the Arima HDAMA board.  I have booted and
loaded Suse 9.0 Professional (I'm awaiting delivery of 9.1), as well as
the Suse 9.1 Live CD, without problems with the standard Phoenix BIOS on
the Arima HDAMA board.

Using LinuxBIOS plus FILO, I'm not having much luck.  I've checked
through the archives, but I'm not finding the right combination of steps
that works.

 -- Booting of the Suse 9.0 DVD in an attempt to install Linux on disk
gets up to the point where yast has determined the proper partition
sizes during it's initial config screens, but then hangs.  It's in the
middle of the yast formatted screens, so I don't know a good way to copy
this to an email.

 -- Booting an already loaded 9.0 system panics the kernel:

		POSIX conformance testing by UNIFIX
		mtrr: v2.02 (20020716))
		CPU: L1 I Cache: 64K (64 bytes/line/2 way), D cache 64K
(64 bytes/line/2 way)
		CPU: L2 Cache: 1024K (64 bytes/line/8 way)
		CPU0:  stepping 01
		per-CPU timeslice cutoff: 5119.55 usecs.
		task migration cache decay timeout: 10 msecs.
		Booting processor 1/1 rip 6000 page 000001000261a000
		Not respondin<4>NMI Watchdog detected LOCKUP on CPU0,
eip ffffffff80204027, registers:
		CPU 0 
		Pid: 0, comm: swapper Not tainted
		RIP: 0010:[<ffffffff80204027>]{serial_in+71}
		RSP: 0018:ffffffff804dfda8  EFLAGS: 00000202
		RAX: 0000000000000000 RBX: 00000000000f4238 RCX:
		RDX: 00000000000003fd RSI: 0000000000000005 RDI:
		RBP: ffffffff804837a0 R08: 000000000000006e R09:
		R10: 0000000000000000 R11: 0000000000000000 R12:
		R13: 000000000000000d R14: 0000000000000010 R15:
		FS:  0000000000000000(0000) GS:ffffffff804cb3c0(0000)
		CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
		CR2: 0000000000000000 CR3: 0000000000101000 CR4:
		Process swapper (pid: 0, stackpage=ffffffff804df000)
		Stack: ffffffff804dfda8 0000000000000018
0000000000040000 0000000000000000 
		       0000000000000000 0000000000000000
0000000000000000 0000000000000000 
  		     0000000000000000 0000000000000000 0000000000000000
		Call Trace:  <EOE>

		Code: 0f b6 c0 c3 66 66 90 66 90 8b 87 ac 00 00 00 41 89
d0 83 f8 
		console shuts up ...

 -- Booting the Suse 9.1 Live CD (I copied all the files on the Live CD
to the root file system on an already installed Suse 9.0 system)

		boot: hda3:/livecd/vmlinuz root=/dev/hda3
initrd=hda3:/livecd/initrd.gz console=ttyS0,115200
		Found Linux version 2.6.4-52-default (geeko at buildhost)
#1 Wed Apr 7 02:08:30 UTC 2004 bzImage.
		Loading kernel... ok
		Loading initrd... ok
		Jumping to entry point...
		Linux version 2.6.4-52-default (geeko at buildhost) (gcc
version 3.3.3 (SuSE Linux)) #1 Wed Apr 7 02:08:30 UTC 2004
		BIOS-provided physical RAM map:
		 BIOS-e820: 0000000000000dc4 - 00000000000a0000 (usable)
		 BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
		128MB vmalloc/ioremap area available.
		128MB HIGHMEM available.
		896MB LOWMEM available.
		On node 0 totalpages: 262144
		  DMA zone: 4096 pages, LIFO batch:1
		  Normal zone: 225280 pages, LIFO batch:16
		  HighMem zone: 32768 pages, LIFO batch:8
		DMI not present.
		ACPI: Unable to locate RSDP
		Built 1 zonelists
		Kernel command line: root=/dev/hda3 console=ttyS0,115200
		Initializing CPU#0
		PID hash table entries: 4096 (order 12: 32768 bytes)
		CKRM Initialized
		Detected 1403.889 MHz processor.
		Using tsc for high-res timesource
		Console: colour VGA+ 80x25
		Memory: 1009620k/1048576k available (1969k kernel code,
37972k reserved, 677k data, 212k init, 131072k highmem)
		Checking if this processor honours the WP bit even in
supervisor mode... Ok.
		Calibrating delay loop... 2760.70 BogoMIPS
		Security Scaffold v1.0.0 initialized
		SELinux:  Initializing.
		SELinux:  Starting in permissive mode
		There is already a security framework initialized,
register_security failed.
		Failure registering capabilities with the kernel
		selinux_register_security:  Registering secondary module
		Capability LSM initialized
		Dentry cache hash table entries: 131072 (order: 7,
524288 bytes)
		Inode-cache hash table entries: 65536 (order: 6, 262144
		Mount-cache hash table entries: 512 (order: 0, 4096
		checking if image is initramfs... it is
		Freeing initrd memory: 26442k freed
		CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
		CPU: L2 Cache: 1024K (64 bytes/line)
		Intel machine check architecture supported.
		Intel machine check reporting enabled on CPU#0.
		CPU: AMD 02/05 stepping 01
		Enabling fast FPU save and restore... done.
		Enabling unmasked SIMD FPU exception support... done.
		Checking 'hlt' instruction... OK.
		POSIX conformance testing by UNIFIX
		NET: Registered protocol family 16
		PCI: Using configuration type 1
		mtrr: v2.0 (20020519)
		ACPI: Subsystem revision 20040326
		ACPI: Interpreter disabled.
		Linux Plug and Play Support v0.97 (c) Adam Belay
		ACPI: ACPI tables contain no PCI IRQ routing entries
		PCI: Invalid ACPI-PCI IRQ routing table
		PCI: Probing PCI hardware
		PCI: Probing PCI hardware (bus 00)
		 ... the first call_usermodehelper: pci_bus
		CPU 0: Machine Check Exception: 0000000000000004
		Bank 4: b200000000070f0f
		Kernel panic: CPU context corrupt

So, it's pretty clear I am missing a crucial step (or two or three) to
booting Linux successfully with LinuxBIOS+FILO.  I'd appreciate some
help in identifying the basic steps.


Craig Forney
Opus Innovations LLC

More information about the coreboot mailing list