From: Pavel Machek <pavel@ucw.cz>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: any cpu hotplug changes in 2.6.24-current-git?
Date: Thu, 7 Feb 2008 10:16:30 +0100 [thread overview]
Message-ID: <20080207091630.GA1816@elf.ucw.cz> (raw)
In-Reply-To: <47AA558F.7030006@gmail.com>
On Wed 2008-02-06 19:49:19, Gregory Haskins wrote:
> Pavel Machek wrote:
>> Hi!
>>
>>
>>>> Are there any recent changes in cpu hotplug? I have suspend (random)
>>>> problems, nosmp seems to fix it, and last messages in the "it hangs"
>>>> case are from cpu hotplug...
>>>>
>>
>>
>>> Can you send along your cpuinfo?
>>>
>>
>> It happened on more than one machine, one cpuinfo is:
>>
> Ah, ok. This one is a C2D, correct? The only reason I asked is that
I don't know what "C2D" means... core2duo? Yes, this is core2duo.
> someone was reporting an s2ram problem on P4s on some of that root-domain
> logic I submitted a little while ago (and was merged in .25), whereas C2D
> seemed fine. That doesn't mean anything here, really. The problem could
> still be my code, or it might be unrelated. I was just wondering if you
> also had a P4 on the troubled systems.
>
> So is your problem on suspend or resume? (or both?) (I know you mentioned
> it was random problems, but I wasn't sure if you could qualify that
> further)
It dies at suspend, always in same place, but not always.
OTOH last few suspends worked for me, not sure what changed...
> Any info you can provide will be appreciated.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-02-07 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 12:58 any cpu hotplug changes in 2.6.24-current-git? Pavel Machek
2008-02-06 14:34 ` Rafael J. Wysocki
2008-02-06 15:25 ` Gregory Haskins
2008-02-06 22:44 ` Pavel Machek
2008-02-07 0:49 ` Gregory Haskins
2008-02-07 9:16 ` Pavel Machek [this message]
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=20080207091630.GA1816@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=gregory.haskins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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