From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Bowler Subject: Re: 2.6.34-rc5: Reported regressions from 2.6.33 Date: Fri, 23 Apr 2010 11:31:45 -0400 Message-ID: <20100423153145.GA6072@elliptictech.com> References: <20100420135636.GA10674@elliptictech.com> <201004210715.38621.rjw@sisk.pl> <20100421085739.GA2576@barney.localdomain> <20100421165758.GA23565@elliptictech.com> <20100423102338.GA3151@barney.localdomain> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20100423102338.GA3151-N6zOBCg9HoVSq9BJjBFyUp/QNRX+jHPU@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jerome Glisse Cc: "Rafael J. Wysocki" , DRI , Linux Kernel Mailing List , Linux ACPI , Andrew Morton , Kernel Testers List , Linus Torvalds , Linux PM List , Maciej Rutecki On 12:23 Fri 23 Apr , Jerome Glisse wrote: > On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote: > > OK, if the failure is due to userspace is doing Very Bad Things(tm), > > catching that seems reasonable. > > > > Nevertheless, even if it happened by luck, the result was (ostensibly) > > working programs that suddenly break once one "upgrades" to the latest > > kernel. If userspace can't be fixed before 2.6.34 is released, perhaps > > a less cryptic log message would be appropriate? > > I pushed fix into mesa for the depth issue i will look into the other > one today and likely push kernel fix. Great, thanks. I'll try out the depth fix tonight. -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)