From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: 2.6.38-rc3-git1: Reported regressions 2.6.36 -> 2.6.37 Date: Thu, 03 Feb 2011 17:11:31 +0100 Message-ID: References: <20110203112316.GA3718@linux-yscl.site> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: netdev-owner@vger.kernel.org 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 List-Id: linux-scsi@vger.kernel.org At Thu, 3 Feb 2011 07:42:05 -0800, Linus Torvalds wrote: >=20 > On Thu, Feb 3, 2011 at 3:23 AM, Carlos R. Mafra = wrote: > > On Thu =C2=A03.Feb'11 at =C2=A01:03:41 +0100, Rafael J. Wysocki wro= te: > >> > >> If you know of any other unresolved post-2.6.36 regressions, pleas= e let us know > >> either and we'll add them to the list. =C2=A0Also, please let us k= now 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). >=20 > Ok, added Keith and Dave to the cc, since they are the signers of tha= t commit. >=20 > > After some time, I also ended up finding an earlier report in the k= ernel bugzilla > > which I think is the same regression (it was bisected to the same c= ommit): > > > > https://bugzilla.kernel.org/show_bug.cgi?id=3D24982 > > > > 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. >=20 > 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