On Mon, Apr 16, 2007 at 12:33:09PM -0700, J.C. Roberts wrote:
> On Monday 16 April 2007 12:06, Maurice Janssen wrote:
> > On Monday, April 16, 2007 at 11:30:29 -0700, Bryan Vyhmeister wrote:
> > >On Apr 16, 2007, at 10:39 AM, J.C. Roberts wrote:
> > >>I've never seen the "alpha bug" on my DS20L (equivalent to the
> > >>CS20) or
> > >>my 500/500 but I have seen it on my PC* boxes. Other people have
> > >> had the exact opposite experience. The only time I've hit the bug
> > >> was during system builds and in contrast, others have reported
> > >> hitting the bug at other times during normal operation. -- The
> > >> trouble is, when you have a strange "mystery bug" floating out
> > >> there, it may or may not be correctly blamed for any and all
> > >> problems.
> > >
> > >Thank you for the followup. I guess I will just try and see what
> > >happens. I should dig out my PC164 whatever box and see if it
> > >exhibits the issue.
> >
> > FWIW: the bug seems to occur at my 3000/300X, but only during heavy
> > load like 'make build'. I never finished such a build, but I only
> > tried a few times.
> >
> > Maurice
>
> I just thought of something which might be worth a try on systems that
> show the bug during system builds; use nice(1) to lower the build
> priority. It's a long shot, and I haven't tried it, but it *might* be a
> useful work around. Then again, it might be a waste of time.
Just curious: why do you think this helps? It's not like nice'ing the
only process on the box that uses any real resources helps, does it?
Joachim
--
TFMotD: tl (4) - Texas Instruments ThunderLAN 10/100 Ethernet device
