All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ethan Weinstein <e-d0uble@stinkfoot.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: aic7xxx panics (long)
Date: 01 Jul 2003 11:59:50 +0200	[thread overview]
Message-ID: <1057053589.32576.310.camel@gaston> (raw)
In-Reply-To: <3F00E86B.1000309@stinkfoot.org>


On Tue, 2003-07-01 at 03:48, Ethan Weinstein wrote:

> Ben,
>
> Unfortunately, xmon gives no output except that is't attempting to use a
> serial port.  This machine (G4 MDD) has no serial, so I'm at a loss
> getting any type of serial console working unless you have a suggestion.
> I see the xmon source mentions using firewire, but I have no idea how
> I'd get that working, as this is the only machine here with fw.

Edit arch/ppc/xmon/start.c, line 133, change use_screen = 0 to
use_screen = 1. At least, xmon will display it's full message on screen
though you'll still won't be able to type commands.

If you additionally load your kernel with it's system.map (that is add
a line that says "sysmap=/boot/System.map" to /etc/yaboot.conf, and make
sure /boot/System.map is what was produced when you built the kernel),
then you'll have at least some symbolic output that can be useful.

Additionally, you can tweak xmon to force display of a stack backtrace
when it is entered. Edit arch/ppc/xmon/xmon.c, line 394, just before
"last_cmd = NULL;", add "backtrace(excp);".

Finally, you can also disable xmon in the kernel config and see if you
get an Oops message you can copy manually.

> The aic7xxx driver's output is as usual, it begins to initialize... and
> then we get the crash.
>
> Is there anything else I can do here?  I've heard I can replace the
> internal modem with a third party serial interface.  I'd be willing to
> try this to get a serial console for debugging.

Additionally, you can try upgrading to Justin Gibbs latest driver
(I don't have the URL at hand right now though, but I'll soon update
my "devel" rsync with a 2.4.22-pre snapshot that contains that latest
version)

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-07-01  9:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30  6:27 aic7xxx panics Ethan Weinstein
2003-06-30  7:11 ` Benjamin Herrenschmidt
2003-07-01  1:48   ` aic7xxx panics (long) Ethan Weinstein
2003-07-01  9:59     ` Benjamin Herrenschmidt [this message]
2003-07-02  3:37       ` Ethan Weinstein
2003-07-02  7:59         ` Ethan Benson
2003-07-02  8:39           ` Michel Dänzer
2003-07-02  9:24           ` Benjamin Herrenschmidt
2003-07-02  9:48             ` Ethan Benson
2003-07-02 12:26         ` Benjamin Herrenschmidt
2003-07-04  1:01           ` Ethan Weinstein
2003-07-07 15:04             ` Benjamin Herrenschmidt
2003-07-07 16:51               ` Ethan Weinstein
2003-07-15 14:15               ` Ethan Weinstein
2003-07-15 14:17                 ` Benjamin Herrenschmidt
2003-07-15 14:26                   ` Ethan Weinstein
2003-07-15 14:30                     ` Benjamin Herrenschmidt
2003-07-19 22:22                       ` Ethan Weinstein
2003-07-21 23:42                         ` Benjamin Herrenschmidt
2003-07-22  1:11                           ` Ethan Weinstein

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=1057053589.32576.310.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=e-d0uble@stinkfoot.org \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.