From: Thomas Meyer <thomas@m3y3r.de>
To: Milan Broz <mbroz@redhat.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: SwSusp to disk doesn't work - Try 2
Date: Sun, 11 Mar 2007 22:02:55 +0100 [thread overview]
Message-ID: <45F46E7F.8020703@m3y3r.de> (raw)
In-Reply-To: <45F46D33.1050808@redhat.com>
Milan Broz schrieb:
> Thomas Meyer napsal(a):
>
>> 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.
>>
>
> Hmmmm, both variants (nohz=off or recompiled kernel without NO_HZ) works for me.
>
> Milan
>
I got a working config:
Without hrtimers and without nohz it is working!
With hrtimers and without nohz it is not working
With hrtimers and with nohz it is not working
Now i want to test: without hrtimers and with nohz.
next prev parent reply other threads:[~2007-03-11 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 18:08 SwSusp to disk doesn't work - Try 2 Thomas Meyer
2007-03-11 18:26 ` Rafael J. Wysocki
2007-03-11 18:37 ` Thomas Meyer
2007-03-11 19:27 ` Rafael J. Wysocki
2007-03-11 19:04 ` Milan Broz
2007-03-11 19:16 ` Thomas Meyer
2007-03-11 19:50 ` Rafael J. Wysocki
2007-03-11 20:04 ` Thomas Meyer
2007-03-11 19:38 ` Rafael J. Wysocki
2007-03-11 20:23 ` Milan Broz
2007-03-11 20:32 ` Rafael J. Wysocki
2007-03-11 20:28 ` Thomas Meyer
2007-03-11 20:45 ` Rafael J. Wysocki
2007-03-11 20:49 ` Thomas Meyer
2007-03-11 20:57 ` Milan Broz
2007-03-11 21:02 ` Thomas Meyer [this message]
2007-03-11 21:09 ` Rafael J. Wysocki
2007-03-11 21:56 ` Thomas Gleixner
2007-03-11 21:57 ` Thomas Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F46E7F.8020703@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox