linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Walsh <walsh.benj@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Maple PPC970 kexec crash-dump problems
Date: Fri, 23 Jan 2009 15:59:47 -0500	[thread overview]
Message-ID: <cb298a870901231259h6bd1ae2ag2baeb20173219664@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Hi all,

I am trying to use kexec with a crash dump kernel on a Maple board (Motorola
ATCA6101 to be precise). This board is running a two-CPU PPC970FX. I am
running a 2.6.27-10 kernel and have tried both older kexec-tools and the
newest ones. I have tried SMP and non-SMP kernels.

Using kexec -l to fast boot works correctly. However, loading a crash dump
kernel and triggering a crash via echo c > /proc/sysrq-trigger simply hangs
the board. I have traced the sequence down to after the call to
kexec_copy_flush(), when the CPU returns to real-address mode (bl
real_mode). At this point I have no further debugging information.

Two things could help me:

- Getting the fix if this is a known issue and a fix exists. I have looked
at recent patches and nothing lept to mind, mostly relocatable kernel
support.
- Obtaining the address of the serial port @3f8 in real mode. The init
sequence with udbg ON says that the physical address of the port is
0xf40003f8; however, setting it up in poll mode and trying to stuff
characters in the tx buffer doesn't produce anything.

Has anyone recently tried to use the serial port in real mode ?

Thanks for any help.

Ben

[-- Attachment #2: Type: text/html, Size: 1233 bytes --]

             reply	other threads:[~2009-01-23 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 20:59 Benjamin Walsh [this message]
2009-01-24  7:52 ` Maple PPC970 kexec crash-dump problems Milton Miller
2009-02-04 18:48   ` Benjamin Walsh
2009-02-06 16:53     ` Milton Miller

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=cb298a870901231259h6bd1ae2ag2baeb20173219664@mail.gmail.com \
    --to=walsh.benj@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).