From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: 2.6.37-rc2-git4: Reported regressions 2.6.35 -> 2.6.36 Date: Thu, 18 Nov 2010 19:47:21 -0500 Message-ID: <4CE5C919.7090504@teksavvy.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux Kernel Mailing List , Maciej Rutecki , Florian Mickler , Andrew Morton , Linus Torvalds , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Linux Wireless List , DRI To: "Rafael J. Wysocki" Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On 10-11-18 06:50 PM, Rafael J. Wysocki wrote: > This message contains a list of some post-2.6.35 regressions introduced before > 2.6.36, for which there are no fixes in the mainline known to the tracking team. > If any of them have been fixed already, please let us know. > > If you know of any other unresolved post-2.6.35 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. > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=21652 > Subject : several problems with intel graphics since 2.6.36 > Submitter : Norbert Preining > Date : 2010-10-27 14:32 (23 days old) > Message-ID :<20101027143252.GA8676-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org> > References : http://marc.info/?l=linux-kernel&m=128818998630241&w=2 That one is interesting to me.. I suspect it may be the same cause as for https://bugzilla.kernel.org/show_bug.cgi?id=21952 I have one of those Samsung (N210) Netbooks here: works fine with 2.6.34 and earlier, but fails to come out of suspend on 2.6.35/2.6.36 (haven't tried 2.6.37). So perhaps add 21952 to the list, or link it to the 21652 (kind of amusing how similar the bug numbers are..). My non-Intel graphics notebook (has ATI X1400 graphics) also has a resume regression with 2.6.36. But it does work fine with 2.6.35 (and earlier, back many years). As a result, I'm stuck with 2.6.35 for the time being, and lack the time for a concerted debug effort on 2.6.36+ right now. Cheers