From: s-jaschke@t-online.de (Stefan Jaschke)
To: Thomas Foerster <puckwork@madz.net>
Cc: "lkml" <linux-kernel@vger.kernel.org>
Subject: Re: Again: Linux 2.4.x and AMD Athlon
Date: Sat, 14 Jul 2001 00:05:42 +0200 [thread overview]
Message-ID: <01071400054201.30655@antares> (raw)
In-Reply-To: <20010713111652Z267032-720+1961@vger.kernel.org>
In-Reply-To: <20010713111652Z267032-720+1961@vger.kernel.org>
On Friday 13 July 2001 13:12, Thomas Foerster wrote:
> I got only one oops in inode.c (forget the actual line number)
> The rest are random application crashes on XFree 4.0.3 (GeForce2 GTS, nVidi
> DRI (older version)) The System NEVER hangs, only applications crash!
So this is off-topic, but anyway here is my experience:
The binary-only Nvidia driver consistently deep-froze my system,
i.e. screen and keyboard were dead. The system log showed, however,
that the system was still alive. Just forget the Nvidia driver...
My 2c,
Stefan
--
Stefan R. Jaschke <stefan@jaschke-net.de>
http://www.jaschke-net.de
next prev parent reply other threads:[~2001-07-13 22:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 11:12 Again: Linux 2.4.x and AMD Athlon Thomas Foerster
2001-07-13 12:34 ` Alan Cox
2001-07-13 22:05 ` Stefan Jaschke [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 8:50 David Balazic
2001-07-15 7:09 Andreas Hartmann
2001-07-16 2:19 ` Stephen Degler
2001-07-14 19:54 Gabriel Friedmann
2001-07-14 20:04 ` Alan Cox
2001-07-15 0:51 ` Luigi Genoni
2001-07-13 12:19 Thomas Foerster
2001-07-13 7:00 Thomas Foerster
2001-07-13 10:42 ` Alan Cox
2001-07-12 21:53 Kenneth Vestergaard Schmidt
2001-07-13 11:13 ` Wilfried Weissmann
2001-07-12 7:15 Thomas Foerster
2001-07-12 19:16 ` Alan Cox
2001-07-13 2:31 ` Benjamin C.R. LaHaise
2001-07-13 8:52 ` Joerg Schmitz-Linneweber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01071400054201.30655@antares \
--to=s-jaschke@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=puckwork@madz.net \
--cc=stefan@jaschke-net.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.