From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L3OS5-0005zO-3G for garchives@archives.gentoo.org; Fri, 21 Nov 2008 05:21:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68E89E05BE; Fri, 21 Nov 2008 05:21:07 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 0F938E05BE for ; Fri, 21 Nov 2008 05:21:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id DA554643FE for ; Fri, 21 Nov 2008 05:21:04 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.461 X-Spam-Level: X-Spam-Status: No, score=-3.461 required=5.5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pzYcueP18uI for ; Fri, 21 Nov 2008 05:20:58 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 0959F6433B for ; Fri, 21 Nov 2008 05:20:57 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L3ORo-0001O9-L9 for gentoo-user@gentoo.org; Fri, 21 Nov 2008 05:20:52 +0000 Received: from athedsl-4376400.home.otenet.gr ([79.130.55.64]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Nov 2008 05:20:52 +0000 Received: from realnc by athedsl-4376400.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Nov 2008 05:20:52 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: Random segfaults with kernel 2.6.27 Date: Fri, 21 Nov 2008 07:20:39 +0200 Message-ID: References: <350fc7cf0811201707y638930ddy4f2cc9bd4caabab7@mail.gmail.com> <350fc7cf0811201820t5fd8c470q2af0639d4c59e232@mail.gmail.com> <492630AB.4070402@netspace.net.au> <49264129.8090805@netspace.net.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: athedsl-4376400.home.otenet.gr User-Agent: Thunderbird 2.0.0.18 (X11/20081121) In-Reply-To: <49264129.8090805@netspace.net.au> Sender: news X-Archives-Salt: 438984d9-ce4f-42a6-942d-7534b0aadd6f X-Archives-Hash: 3fc1bae2b8bc2899c12d335b1894f09c Iain Buchanan wrote: > Nikos Chantziaras wrote: >> Iain Buchanan wrote: > >>> I would definitely say this is worth looking into - not necessarily >>> because the ati-drivers are bad software but because they have always >>> stressed my hardware more than any open source drivers (and yielded >>> better performance too). >> >> I have opened a bug for it, but it got closed immediately because I have >> no evidence to support it. lol :P >> >> http://bugs.gentoo.org/show_bug.cgi?id=247860 > > AFAIR Jer is only a wrangler (ok, "only" is not the right word, but you > know what I mean) so he's likely not going to get into too much detail > about the specifics of the bug wrt fglrx, ati, etc. You'd have better > luck talking to a dev who deals with fglrx or the kernel, and convincing > them to look at it. > > I know it can be frustrating to have bugs marked as INVALID, but saying > "your justification for marking this as INVALID is actually the invalid > thing here ... not my bug report" is probably going to get you ignored! > > I'm not disagreeing with you here, but I do think you will have a hard > time getting hard evidence it's specifically the fglrx driver, and not > some effect the fglrx driver is having on your hw... I don't know what I can do. I'm not willing to set up a hacker kernel and start debugging ATI's module. I posted that bug and also posted on Phoronix to warn people to check if they're affected by this. At least, that's enough for a "told you so" reply later ;D (Though I hope it's just my PC that's acting up here, I don't wish anyone any kind of data loss or anything.) Other than that, I'll wait for Catalyst 8.12 and see what happens.