> From: Tomas Szepe <email@example.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 <firstname.lastname@example.org>.)
> 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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri May 31 2002 - 22:00:19 EST