Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756952Ab0DWKX7 (ORCPT ); Fri, 23 Apr 2010 06:23:59 -0400 Received: from nox2.protox.org ([95.130.11.66]:51473 "EHLO protox.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755693Ab0DWKX5 (ORCPT ); Fri, 23 Apr 2010 06:23:57 -0400 Date: Fri, 23 Apr 2010 12:23:38 +0200 From: Jerome Glisse To: "Rafael J. Wysocki" , DRI , Linux Kernel Mailing List , Linux ACPI , Andrew Morton , Kernel Testers List , Linus Torvalds , Linux PM List , Maciej Rutecki Subject: Re: 2.6.34-rc5: Reported regressions from 2.6.33 Message-ID: <20100423102338.GA3151@barney.localdomain> References: <20100420135636.GA10674@elliptictech.com> <201004210715.38621.rjw@sisk.pl> <20100421085739.GA2576@barney.localdomain> <20100421165758.GA23565@elliptictech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100421165758.GA23565@elliptictech.com> User-Agent: Mutt/1.5.20 (2009-12-10) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1756 Lines: 42 On Wed, Apr 21, 2010 at 12:57:58PM -0400, Nick Bowler wrote: > On Wed, Apr 21, 2010 at 07:15:38AM +0200, Rafael J. Wysocki wrote: > > On Tuesday 20 April 2010, Nick Bowler wrote: > > > Please list these two similar regressions from 2.6.33 in the r600 DRM: > > > > > > * r600 CS checker rejects GL_DEPTH_TEST w/o depth buffer: > > > https://bugs.freedesktop.org/show_bug.cgi?id=27571 > > > > > > * r600 CS checker rejects narrow FBO renderbuffers: > > > https://bugs.freedesktop.org/show_bug.cgi?id=27609 > > > > Do you want to me to add them as one entry or as two separate bugs? > > As upstream doesn't consider the first to be a kernel issue, I guess you > should just list the second. > > On 10:57 Wed 21 Apr , Jerome Glisse wrote: > > First one is userspace bug, i need to look into the second one. > > ie we were lucky the hw didn't lockup without depth buffer and > > depth test enabled. > > 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? > > -- > Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/) I pushed fix into mesa for the depth issue i will look into the other one today and likely push kernel fix. Cheers, Jerome -- 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/