Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Matthew Wilcox <matthew@wil.cx>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] 64-bit kernel crashes on my c3600
Date: Wed, 20 Oct 2004 11:24:52 -0400	[thread overview]
Message-ID: <20041020152450.GW24430@baldric.uwo.ca> (raw)
In-Reply-To: <20041019175440.GP16153@parcelfarce.linux.theplanet.co.uk>

On Tue, Oct 19, 2004 at 06:54:40PM +0100, Matthew Wilcox wrote:
> One of the problems with this crash is that enabling EARLY_CONSOLE
> doesn't help.  The exact same configuration boots fine in 32-bit mode.
> I'm building from the same tree (with O=) so there's no question of patch
> skew.  Turning on DISCONTIGMEM does not help.  The HPMC points inside
> the code generated by the save_general macro just past skip_save_ior
> inside the intr_save function in entry.S

This is just before calling handle_interruption, so it looks like you
took an interrupt before something was setup properly?

These sorts of problems are very messy to debug if they are
non-deterministic. Just stick an infinite loop in a portion of code you
expect might be before the HPMC, run, TOC, check, and move the loop.
That's my normal procedure when I had to debug similar stuff to prove
some lws code.
 
> I'm not even sure how to start debugging.  My initial thought is that r29
> seems awfully high to be a good memory address.

Why do you think that?

I'm interested in r2 which is a userspace address. Did this box make it
to userspace?

c.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-10-20 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 17:54 [parisc-linux] 64-bit kernel crashes on my c3600 Matthew Wilcox
2004-10-20 15:24 ` Carlos O'Donell [this message]
2004-10-31  6:29 ` Randolph Chung

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=20041020152450.GW24430@baldric.uwo.ca \
    --to=carlos@baldric.uwo.ca \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.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