On Wed, 7 Feb 2001, Alan Cox wrote:
> > report got ignored). After running for 4 days I got many, many oopses.
> > They were trigerred by xscreensaver, and some other X-related apps.
> > After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
> > graphics: Riva TNT2
>
> That makes
On Wed, 7 Feb 2001, Alan Cox wrote:
> > am not sure how to eliminate or confirm this. Recently I added some RAM
> > (256->384) and decided to get rid of swap. This seemed to have destabilized
> > the system, although nothing is obvious. I can try to stress the system by
>
> Get a copy of memtest8
> am not sure how to eliminate or confirm this. Recently I added some RAM
> (256->384) and decided to get rid of swap. This seemed to have destabilized
> the system, although nothing is obvious. I can try to stress the system by
Get a copy of memtest86, its a standalone memory tester.
-
To unsub
On Wed, 7 Feb 2001, Alan Cox wrote:
> > report got ignored). After running for 4 days I got many, many oopses.
> > They were trigerred by xscreensaver, and some other X-related apps.
> > After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
> > graphics: Riva TNT2
>
> That makes
> report got ignored). After running for 4 days I got many, many oopses.
> They were trigerred by xscreensaver, and some other X-related apps.
> After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
> graphics: Riva TNT2
That makes it harder to say 'Use a 3.3.6 X server'. If you
Hi all,
I have a misfortune of reporting yet another Oops in 2.4.1 (my previous
report got ignored). After running for 4 days I got many, many oopses.
They were trigerred by xscreensaver, and some other X-related apps.
After dopping to runlevel 3, the system seemed O.K. Nothing unusual in
proces
6 matches
Mail list logo
