From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Alex Cruise <acruise@infowave.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: apm suspend broken in 2.4.10
Date: Fri, 28 Sep 2001 15:31:29 -0700 [thread overview]
Message-ID: <3BB4FA41.DAAFB705@osdlab.org> (raw)
In-Reply-To: <6B90F0170040D41192B100508BD68CA1015A81B6@earth.infowave.com>
> > Unload some of these (that you don't really need to run)
> > and try "apm -s".
> > If that fails, unload some more of them and try again...
> > That would at least narrow down the search for us.
>
> I already tried that... Maybe my message didn't get through :)
>
> >AC> Just for fun, I tried removing all of my loaded 2.4.10 modules one by
> one,
> >AC> and attempting 'apm --suspend' in between, and still had the same
> problem
> >AC> when I got down to the bare minimum (ext3 and jbd)
>
> Anyway, it looks like something keyboard- or A20-related is vetoing my
> suspend request. Did you get my "the plot thickens" message? It's not
> appearing in the lkml archives, maybe it got lost last night.
I saw the keyboard message, and someone else's A20 reference.
Not one from you IIRC.
~Randy
next prev parent reply other threads:[~2001-09-28 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 22:30 apm suspend broken in 2.4.10 Alex Cruise
2001-09-28 22:31 ` Randy.Dunlap [this message]
[not found] <6B90F0170040D41192B100508BD68CA1015A81B2@earth.infowave.co m>
2001-09-28 3:31 ` Lewin A.R.W. Edwards
-- 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=3BB4FA41.DAAFB705@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=acruise@infowave.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.