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 1L3OTL-00069T-Ks for garchives@archives.gentoo.org; Fri, 21 Nov 2008 05:22:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0A57EE0234; Fri, 21 Nov 2008 05:22:28 +0000 (UTC) Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by pigeon.gentoo.org (Postfix) with ESMTP id D47A1E0234 for ; Fri, 21 Nov 2008 05:22:27 +0000 (UTC) Received: by gxk10 with SMTP id 10so1312367gxk.10 for ; Thu, 20 Nov 2008 21:22:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=kg/Flgcd7cDGSe5NGuJYNyIoXBgf+m1FePhoQ3fa7x4=; b=WBt8pN+uCc1Wnm3z5DwPPfVj07sGow/1tqvqVjPhefbmLw/tt3nPYY51Ik1rnvSHiX tSswb8reHNsFlouIlUGSwvTkKDdiHQu5a82ggRg1Gt4r115TVjhL1u/VDDmK0anQp34i P7LyngUcCZyW+a3rvPVjCVzNMKjlVQHZSZtYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=UJY15xE+dZM5IbVssiBPh1gMwuYqqXsH8fD06gif6ByRrLybkohvtavZ0ShoxfNCvZ y8637k8rj2ve1u5oiq2m3LlMd0eXcmTH4yJ3ekMA3ySvd7y7d++iONphQUpVWm8WHCi5 9zVR1xo5VjMokG5+/fL3PVe3lrcAagu0djH0c= Received: by 10.150.123.16 with SMTP id v16mr271620ybc.55.1227244945814; Thu, 20 Nov 2008 21:22:25 -0800 (PST) Received: by 10.151.137.13 with HTTP; Thu, 20 Nov 2008 21:22:25 -0800 (PST) Message-ID: <350fc7cf0811202122t6eab1543u3c524b784cb8aed2@mail.gmail.com> Date: Thu, 20 Nov 2008 21:22:25 -0800 From: "Andrey Falko" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Random segfaults with kernel 2.6.27 In-Reply-To: <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: multipart/alternative; boundary="----=_Part_102185_25541962.1227244945813" References: <350fc7cf0811201707y638930ddy4f2cc9bd4caabab7@mail.gmail.com> <350fc7cf0811201820t5fd8c470q2af0639d4c59e232@mail.gmail.com> <492630AB.4070402@netspace.net.au> <49264129.8090805@netspace.net.au> X-Archives-Salt: fb154035-0148-41c6-9048-0b68cbbe1ef8 X-Archives-Hash: e87a5189aad9d1d88a81e6d8710447c7 ------=_Part_102185_25541962.1227244945813 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Nov 20, 2008 at 9:03 PM, Iain Buchanan wrote: > Nikos Chantziaras wrote: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 agree. Even if this is a bug, no open source developer could be qualified to fix it because fgrlx is closed source. If you can, report this to ATI, otherwise, you will have to live with the problem or use open source drivers. ------=_Part_102185_25541962.1227244945813 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Nov 20, 2008 at 9:03 PM, Iain Buchanan <iaindb@netspace.net.au> wrote:
Nikos Chantziaras wrote:
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 agree. Even if this is a bug, no open source developer could be qualified to fix it because fgrlx is closed source. If you can, report this to ATI, otherwise, you will have to live with the problem or use open source drivers.
------=_Part_102185_25541962.1227244945813--