From: John Fremlin <chief@bandits.org>
To: bradley mclain <bradley_kernel@yahoo.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: APM suspend system lockup under 2.4.2 and 2.4.2ac1
Date: 23 Feb 2001 22:37:36 +0000 [thread overview]
Message-ID: <m2snl53u1b.fsf@boreas.yi.org.> (raw)
In-Reply-To: <20010223031521.93782.qmail@web9205.mail.yahoo.com>
In-Reply-To: bradley mclain's message of "Thu, 22 Feb 2001 19:15:21 -0800 (PST)"
Unfortunately, the APM maintainer, Stephen Rothwell, seems to have
gone into hibernation (pun) and is not responding to emails.
bradley mclain <bradley_kernel@yahoo.com> writes:
> apm --suspend causes my system to hang under 2.4.2 and 2.4.2ac1. it
> was working fine under 2.4.1ac19. looking at syslog it appears that
> the driver for my xircom pcmcia card may be involved -- it was the
> last entry on two of three occasions. the latest lockup (under
> 2.4.1ac1) left no trace in syslog.
Are all kernel messages dumped to syslog? See syslog.conf(5).
> upon issuing the command the screen shuts down, but the rest of the
> machine (drive, etc.) fails to, and i cannot get control back.
If the screen shutdown, all the PM enabled drivers OK'd the suspend
and the APM state was changed.
Perhaps the particular driver you used bungled things somehow. You
could try again with the driver/card unloaded, which would help narrow
the cause of the problem down.
[...]
--
http://www.penguinpowered.com/~vii
next prev parent reply other threads:[~2001-02-23 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 3:15 APM suspend system lockup under 2.4.2 and 2.4.2ac1 bradley mclain
2001-02-23 22:37 ` John Fremlin [this message]
[not found] <E14WJrt-0006Ud-00@the-village.bc.nu>
2001-02-24 5:27 ` bradley mclain
2001-02-24 5:29 ` bradley mclain
2001-02-24 17:02 ` Alan Cox
2001-03-01 20:00 ` John Fremlin
2001-03-01 22:22 ` Alan Cox
2001-03-01 23:04 ` John Fremlin
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=m2snl53u1b.fsf@boreas.yi.org. \
--to=chief@bandits.org \
--cc=bradley_kernel@yahoo.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