From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Alex Cruise <acruise@infowave.com>,
"'Randy.Dunlap'" <rddunlap@osdlab.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: apm suspend broken in 2.4.10
Date: Thu, 27 Sep 2001 23:31:55 -0400 [thread overview]
Message-ID: <4.3.2.7.2.20010927233132.00b75ee0@pop.registeredsite.com> (raw)
In-Reply-To: <6B90F0170040D41192B100508BD68CA1015A81B2@earth.infowave.co m>
>Sep 27 19:39:09 onus kernel: awc: APM Suspend vetoed by:
>Sep 27 19:39:09 onus kernel: type = 1 id = 1104151299 callback =
>-1072064644 data = 0 flags = 0 state = 0 prev_state = 0
>
>1104151299 is 0x41D00303, which if you consult your include/linux/pm.h
>(PM_SYS_DEV = 1, PM_SYS_KBC = 0x41d00303), would seem AFAICT to indicate
>that it's the keyboard driver--or something upstream of it--who's vetoing my
>suspend. Am I crazy?
Maybe something to do with A20 switching?
-- Lewin A.R.W. Edwards
Embedded Engineer, Digi-Frame Inc.
Work: http://www.digi-frame.com/
Tel (914) 937-4090 9am-6:30pm M-F ET
Personal: http://www.larwe.com/ http://www.zws.com/
next parent reply other threads:[~2001-09-28 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6B90F0170040D41192B100508BD68CA1015A81B2@earth.infowave.co m>
2001-09-28 3:31 ` Lewin A.R.W. Edwards [this message]
2001-09-28 22:30 Alex Cruise
2001-09-28 22:31 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 3:03 Alex Cruise
2001-09-28 1:50 Alex Cruise
2001-09-28 22:05 ` Randy.Dunlap
2001-09-27 23:56 Alex Cruise
2001-09-28 0:10 ` Randy.Dunlap
2001-09-28 0:52 ` Alan Cox
2001-09-28 9:09 ` jc
2001-09-28 10:05 ` Keith Owens
2001-09-27 21:07 Alex Cruise
2001-09-27 21:03 Alex Cruise
2001-09-27 22:17 ` Randy.Dunlap
2001-09-28 9:12 ` jc
2001-09-27 0:29 Alex Cruise
2001-09-27 20:36 ` Randy.Dunlap
2001-09-25 22:00 jc
2001-09-26 8:44 ` Matthias Andree
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=4.3.2.7.2.20010927233132.00b75ee0@pop.registeredsite.com \
--to=larwe@larwe.com \
--cc=acruise@infowave.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdlab.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®