public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Will Schmidt <will_schmidt@vnet•ibm.com>
To: ppc64@storix•com
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Kernel panic: kernel access of bad area pc
Date: Mon, 11 Sep 2006 10:37:12 -0500	[thread overview]
Message-ID: <1157989033.27328.16.camel@farscape> (raw)
In-Reply-To: <200609081532.59764.ppc64@storix.com>

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

  reply	other threads:[~2006-09-11 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 22:32 Kernel panic: kernel access of bad area pc ppc64
2006-09-11 15:37 ` Will Schmidt [this message]
2006-09-11 16:01 ` Olaf Hering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1157989033.27328.16.camel@farscape \
    --to=will_schmidt@vnet$(echo .)ibm.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=ppc64@storix$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox