Re: Solid v2.1.115 kernel lockup

Michel Eyckmans (mce@tornado.be)
Wed, 19 Aug 1998 01:24:04 +0200


> I'm quite sure that it is X, some actions (fdisk -l under 2.1.113)
> crash the system under X while they run perfectly when run in

In this context, I'd like to add that yesterday I had another crash
of the kind that I described back in July under these subjects:

Solid crash of 2.1.111
Again: Solid crash of 2.1.111

This time it was with 2.115. Right after I had manually sync'ed the
machine as a safety precaution, but before the disk had completely
come to rest again. I also had a vfat ZIP disk mounted that did not
get synced in time.

Considering that for me the most visible effect is that suddenly X
is gone and replaced by randome garbage, it seems to me that indeed
there must be a link to the X server. Or at least the graphics
stuff (vesafb and friends, maybe?)

If only I knew how to trigger it on demand... IMHO this one really
should get fixed before 2.2 gets out. Right now I don't trust my
box at all.

MCE

-- 
========================================================================
M. Eyckmans (MCE)          Code of the Geeks v3.1         mce@tornado.be
GCS d+ s+:- a32 C+++$ UHLUASO+++$ P+ L+++ E--- W++ N+++ !o K w--- !O M--
 V-- PS+ PE+ Y+ PGP- t--- !5 !X R- tv- b+ DI++ D-- G++ e+++ h+(*) !r y?
========================================================================

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html