Subject: Re: Instability in -current
To: Juan RP <email@example.com>
From: Kurt Schreiner <firstname.lastname@example.org>
Date: 05/21/2007 13:37:51
On Mon, May 21, 2007 at 01:11:38PM +0200, Juan RP wrote:
> On Mon, 21 May 2007 12:56:30 +0200
> Kurt Schreiner <email@example.com> wrote:
> > On Mon, May 21, 2007 at 04:21:42AM +0200, Juan RP wrote:
> > > On Sun, 20 May 2007 22:18:09 -0400
> > > Gary Duzan <firstname.lastname@example.org> wrote:
> > >
> > > > I tried the following, but it didn't seem to help. The easiest
> > > > way I've found to crash X is to bring up a bunch of tabs in firefox,
> > > > but parallel kernel builds are dying, too.
> > >
> > > I've been using the following patch since yamt-idlelwp was merged in.
> > > With that patch it works rock solid (Frank Van Der Linden is still
> > > trying to find the problem) so it's a temporary workaround:
> > > [...]
> > with this workaround the 'Error code 255' from "make -j<n> ...." seems
> > to be gone, too...
> The changes that were causing these problems were reverted, so it
> should be stable as before.
Hm, I first tried a -current kernel from sources as checked out from anoncvs,
i.e. with franks changes reverted and still had this 'Error code 255'.
Than tried with your patch applied and voila, no errors from make...
(Until the known one in gdb.)