From: Mikael Pettersson <mikpe@csd.uu.se>
To: David Woodhouse <dwmw2@infradead.org>
Cc: georgn@somanetworks.com, linux-kernel@vger.kernel.org
Subject: Re: Dell I8000, 2.4.8-ac5 and APM
Date: Mon, 20 Aug 2001 12:21:13 +0200 [thread overview]
Message-ID: <15232.58521.815192.337227@harpo.it.uu.se> (raw)
In-Reply-To: <28536.998043272@redhat.com>
In-Reply-To: <200108162056.WAA18756@harpo.it.uu.se> <28536.998043272@redhat.com>
David Woodhouse writes:
> mikpe@csd.uu.se said:
> > Concerning your problem with pulling the AC plug on your Dell I8000,
> > my suspicion is that either (a) the BIOS isn't notifying apm.c of the
> > event, or (b) apm.c fails to propagate the event to its PM clients.
>
> The problem with suspend actually turned out to be because the APIC is
> unconditionally enabled _before_ the command line is scanned and the 'noapic'
> option is detected.
Right, the local APIC is enabled very early, for some reason I don't recall right now.
> The noapic option, however, does have the effect of
> preventing the registration of the power management code :)
Hmm, the "noapic" kernel option does not and never has had anything to do with
the local APIC, only the IO-APIC which is a completely different beast.
However, RedHat 7.1+ added a bug in init/main.c where they bypass the second
half of the UP APIC initialisation if "noapic" is specified. So using "noapic"
you now end up with the local APIC enabled but its PM code disabled. Nice, eh?
> Booting with 'apic' makes the thing take some time to suspend, and then
> it reboots instead of resuming. That may be your case (b). I put printk in
> the apic suspend and resume functions and neither of them seem to appear.
Please try this with a normal 2.4-ac kernel. Add a printk and a delay at the top
of apm.c's send_event() so we can see exactly which events occur. Boot with
UP_APIC enabled. Initiate suspend: did apm.c log an event and if so which one?
Try to resume: did apm.c log anything before the machine rebooted?
/Mikael
next prev parent reply other threads:[~2001-08-20 10:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 20:56 Mikael Pettersson
2001-08-16 21:30 ` Georg Nikodym
2001-08-17 10:14 ` David Woodhouse
2001-08-20 10:21 ` Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 18:55 Georg Nikodym
2001-08-15 19:57 ` Georg Nikodym
2001-08-15 21:09 ` David Woodhouse
2001-08-15 21:29 ` arjan
2001-08-15 21:42 ` David Woodhouse
2001-08-15 21:57 ` Andrew Morton
2001-08-15 22:07 ` arjan
2001-08-15 23:04 ` Wichert Akkerman
2001-08-15 23:23 ` Alex Romosan
2001-08-15 21:31 ` Georg Nikodym
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=15232.58521.815192.337227@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=dwmw2@infradead.org \
--cc=georgn@somanetworks.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
all inboxes | Powered by JetHome®