lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 08 Feb 2010 20:32:10 +0100
From:	Stefan Bader <stefan.bader@...onical.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Rafał Miłecki <zajec5@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Len Brown <len.brown@...el.com>,
	Zhang Rui <rui.zhang@...el.com>
Subject: Re: [Bug #15096] Resume lock up -- bisected, commit 3a1151e3f124fd1a2c54b8153f510f1a7c715369

Rafael J. Wysocki wrote:
> On Monday 08 February 2010, Rafał Miłecki wrote:
>> 2010/2/8 Stefan Bader <stefan.bader@...onical.com>:
>>> Rafael J. Wysocki wrote:
>>>> On Monday 08 February 2010, Rafał Miłecki wrote:
>>>>> 2010/2/8 Rafael J. Wysocki <rjw@...k.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@...il.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.
>>> 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

Rafał can correct me. I would phrase it that way that without the bisected
patch, there is no backlight control. And because there is with it, we hit the
next BIOS bug because the backlight driver now tries to correctly bring it back
on resume.

Stefan

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ