All of lore.kernel.org
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Highmem on PPC?
Date: Tue, 5 Feb 2002 12:42:14 -0700	[thread overview]
Message-ID: <20020205124214.H6834@boardwalk> (raw)
In-Reply-To: <20020205193316.19866@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Tue, Feb 05, 2002 at 08:33:16PM +0100


On Tue, Feb 05, 2002 at 08:33:16PM +0100, Benjamin Herrenschmidt wrote:
>
> >I'm currently getting hard crashes on the dual 7410 with highmem.  Not
> >even the SMI starts xmon.  I'm not sure that it's a software bug,
> >which is why I'm getting the dual 7450.
>
> Interesting. I have similar reports about dual 800s with 1.5G of RAM.
> I don't personally have a machine with that much RAM, so it makes things
> a bit difficult to debug. All I noticed so far is that
> enabling interrupt distribution will cause occasional lockups on my
> dual 7400 at work (not related to highmem). So if you plan to chase
> this highmem bug, start by disabling that option to avoid mixing
> problems.

I don't use interrupt distribution.

I triggered the absolute hard hang with my usual tests: 5 or 6 of the
following running in the background:

find /mnt/cdrom -exec cat {} \; > /dev/null 2>&1 &
find /usr -exec cat {} \; > /dev/null 2>&1 &

And a make -j8 zImage in the foreground.  I didn't even start the
flood ping before it hung. :)

> Just in case it's a spinlock bug (who knows...) you may want to hack
> the spinlock debug output to use the btext engine (basically #define
> printf to xmon_printf in the spinlock code and hack xmon/start.c to
> force use_screen).

This is actually over serial console, but I'll keep that in mind when
I get the apple.

> And let me know if you find something ;)

:) You bet.  You're sure you're not seeing these hangs?  What are you
using, dual 7400 with 1 GB RAM?

-VAL

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

  reply	other threads:[~2002-02-05 19:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  1:32 Highmem on PPC? Val Henson
2002-02-05 12:52 ` benh
2002-02-05 18:56   ` Val Henson
2002-02-05 19:33     ` Benjamin Herrenschmidt
2002-02-05 19:42       ` Val Henson [this message]
2002-02-05 19:47         ` Benjamin Herrenschmidt
2002-02-07 12:27       ` Christopher Murtagh
2002-02-07 21:43       ` Val Henson
2002-02-07 21:51         ` Benjamin Herrenschmidt
2002-02-07 21:56           ` Val Henson
2002-02-07 21:59             ` Benjamin Herrenschmidt
2002-02-07 21:53         ` Mark A. Greer
2002-02-07 21:58           ` Val Henson
2002-02-07 23:09             ` Mark A. Greer
2002-02-08  3:02         ` Tom Rini
2002-02-08  6:05         ` Christopher Murtagh
2002-02-08  6:25           ` Val Henson
2002-02-08 17:36       ` Val Henson

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=20020205124214.H6834@boardwalk \
    --to=val@nmt.edu \
    --cc=benh@kernel.crashing.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.