Return-path: Received: from cantor2.suse.de ([195.135.220.15]:55758 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756235Ab1BCQLc (ORCPT ); Thu, 3 Feb 2011 11:11:32 -0500 Date: Thu, 03 Feb 2011 17:11:31 +0100 Message-ID: From: Takashi Iwai To: Linus Torvalds Cc: "Carlos R. Mafra" , Keith Packard , Dave Airlie , "Rafael J. Wysocki" , Linux Kernel Mailing List , Maciej Rutecki , Florian Mickler , Andrew Morton , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Linux Wireless List , DRI Subject: Re: 2.6.38-rc3-git1: Reported regressions 2.6.36 -> 2.6.37 In-Reply-To: References: <20110203112316.GA3718@linux-yscl.site> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: At Thu, 3 Feb 2011 07:42:05 -0800, Linus Torvalds wrote: > > On Thu, Feb 3, 2011 at 3:23 AM, Carlos R. Mafra wrote: > > On Thu  3.Feb'11 at  1:03:41 +0100, Rafael J. Wysocki wrote: > >> > >> If you know of any other unresolved post-2.6.36 regressions, please let us know > >> either and we'll add them to the list.  Also, please let us know if any > >> of the entries below are invalid. > > > > I'm sorry if I'm overlooking something, but as far as I can see the regression > > reported here: > > > > https://lkml.org/lkml/2011/1/24/457 > > > > is not in the list (update on that report: reverting that commit on top of > > 2.6.37 fixes the issue). > > Ok, added Keith and Dave to the cc, since they are the signers of that commit. > > > After some time, I also ended up finding an earlier report in the kernel bugzilla > > which I think is the same regression (it was bisected to the same commit): > > > > https://bugzilla.kernel.org/show_bug.cgi?id=24982 > > > > but I do not see it in the list either, even though it's marked as a > > regression in the bugzilla. > > > > The issue was also present in 2.6.38-rc2 last time I tested. > > Just to confirm, can you also check -rc3? I'm pretty sure nothing has > changed, but there were a few drm patches after -rc2, so it's alsways > good to double-check. The problem I reported in the bugzilla above is still present in 2.6.38-rc3. I'm pretty sure that's the same issue as Carlos' case. thanks, Takashi