From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Mikael Pettersson" <mikpe@csd.uu.se>, <pavel@ucw.cz>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test6 APM/IDE double-suspend weirdness
Date: Sun, 12 Oct 2003 18:23:51 +0900 [thread overview]
Message-ID: <2c8a01c390a2$cee80640$5cee4ca5@DIAMONDLX60> (raw)
Mikael Pettersson and Pavel Machek wrote:
> > > In test6 (and test5 and possibly earlier), when suspending
> > > my aging Latitude with APM, the machine turns off, only to
> > > turn itself on again one second later with the disk spinning
> > > up. Then it turns itself off again a second later.
In test7 and earlier, when suspending (using command "apm -s" since
2.6.0-test[1-7] disable the keyboard's hotkeys), my Let's Note turns off the
hard disk, only to turn on the hard disk one second later, and then finally
put the entire machine in suspend-to-RAM.
> > Try removing pm_send_all from apm.c
>
> Ok I tried removing all pm_send_all from apm.c.
> I made no difference at all.
I am not surprised. 2.4.20 has the same pm_send_all but does not have
double-suspend weirdness. I removed the call device_suspend(3) instead,
since 2.4.20 didn't call device_suspend(3). This solved it for me in
2.6.0-test7.
Hmm. I've been running with apm=debug for a while, ever since checking
whether the keyboard's hotkeys really were completely disabled (they were,
the BIOS doesn't even find out that I pressed the suspend key or hibernate
key). I wonder if hda powered up again just to write a syslog entry? But
still, it doesn't happen any more after I removed the call
device_suspend(3).
What is the intended effect of device_suspend(3)? Am I asking for trouble
by removing it?
next reply other threads:[~2003-10-12 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 9:23 Norman Diamond [this message]
2003-10-12 11:50 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 12:34 Mikael Pettersson
2003-10-02 12:51 ` Pavel Machek
2003-10-07 9:11 ` Mikael Pettersson
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='2c8a01c390a2$cee80640$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--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
all inboxes | Powered by JetHome®