From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Random segfaults with kernel 2.6.27
Date: Fri, 21 Nov 2008 04:36:38 +0200 [thread overview]
Message-ID: <gg56ro$a7s$1@ger.gmane.org> (raw)
In-Reply-To: <350fc7cf0811201820t5fd8c470q2af0639d4c59e232@mail.gmail.com>
Andrey Falko wrote:
> On 11/20/08, *Nikos Chantziaras* <realnc@arcor.de
> <mailto:realnc@arcor.de>> wrote:
>
> As it happens, upgrading to kernel 2.6.27 was not the only change; I
> switched from xf86-video-radeonhd to the proprietary ATI Catalyst
> drivers. Didn't think that this has anything to do with it though.
>
>
> I have a hunch that this is the problem. Have you tried 2.6.27 without
> the proprietary ATI drivers?
I'll be running tests on this with various combinations
(2.6.26/2.6.27/Catalyst/open source radeonhd) and see what happens.
Re-emerging a bunch of stuff should do it.
> This is the first thing I would suspect
> because ATI drivers are not reputed --- or so I believe --- for being
> the best quality software out there.
They are reputed to be one of the most broken (from packaging, install
scripts up to the actual binary blobs) ever produced ;P Too bad they're
the *only* choice on modern cards. No 3D (or even accelerated 2D)
support with any open source driver for HD4xxx series cards. It's one
of those things you hate to the bone but can't do without due to AMD's
refusal to open source them so we can fix them.
> Either way, we need to eliminate as
> many factors as possible and one of these factors is your ATI driver
> change. I don't know much about Prime95, but if it won't simulate a
> subtlety in your video drivers, especially how proprietary ATI drivers
> will play with kernel 2.6.27.
Yes, Prime doesn't touch the GPU. It stresses CPU, northbridge and RAM
only.
next prev parent reply other threads:[~2008-11-21 2:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 0:52 [gentoo-user] Random segfaults with kernel 2.6.27 Nikos Chantziaras
2008-11-21 1:07 ` Andrey Falko
2008-11-21 1:24 ` [gentoo-user] " Nikos Chantziaras
2008-11-21 1:58 ` Dale
2008-11-21 2:27 ` Nikos Chantziaras
2008-11-21 5:39 ` Dale
2008-11-21 2:20 ` Andrey Falko
2008-11-21 2:36 ` Nikos Chantziaras [this message]
2008-11-21 3:16 ` Nikos Chantziaras
2008-11-21 3:51 ` Mike
2008-11-21 3:59 ` Mike
2008-11-21 3:53 ` Iain Buchanan
2008-11-21 4:39 ` Nikos Chantziaras
2008-11-21 5:03 ` Iain Buchanan
2008-11-21 5:20 ` Nikos Chantziaras
2008-11-21 5:22 ` Andrey Falko
2008-11-21 5:50 ` Nikos Chantziaras
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='gg56ro$a7s$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox