> On 5 Mar 1998, Ben Pfaff wrote:
>
> > I've reported this to the XFree86 people but they apparently ignored
> > the report.
>
> The XFree86 people apparently do not ignore bug reports.
>
> It is a known problem that starting the Matrox server on certain
> motherboards can hang the system in about 5% of the cases. As of Feb 98
> the reason for this problem was still unknown. Not knowing how to solve a
> problem does not mean ignoring it.
>
> Hubert
>
1. Please, I think this thread should stop as soon as possible.
2. I don't want to revive the GGI one, but I think that, if really there
are PCI stalls coming from X directly mangling the bus, they could
really be a good reason to get something like GGI inside the
kernel, instead of the suid root server which mangles the registers like
it now does
3. I'm really unsure X is guilty, since I've never seen something like
this before, and got two crashes in a line, both times after having done a
diff between a SCSI CD-reader/writer used in read mode and the backed up
directory
4. I'm not sure if this could help, but I can try and run an instrumented
server, to log its start-up activity on the DAT tape after having done
another diff, but I gave the writer to its owner, and I'm unsure if I'll
be able to trigger the problem without it.
Now, I beg all of the readers' pardon, but I still think I had to reply to
the list, since I started a thread (against my own will) which was
perceived as mourning about XFree developers. For now, I'm not going to
do other tests (and potentially wait for four long fsck) before I get an
instrumented server, but I'm ready to change my mind, if you convince me.
In all fairness, I'd rather avoid doing tests in the week-end, since I
rather prefer spending those days at home than here.
Yours,
lorenzo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu