From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: Bug in PCI core Date: Fri, 13 Oct 2006 18:09:09 +0100 Message-ID: <1160759349.25218.62.camel@localhost.localdomain> References: <1160753187.25218.52.camel@localhost.localdomain> <1160753390.3000.494.camel@laptopd505.fenrus.org> <1160755562.25218.60.camel@localhost.localdomain> <1160757260.26091.115.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1160757260.26091.115.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Adam Belay Cc: linux-pci@atrey.karlin.mff.cuni.cz, Linux-pm mailing list , Kernel development list , Arjan van de Ven List-Id: linux-pm@vger.kernel.org Ar Gwe, 2006-10-13 am 12:34 -0400, ysgrifennodd Adam Belay: > I agree this needs to be fixed. However, as I previously mentioned, > this isn't the right place to attack the problem. Remember, this wasn't > originally a kernel regression. Rather it's a workaround for a known It's a kernel regression. It used to be reliable to read X resource addresses at any time. > Finally, it's worth noting that this issue is really a corner-case, and > in most systems it's extremely rare that even incorrect userspace apps > would have any issue. Except just occasionally and randomly in the field, probably almost undebuggable and irreproducable - the very worst conceivable kind of bug.