linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: remi@a2zis.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-ac8 hardlocks when going to standby
Date: Wed, 6 Jun 2001 15:10:11 +0200 (MET DST)	[thread overview]
Message-ID: <200106061310.PAA14058@harpo.it.uu.se> (raw)

On Tue, 5 Jun 2001 23:15:49 +0200, Remi Turk wrote:

>On Tue, Jun 05, 2001 at 09:37:52PM +0100, Alan Cox wrote:
>> > 2.4.5-ac[4678] all lock hard (no sysreq) when pushing my
>> > power-button (setup from the bios to go to standby) or
>> > when running apm --standby. (apm version 3.0final, RH6.2)
>> > apm --suspend works the way it should.
>> > 
>> > 2.4.5/2.4.6-pre1 don't hardlock.
>> 
>> Are you using the same build options for both
>> What machine is this - laptop ?
>
>It's not a laptop.
>Tbird 950 + Abit KT7 (KT133)
>
>UP APIC is enabled in -ac[4678] and emu10k1 is the in-kernel

and later quoted Alan as saying:

> On Tue, Jun 05, 2001 at 10:18:07PM +0100, Alan Cox wrote:
> > Thanks. UP-APIC is a real candidate for this case.

Actually, I suspect apm.c is at fault here. Suspend works,
which proves that the PM code in apic.c and nmi.c works.

But note how apm.c:send_event() ignores standby events and fails
to propagate them to PM clients. Thus, Remi's box will have an
activated local APIC and live NMI watchdog when the APM BIOS
finally gets to do whatever it does at standby.
It is fatal to have an active local APIC and NMI watchdog at suspend,
and I can only assume that this is true for standby as well.

Please try changing apm.c:send_event() to propagate standbys to PM
clients just like suspends. Does this fix the problem?

(Any why use standby in the first place? Any reason you don't
want to / can't use suspend?)

/Mikael

             reply	other threads:[~2001-06-06 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06 13:10 Mikael Pettersson [this message]
2001-06-06 17:03 ` 2.4.5-ac8 hardlocks when going to standby Remi Turk
2001-06-06 20:42   ` Remi Turk
  -- strict thread matches above, loose matches on Subject: below --
2001-06-10 14:21 Remi Turk
2001-06-07 11:00 Mikael Pettersson
2001-06-07 14:41 ` Remi Turk
2001-06-05 16:44 Remi Turk
2001-06-05 20:37 ` Alan Cox
2001-06-05 21:15   ` Remi Turk
2001-06-05 21:48     ` Joel Becker
     [not found]     ` <E157ODH-0007PX-00@the-village.bc.nu>
     [not found]       ` <20010605235346.A737@localhost.localdomain>
2001-06-06  9:32         ` Remi Turk

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=200106061310.PAA14058@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=remi@a2zis.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;
as well as URLs for NNTP newsgroup(s).