[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200701051553.04673.s0348365@sms.ed.ac.uk>
Date: Fri, 5 Jan 2007 15:53:04 +0000
From: Alistair John Strachan <s0348365@....ed.ac.uk>
To: Mikael Pettersson <mikpe@...uu.se>
Cc: torvalds@...l.org, 76306.1226@...puserve.com, akpm@...l.org,
bunk@...sta.de, greg@...ah.com, linux-kernel@...r.kernel.org,
yanmin_zhang@...ux.intel.com
Subject: Re: kernel + gcc 4.1 = several problems
On Wednesday 03 January 2007 02:20, Alistair John Strachan wrote:
> On Wednesday 03 January 2007 02:12, Mikael Pettersson wrote:
> > On Tue, 2 Jan 2007 17:43:00 -0800 (PST), Linus Torvalds wrote:
> > > > The suggestions I've had so far which I have not yet tried:
> > > >
> > > > - Select a different x86 CPU in the config.
> > > > - Unfortunately the C3-2 flags seem to simply tell GCC
> > > > to schedule for ppro (like i686) and enabled MMX and SSE
> > > > - Probably useless
> > >
> > > Actually, try this one. Try using something that doesn't like "cmov".
> > > Maybe the C3-2 simply has some internal cmov bugginess.
> >
> > That's a good suggestion. Earlier C3s didn't have cmov so it's
> > not entirely unlikely that cmov in C3-2 is broken in some cases.
> > Configuring for P5MMX or 486 should be good safe alternatives.
>
> Or just C3 (not C3-2), which is what I've done.
>
> I'll report back whether it crashes or not.
This didn't help. After about 14 hours, the machine crashed again.
cmov is not the culprit.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists