linux-kernel - Re: [3/5] 2.6.21-rc4: known regressions (v2)

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]

Message-ID: <46068473.9020704@m3y3r.de>
Date:	Sun, 25 Mar 2007 16:17:23 +0200
From:	Thomas Meyer <thomas@...3r.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Tony Luck <tony.luck@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: [3/5] 2.6.21-rc4: known regressions (v2)

Rafael J. Wysocki schrieb:
> On Sunday, 25 March 2007 14:03, Eric W. Biederman wrote:
>   
>> Thomas Meyer <thomas@...3r.de> writes:
>>
>>     
>>> Eric W. Biederman schrieb:
>>>       
>>>> Thomas could you verify the patch below makes the problem go away
>>>> for you.
>>>>   
>>>>         
>>> The patch solves the problem. I'm writing this after the third suspend
>>> and resume cycle.
>>> msi irq stays enabled for libata device:
>>> cat /sys/devices/pci0000\:00/0000\:00\:1f.2/irq
>>> 218
>>>       
>>> The first suspend to disk is ok. The second suspend to disk has a
>>> strange behaviour:
>>> 1.) write pm image
>>> 2.) the system disable the non-boot cpus again (i guess this happens in
>>> power_down())
>>>       
>
> Yes, in kernel/power/disk.c:power_down() .
>
> Please comment out the disable_nonboot_cpus() in there and retest (but please
> test the latest Linus' tree).
>
>   
Without disable_nonboot_cpus in power_down the computer powers down
without the mysterious "wait for the next interrupt" hang.
>>> 3.) the system doesn't power down.
>>> 4.) pressing any key and the system powers down.
>>>
>>> The same is true for the third suspend cycle. Maybe an acpi problem?
>>>       
>> Sounds possible.  You could probably verify it isn't my patch but running
>> an unpatched kernel without msi support.  As I think the crash you saw should
>> only be reproducible when using devices that support msi.
>>
>> Unless I hear different I'm going to assume that this second case is a
>> completely different problem.
>>     
>
> I think it is different too.
>   
Yes, it's a different problem
-
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/