linux-kernel - Re: SwSusp to disk doesn't work

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:	Sun, 11 Mar 2007 21:28:16 +0100
From:	Thomas Meyer <thomas@...3r.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Milan Broz <mbroz@...hat.com>, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@....cz>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: SwSusp to disk doesn't work - Try 2

Rafael J. Wysocki schrieb:
> On Sunday, 11 March 2007 21:23, Milan Broz wrote:
>   
>> Rafael J. Wysocki:
>>     
>>> Ah, NO_HZ.  Thomas Gleixner's address added to the Cc list.
>>>
>>>       
>>>> short printk trace 
>>>>
>>>> enable_nonboot_cpus
>>>>  _cpu_up
>>>>   raw_notifier_callchain (CPU_UP_PREPARE)
>>>>     ...
>>>>     update_sched_domains
>>>>      detach_destroy_domains
>>>>        [waits here] --> synchronize_sched (==synchronize_rcu)
>>>>         
>>> Well, I think the call to wait_for_completion() does not return, probably
>>> because the task supposed to complete the completion is frozen at this
>>> point.  Can you please try to confirm that it gets stuck on
>>> wait_for_completion() in synchronize_rcu()?
>>>       
>> Yes, it's in wait_for_completion() in synchronize_rcu().
>> As noted in some previous mail, it will wake up after
>> event - key press etc.
>>
>> Patch in http://lkml.org/lkml/2007/3/7/255 solves different problem.
>> I added it to my quilt and applied anyway -> no change.
>>     
>
> Does the problem go away if NO_HZ is unset?
>   

i tried to boot with nohz=off, but the problem did persist.

-
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/