Re: [Bug #15096] Resume lock up -- bisected, commit 3a1151e3f124fd1a2c54b8153f510f1a7c715369

From: Rafael J. Wysocki
Date: Mon Feb 08 2010 - 14:22:00 EST


On Monday 08 February 2010, RafaÅ MiÅecki wrote:
> 2010/2/8 Stefan Bader <stefan.bader@xxxxxxxxxxxxx>:
> > Rafael J. Wysocki wrote:
> >> On Monday 08 February 2010, RafaÅ MiÅecki wrote:
> >>> 2010/2/8 Rafael J. Wysocki <rjw@xxxxxxx>:
> >>>> This message has been generated automatically as a part of a report
> >>>> of regressions introduced between 2.6.31 and 2.6.32.
> >>>>
> >>>> The following bug entry is on the current list of known regressions
> >>>> introduced between 2.6.31 and 2.6.32. Please verify if it still should
> >>>> be listed and let the tracking team know (either way).
> >>>>
> >>>>
> >>>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15096
> >>>> Subject : Resume lock up -- bisected, commit 3a1151e3f124fd1a2c54b8153f510f1a7c715369
> >>>> Submitter : RafaÅ MiÅecki <zajec5@xxxxxxxxx>
> >>>> Date : 2010-01-20 23:15 (19 days old)
> >>>> First-Bad-Commit: http://git.kernel.org/git/linus/3a1151e3f124fd1a2c54b8153f510f1a7c715369
> >>
> >> It looks like we should revert this commit, seems broken.
> >
> > Hm, otoh we had definitely people with some Asus laptops who where only be able
> > to use backlight control with it. So I would rather prefer some work around to
> > the suspend/resume problem (_DOS if I understood correctly).
>
> It's same case with my Sony VAIO. Without this I can not control
> backlight. Eventually I can hack on GPU registers directly, but I
> don't think it can be called solution.

Well, do I understand correctly that without commit
3a1151e3f124fd1a2c54b8153f510f1a7c715369 you can't control the backlight,
but with the commit applied there's a resume problem on your box?

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/