From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suspend on Dell D420
Date: Sat, 5 Aug 2006 11:08:00 +0200 [thread overview]
Message-ID: <200608051108.01180.rjw@sisk.pl> (raw)
In-Reply-To: <20060805082321.GB27129@uio.no>
On Saturday 05 August 2006 10:23, Steinar H. Gunderson wrote:
> On Sat, Aug 05, 2006 at 01:26:56AM +0200, Rafael J. Wysocki wrote:
> > Because the non-boot CPUs are taken off early, before anything else, and the
> > system is effectively non-SMP during the entire suspend-resume cycle
> > (well, almost). If SMP-related things go wrong during the suspend, CPU
> > hotplug is the first suspect. ;-)
>
> Well, it seems to work fine during the suspend phase, at least, and it also
> seems to work well during normal use:
>
> fugl:~# echo 0 > /sys/devices/system/cpu/cpu1/online
> fugl:~# echo 1 > /sys/devices/system/cpu/cpu1/online
>
> FWIW, there is an error in dmesg afterwards, though:
>
> ===
> CPU 1 is now offline
> SMP alternatives: switching to UP code
> SMP alternatives: switching to SMP code
> Booting processor 1/1 eip 3000
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 2394.85 BogoMIPS (lpj=4789709)
> CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
> CPU: After vendor identify, caps: bfe9fbff 00100000 00000000 00000000 0000c1a9 00000000 00000000
> monitor/mwait feature present.
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 2048K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> CPU: After all inits, caps: bfe9fbff 00100000 00000000 00000140 0000c1a9 00000000 00000000
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#1.
> CPU1: Intel Genuine Intel(R) CPU U2500 @ 1.20GHz stepping 08
> APIC error on CPU1: 00(40)
> ===
>
> No idea whether it's related. FWIW, resume didn't work with maxcpus=1 on boot
> either, so I'm not really sure how related it is.
Hm, could you please try it with a non-SMP kernel?
Rafael
next prev parent reply other threads:[~2006-08-05 9:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 16:23 Steinar H. Gunderson
2006-08-04 21:27 ` Rafael J. Wysocki
2006-08-04 22:17 ` Andrew Morton
2006-08-04 23:26 ` Rafael J. Wysocki
2006-08-05 8:23 ` Steinar H. Gunderson
2006-08-05 9:08 ` Rafael J. Wysocki [this message]
2006-08-06 11:50 ` Steinar H. Gunderson
2006-08-06 23:10 ` Pavel Machek
2006-08-06 23:15 ` Steinar H. Gunderson
2006-08-17 15:00 ` Pavel Machek
2006-08-08 14:04 ` Rafael J. Wysocki
2006-08-08 15:01 ` Steinar H. Gunderson
2006-08-08 15:41 ` Rafael J. Wysocki
2006-08-09 0:21 ` Pavel Machek
2006-08-09 8:44 ` Steinar H. Gunderson
2006-08-09 9:02 ` Pavel Machek
2006-08-09 9:05 ` Steinar H. Gunderson
2006-08-09 9:08 ` Pavel Machek
2006-08-09 9:17 ` Steinar H. Gunderson
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=200608051108.01180.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=sgunderson@bigfoot.com \
/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
Powered by JetHome