From: Pavel Machek <pavel@ucw.cz>
To: Huw Rogers <count0@localnet.com>
Cc: linux-kernel@vger.kernel.org, linux-laptop@mobilix.org
Subject: Re: 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0
Date: Tue, 27 Jan 2004 09:39:36 +0100 [thread overview]
Message-ID: <20040127083936.GA18246@elf.ucw.cz> (raw)
In-Reply-To: <20040124233749.5637.COUNT0@localnet.com>
Hi!
> irqbalance just locks up the machine totally, hard power-off needed, no
> traces in the logs. Probably some issue (race?) with it writing to
> /proc/irq/X/smp_affinity. And how is irqbalance supposed to play with
> kirqd anyway? Grepping this list and others doesn't give any kind of an
> answer. But disabling it gives all interrupts to cpu0 (looking at
> /proc/interrupts). kirqd apparently only balances between CPU packages,
> not between HT siblings (info gleaned from this list).
>
> Anyway, sleep/suspend/standby functionality (important to most laptop
> users, need to close the lid and go): This checkin to
> kernel/power/main.c seems to disable suspend with SMP (!?):
>
> --- 1.3/kernel/power/main.c Sat Jan 24 20:44:47 2004
> +++ 1.4/kernel/power/main.c Sat Jan 24 20:44:47 2004
> @@ -172,6 +172,12 @@
> if (down_trylock(&pm_sem))
> return -EBUSY;
>
> + /* Suspend is hard to get right on SMP. */
> + if (num_online_cpus() != 1) {
> + error = -EPERM;
> + goto Unlock;
> + }
> +
> if ((error = suspend_prepare(state)))
> goto Unlock;
>
> ... which, given the prevalence of hyperthreaded CPUs on laptops, is
> fighting a trend. I backed out the above with a #if 0 then tried echo -n
> 1>/proc/acpi/sleep again. This time I got:
Well, no sleep developers have SMP or HT machines, AFAICT.
If you back that out... well you are on your own.
> A lot of effort is going into swsusp/pmdisk - but a lot of laptop users
> prefer S1 to S4, as it's faster and more reliable. It'd be nice to see a
> simpler "spin down the hard drive, reduce CPU clock speed to a minimum,
> and power down display/ether/wireless/usb/PCMCIA" working ahead of
> hibernation.
As far as I can see, noone is interested in S1. If you want to help
with it... [There's no need to stop tasks/stop devices on non-broken
hardware. Unfortunately there's a lot of broken hw out there, so I'm
not sure we can do it by default.]
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-27 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 5:26 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0 Huw Rogers
2004-01-25 15:28 ` Zwane Mwaikambo
2004-01-26 23:33 ` bill davidsen
2004-01-27 8:39 ` Pavel Machek [this message]
2004-01-27 15:38 ` Bart Samwel
2004-01-27 19:30 ` Nigel Cunningham
[not found] ` <37778.199.172.169.20.1075236597.squirrel@webmail.localnet.com>
2004-02-01 21:05 ` APM good, ACPI bad (2.6.2-rc1 / p4 HT / Uniwill N258SA0) Huw Rogers
2004-02-01 22:46 ` Pavel Machek
2004-02-17 2:26 ` 2.6.3-rc3-mm1 - COMPILE FAILURE Huw Rogers
2004-01-27 20:58 ` 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0 Pavel Machek
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=20040127083936.GA18246@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=count0@localnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-laptop@mobilix.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