I have a process to create tape boot images by combining the kernel and initrd
into a zImage. The process works for 2.4 (RHEL 3.3) & 2.6 kernels (SLES9 &
RHEL4). However on SLES8 ppc64 the kernel panics with "error kernel access of
bad area pc".
Attached is the complete log of the boot with backtrace data.
The system is:
IBM 7044-170
SLES 8 (2.4.19-ul1-ppc64-SMP)
The kernel was uncompressed using:
# objcopy -j .kernel:vmlinux -O binary vmlinuz vmlinux-storix.gz
# gunzip vmlinux-storix.gz
Which gives me vmlinux-storix
Kernel Memsize
# nm -n /boot/vmlinux-storix | tail -n1
c0000000007c4000 A _end
Anyone have an idea what is causing the failure? The error message appears to
be pretty generic.
--
David Huffman
Support & Development
Storix, Inc
Life is hard. Get a helmet.
On Fri, 2006-08-09 at 15:32 -0700, ppc64@storix.com wrote:
I have a process to create tape boot images by combining the kernel and initrd
into a zImage. The process works for 2.4 (RHEL 3.3) & 2.6 kernels (SLES9 &
RHEL4). However on SLES8 ppc64 the kernel panics with "error kernel access of
bad area pc".
Anyone have an idea what is causing the failure? The error message appears to
be pretty generic.
The exception is a "TRAP: 0600" which is an alignment interrupt.
the trap occurred at NIP: C000000000085874
Get an objdump of your kernel, (or drop into xmon/kdb and use the
disassembler commands) and see what instruction lives at that NIP
address, and which registers it is referencing. (Then its a matter of
finding out why the registers have bad data in them).
(You probally have already done this, but if not... ) If you're booting
off of tape in this instance, may want to try booting off of disk, and
doing some tape operations after successful boot, to ensure the driver
is all OK.
-Will
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Fri, Sep 08, ppc64@storix.com wrote:
I have a process to create tape boot images by combining the kernel and initrd
into a zImage. The process works for 2.4 (RHEL 3.3) & 2.6 kernels (SLES9 &
RHEL4). However on SLES8 ppc64 the kernel panics with "error kernel access of
bad area pc".
What do you use to create the zImage header?
Also, does the SP3 kernel work any better? The reiserfs mem corruption
has likely has likely the same cause as the ramdisk corruption.