mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Recent problems with APM and XFree86-4.0.1
Date: Sat, 31 Mar 2001 02:15:14 +0200	[thread overview]
Message-ID: <20010331021514.A6784@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20010325164003.6131@smtp.wanadoo.fr>
In-Reply-To: <20010325164003.6131@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Sun, Mar 25, 2001 at 06:40:03PM +0200

Benjamin Herrenschmidt wrote:
> There is a problem with the power management code for console.c
> 
> The current code calls do_blank_screen(0); on PM_SUSPEND, and
> unblank_screen() on PM_RESUME.
> 
> The problem happens when X is the current display while putting the
> machine to sleep. The do_blank_screen(0) code will do nothing as
> the console is not in KD_TEXT mode.
> However, unblank_screen has no such protection. That means that
> on wakeup, the cursor timer & console blank timers will be re-enabled
> while X is frontmost, causing the blinking cursor to be displayed on
> top of X, and other possible issues.

On that theme of power management with X problems, I have been having
trouble with my laptop crashing when the lid is closed, instead of
suspending as it used to.  The laptop is a Toshiba Satellite 4070CDT.

The problem appeared around the time I updated the XFree86-4 package to
Red Hat 7's latest update, but I also updated to kernel 2.4.2 around
the same time so I'm not sure of the cause.

Until recently, closing the lid caused the machine to beep three times,
sync data to disk and suspend, then opening the lid resumed.  This
worked with or without X displaying.

Now if I switch to a text console and then suspend, it is fine.

If I have X displaying, closing the lid causes the machine to
beep... and beep and beep.  About half the time it does suspend after
many more beeps than usual (e.g. 10 seconds pass before deciding to sync
to disk), and in that case it usually resumes ok but sometimes it
resumes and the machine is not responding to keyboard input.  When this
happens, a hard reboot is required.  (SysRq doesn't work).

The other half of the time it just beeps repeatedly forever.  Mouse
input doesn't work, nor does keyboard.  Curiously, SysRq-S-U-B still
syncs and reboots the machine with a clean disk from this state.

These effects might have something to do with APM in current kernels
and/or XFree86-4.0.1-1 from Red Hat 7 updates.  Has anyone observed
similar recent problems?

-- Jamie

  reply	other threads:[~2001-03-31  0:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-25 16:40 console.c unblank_screen problem Benjamin Herrenschmidt
2001-03-31  0:15 ` Jamie Lokier [this message]
2001-03-31  5:37   ` Recent problems with APM and XFree86-4.0.1 Stephen Rothwell
2001-03-31 14:25     ` Jamie Lokier
2001-04-01 21:41       ` Jamie Lokier
2001-04-01 22:31         ` Rafael E. Herrera
2001-04-02 12:42           ` Jamie Lokier
2001-04-03  6:35     ` Alain E.

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=20010331021514.A6784@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®