From: Tomas Szepe <szepe@pinerecords.com>
To: linux-kernel@vger.kernel.org
Cc: tcallawa@redhat.com, colin@gibbs.dhs.org,
sparclinux@vger.kernel.org, aurora-sparc-devel@linuxpower.org
Subject: 2.4 SRMMU bug revisited
Date: Mon, 27 May 2002 11:24:08 +0200 [thread overview]
Message-ID: <20020527092408.GD345@louise.pinerecords.com> (raw)
> From: Tomas Szepe <szepe@pinerecords.com>
> Date: Thu, 23 May 2002 09:02:44 +0200
>
> > > 2. What is the "proper" fix for the patch collision between the raid
> > > patch and the ext3 patch in /include/linux/fs.h?
> >
> > Use 2.4.
>
> Impossible on sparc32 on account of the lurking SRMMU bug.
> (See yesterday's post by Joris Braakman <jorisb@nl.euro.net>.)
>
> There have been several patches posted to deal with that
> problem, you can apply them yourself or grab Marcelo's
> current 2.4.x BK tree.
I finally got round to trying the patches out and --
unfortunately, things got even worse. While before the machine would
oops (still allowing one to ssh in and reboot) under heavy loads, now
it doesn't bother to log the slightest notice that something might
have broken, and freezes entirely (it can be pinged, though).
I can't say I like these fixes much.
T.
next reply other threads:[~2002-05-27 9:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:24 Tomas Szepe [this message]
2002-05-27 10:17 ` 2.4 SRMMU bug revisited David S. Miller
2002-05-27 6:20 ` Tomas Szepe
2002-05-27 10:40 ` David S. Miller
2002-05-27 11:19 ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41 ` Denis Vlasenko
2002-05-28 12:11 ` David S. Miller
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34 ` Colin Gibbs
2002-05-28 1:12 ` Tomas Szepe
2002-05-27 21:30 ` Tomas Szepe
2002-05-28 3:41 ` David S. Miller
2002-05-28 5:40 ` Tomas Szepe
2002-05-28 8:39 ` David Woodhouse
2002-05-28 11:58 ` Alan Cox
2002-05-28 11:05 ` David S. Miller
2002-05-28 12:10 ` Ben Collins
2002-05-28 12:19 ` David S. Miller
2002-05-28 0:40 ` David S. Miller
2002-05-29 21:42 ` Tomas Szepe
[not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` Pete Zaitcev
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=20020527092408.GD345@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=aurora-sparc-devel@linuxpower.org \
--cc=colin@gibbs.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tcallawa@redhat.com \
/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