From: Andreas Hartmann <andihartmann@freenet.de>
To: Kernel-Mailingliste <linux-kernel@vger.kernel.org>
Subject: Re: Again: Linux 2.4.x and AMD Athlon
Date: Sun, 15 Jul 2001 09:09:20 +0200 [thread overview]
Message-ID: <3B5141A0.2B98693@athlon.maya.org> (raw)
Hello all,
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!
Some more experiences with AMD and X-related crashes:
-> I've an Athlon 800 on a Epox EP7KXA Mobo (686A) with 512MB RAM and no
nVIDIA graphics card, but ATI XPERT 2000.
I've got similar problems with 2.4.x-kernels and I would be very glad,
if the cause could be found. The problem is more than half of a year
old!
I posted it in this list some time ago (more than once) - nobody seemed
to be interested. I posted it 2 times to the X bug list - no interest.
But as I can see now, the problem seems to be greater than I thoght.
Therefore I write here some of my latest experiences:
# X 4.1 (if I remember right) and 2.4.6 -> a lot off solid crashes (even
pinging the machine didn't work) while starting X, no matter if DRI was
turned on or off; no matter if agp was loaded or not. Unuseable.
# X-CVS and 2.4.6ac2 eg. is working fine - with DRI turned on - I didn't
test it without DRI.
# Before, I tried to run X 4.1 and ac-Kernels. They have been crashing
too as described above. That's why I'm using X CVS.
# If I try to run X CVS and vanilla 2.4.6, I'm getting blinking screens
after some restarts of X or after long working with X. It's unuseable,
too.
For me, it seems to be not a nVIDIA related problem.
The question for me is:
where are the differences between X CVS / X 4.1 and Vanilla / ac-patches
- and there combinations.
Why is the combination 2.4.6ac2 or the ac-patches before and X CVS
(about 4 weeks old; not DRI-CVS; but they have been merged as far as I
know) working for me without any problems?
Did you try this combination too? It would bee interersting if it would
work for you too!
Regards,
Andreas Hartmann
next reply other threads:[~2001-07-15 7:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-15 7:09 Andreas Hartmann [this message]
2001-07-16 2:19 ` Again: Linux 2.4.x and AMD Athlon Stephen Degler
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 8:50 David Balazic
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 11:12 Thomas Foerster
2001-07-13 12:34 ` Alan Cox
2001-07-13 22:05 ` Stefan Jaschke
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=3B5141A0.2B98693@athlon.maya.org \
--to=andihartmann@freenet.de \
--cc=linux-kernel@vger.kernel.org \
/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.