public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <jap3003@ksu.edu>
To: linux-kernel@vger.kernel.org
Subject: APM, virtual console problem in 2.4.0
Date: Mon, 8 Jan 2001 13:16:53 -0600	[thread overview]
Message-ID: <20010108131653.A27992@ksu.edu> (raw)

Greetings.

When suspending my laptop (Toshiba Satellite 1605CDS; BIOS set to
  suspend to disk) with Debian 2.2r2's 'apm -s', the screen blanks
  and then the system locks up hard (not even the power button works).
  In 2.2.17, 'apm -s' works properly, first blanking the screen (maybe
  twice), then (apparently) handing off to the BIOS.  It looks like 
  the handing off isn't reached in 2.4.0; the screen blanks, but 
  it never reaches the BIOS's 'Saving to Disk' screen.
Additionally (included because of the similar symptomology), when
  changing virtual consoles under 2.4.0 and running X (XFree86 3.3.6;
  from Debian 2.2r0), the screen blanks once again, but then the system
  lock up hard, exactly as above.
Any ideas what I might be doing wrong or what needs to be fixed?  If
  I get some time in the next few days, I'll look at the code; but
  school's coming up and I have a lot of work to get done.
I can supply more information if you need it.
Thanks!

                              -Joseph
-- 
Joseph==============================================jap3003@ksu.edu
"I felt a great disturbance in the force.  As if a significant plot
  line suddenly cried out in terror... and was suddenly silenced."
                        -Torg in "Sluggy Freelance" www.sluggy.com.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-08 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 19:16 Joseph Pingenot [this message]
2001-03-05  1:57 ` APM, virtual console problem in 2.4.0 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=20010108131653.A27992@ksu.edu \
    --to=jap3003@ksu.edu \
    --cc=jap3003+response@ksu.edu \
    --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