public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.25-rc4
Date: Sun, 22 Feb 2004 09:41:53 +0100	[thread overview]
Message-ID: <20040222084153.GA20189@alpha.home.local> (raw)
In-Reply-To: <20040220224836.GA32153@elf.ucw.cz>

Hi Pavel,

On Fri, Feb 20, 2004 at 11:48:36PM +0100, Pavel Machek wrote:
> > 
> > Your fix looks ok. I dont think calling acpi_system_save_state(S5) can
> > cause any breakage. Len?
> 
> I bet it will create "machine will reboot instead of poweroff" on some
> strange machine.... Perhaps it fixes more machines than it breaks, but
> it will probably break some.

This is interesting. Do you have an idea about what could break exactly ?
In my case, I have noticed two things :
  - if I disable local APIC, the standard code works
  - if I enable local APIC, I need the patch above.

So perhaps it would be enough to disable local APIC instead of calling this
function ?

BTW, I have retested on the Supermicro server which didn't want to stop
previously. It's a P4 HT. Interestingly, with the new code, it displays :
  Power Down
  Trying to free free IRQ 23

IRQ 23 is assigned to eth0 (e1000). If I rmmod e1000 before, then it stops
correctly. And if I boot it with 'nosmp', it stops correcly both with new
and older code.

So I suspect that sending PM events is not exactly SMP safe, and that this
system cannot power off in SMP for an unknown reason. Perhaps as with APM,
some parts of the code need to be executed by CPU0 only ? Or perhaps when
I booted with 'nosmp', APIC was disabled ? (I didn't notice particularly).

I can do tests on my notebook, but I'm mainly lacking ideas now. I will
try to disable APIC only, just in case. And if it doesn't work on the
P4 HT, I can try to stop every CPU>0. If we don't find an universal solution,
it might indicate that we need another boot option to adapt to different
hardware :-(

Regards,
Willy


  reply	other threads:[~2004-02-22  8:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18  5:11 Linux 2.4.25-rc4 Marcelo Tosatti
2004-02-18  5:57 ` Willy Tarreau
2004-02-18 14:34   ` Marcelo Tosatti
2004-02-18 21:27     ` Willy Tarreau
2004-02-20 22:48     ` Pavel Machek
2004-02-22  8:41       ` Willy Tarreau [this message]
2004-02-22 22:03         ` Pavel Machek
2004-02-18 19:17 ` Hilko Bengen
2004-02-19 19:39   ` Marcelo Tosatti
2004-02-19 23:28     ` Hilko Bengen

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=20040222084153.GA20189@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=pavel@ucw.cz \
    /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