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

Rafał Miłecki
2010-02-08T19:31:13Z

W dniu 8 lutego 2010 20:24 użytkownik Rafael J. Wysocki <rjw@sisk.pl> napisał:
> On Monday 08 February 2010, Rafał Miłecki wrote:
>> W dniu 8 lutego 2010 11:56 użytkownik Rafael J. Wysocki <rjw@sisk.pl> napisał:
>> > On Monday 08 February 2010, Rafał Miłecki wrote:
>> >> 2010/2/8 Rafael J. Wysocki <rjw@sisk.pl>:
>> >> > 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@gmail.com>
>> >> > 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.
>> >
>> > Anyway, I'll do my best to have a look at this bug later today.
>>
>> In such case I'd prefer to add "broken_DOS" flag for devices that were
>> enabled by this patch. We could avoid restoring backlight on resume
>> for broken_DOS then and maybe just update brightness to current value.
>
> Or perhaps we can try to restore the backlight at a different place.

I wanted to find out what causes this lock up by syncing modules
resume or putting some delays. See bug report of my question.
Unfortunately didn't get answer.

--
Rafał