From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ethan Weinstein <lists@stinkfoot.org>
Cc: Rudy Klinksiek <klink@arlut.utexas.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: "Illegal instruction" traps on smp clients - 2.4.19
Date: 27 Feb 2003 17:23:07 +0100 [thread overview]
Message-ID: <1046362987.2019.2.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <3E5E354D.605@stinkfoot.org>
On Thu, 2003-02-27 at 16:57, Ethan Weinstein wrote:
> Rudy Klinksiek wrote:
>
> | Smp and UP kernels work fine on the "server".
> |
> | Has anyone else seen this type of problem or something similar?
> |
>
> I have. I run a dual G4(7400), also with CONFIG_HIMEM and got plenty of
> random SIGILL's, SIGABRT's and deamons crashing upon startup until I
> started using Ben's bk tree. I've been using 2.4.20-ben(x) for quite
> some time now without this problem.
>
> | This appears to me to be an smp problem.
>
> | And then, what can I do about it? I'm willing to try things
> | as my time permits. I have looked at 2.5.60 memory.c/mmap.c
> | and related functions, and trying to port the new methods
> | back to 2.4.19 seems to be a rather daunting task.
> |
> | Comments, suggestions?
> |
> Try rsyncing ben's bk tree and using it, it cleared up this issue for me.
>
> rsync -avz --delete rsync.penguinppc.org::linux-2.4-benh
This is actually my "stable" tree (2.4.20-ben7 at this time). Please
let me know if it's also fixed by the linuxppc_2_4 PPC bk tree (see
penguinppc.org for details on how to get these).
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-27 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 14:44 "Illegal instruction" traps on smp clients - 2.4.19 Rudy Klinksiek
2003-02-27 15:57 ` Ethan Weinstein
2003-02-27 16:23 ` Benjamin Herrenschmidt [this message]
2003-02-27 16:37 ` David Bryan
2003-02-27 18:26 ` Michael R. Zucca
2003-02-27 20:32 ` David Bryan
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=1046362987.2019.2.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=klink@arlut.utexas.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=lists@stinkfoot.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).