Gentoo Archives: gentoo-user

From: Nikos Chantziaras <realnc@×××××.de>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Random segfaults with kernel 2.6.27
Date: Fri, 21 Nov 2008 05:21:09
Message-Id: gg5gf9$sts$1@ger.gmane.org
In Reply to: Re: [gentoo-user] Re: Random segfaults with kernel 2.6.27 by Iain Buchanan
1 Iain Buchanan wrote:
2 > Nikos Chantziaras wrote:
3 >> Iain Buchanan wrote:
4 >
5 >>> I would definitely say this is worth looking into - not necessarily
6 >>> because the ati-drivers are bad software but because they have always
7 >>> stressed my hardware more than any open source drivers (and yielded
8 >>> better performance too).
9 >>
10 >> I have opened a bug for it, but it got closed immediately because I have
11 >> no evidence to support it. lol :P
12 >>
13 >> http://bugs.gentoo.org/show_bug.cgi?id=247860
14 >
15 > AFAIR Jer is only a wrangler (ok, "only" is not the right word, but you
16 > know what I mean) so he's likely not going to get into too much detail
17 > about the specifics of the bug wrt fglrx, ati, etc. You'd have better
18 > luck talking to a dev who deals with fglrx or the kernel, and convincing
19 > them to look at it.
20 >
21 > I know it can be frustrating to have bugs marked as INVALID, but saying
22 > "your justification for marking this as INVALID is actually the invalid
23 > thing here ... not my bug report" is probably going to get you ignored!
24 >
25 > I'm not disagreeing with you here, but I do think you will have a hard
26 > time getting hard evidence it's specifically the fglrx driver, and not
27 > some effect the fglrx driver is having on your hw...
28
29 I don't know what I can do. I'm not willing to set up a hacker kernel
30 and start debugging ATI's module. I posted that bug and also posted on
31 Phoronix to warn people to check if they're affected by this. At least,
32 that's enough for a "told you so" reply later ;D (Though I hope it's
33 just my PC that's acting up here, I don't wish anyone any kind of data
34 loss or anything.)
35
36 Other than that, I'll wait for Catalyst 8.12 and see what happens.