Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751698AbWIVEiF (ORCPT ); Fri, 22 Sep 2006 00:38:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751700AbWIVEiF (ORCPT ); Fri, 22 Sep 2006 00:38:05 -0400 Received: from solarneutrino.net ([66.199.224.43]:17157 "EHLO tau.solarneutrino.net") by vger.kernel.org with ESMTP id S1751698AbWIVEiD (ORCPT ); Fri, 22 Sep 2006 00:38:03 -0400 Date: Fri, 22 Sep 2006 00:38:01 -0400 To: Stephen Olander Waters Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net Subject: R200 lockup (was Re: DRI/X error resolution) Message-ID: <20060922043801.GE16939@tau.solarneutrino.net> References: <1158898988.3280.8.camel@ix> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1158898988.3280.8.camel@ix> User-Agent: Mutt/1.5.9i From: Ryan Richter Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 799 Lines: 23 On Thu, Sep 21, 2006 at 11:23:08PM -0500, Stephen Olander Waters wrote: > Hey, > > Did they ever fix that bug you reported here? > http://lkml.org/lkml/2005/5/11/121 > > I'm having the same problem! Argh! No, sad to say it still happens to us too. Argh is right! I'll cc this to dri-devel and lkml in case anyone wants to try hunting the bug again. FWIW, I'm still seeing the ioctl(5, 0x6444, 0) / SIGALARM behavior I reported originally. This has continued to happen regularly with all 2.6 kernels up to 2.6.17.6 and Xfree/X.org up to 6.9. -ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/