public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: brian@worldcontrol.com
To: "Jonathan D. Amery" <jdamery@chiark.greenend.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VT82C686 && APM deadlock bug?
Date: Thu, 13 Dec 2001 16:02:15 -0800	[thread overview]
Message-ID: <20011213160215.A14006@top.worldcontrol.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112121632440.4294-100000@chiark.greenend.org.uk>
In-Reply-To: <Pine.LNX.4.21.0112121632440.4294-100000@chiark.greenend.org.uk>

On Wed, Dec 12, 2001 at 04:37:01PM +0000, Jonathan D. Amery wrote:
> 
>  I haven't seen this reported anywhere, so apologies if you've heard this
> before:).
> 
>  in 2.4.9 and 2.4.16 with APM compiled in on my Sony Vaio FX201 laptop
> (Via VT82C686 chipset) sometimes when the hardware screensaver comes on
> (as a result of APM) the machine deadlocks and has to be powered off and
> on again.  (Lots of fscking).
> 
>  If you want any more info, please ask :).

I experience the same problem on my Sony Vaio FXA32.

It seems to me to be related to the display.

I can sometimes go into standby mode while in text mode and things 
seem fine.

Going into standby while in X cause the system to freeze.

I can go into standby and come right back out immediately and things
come back but there seems to be memory corruption.


-- 
Brian Litzinger <brian@worldcontrol.com>

    Copyright (c) 2000 By Brian Litzinger, All Rights Reserved

      parent reply	other threads:[~2001-12-14  0:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-12 16:37 VT82C686 && APM deadlock bug? Jonathan D. Amery
2001-12-12 16:50 ` Andreas Steinmetz
2001-12-12 17:11   ` Alan Cox
2001-12-12 17:11     ` Andreas Steinmetz
2001-12-13 11:32 ` Markus Hetzmannseder
2001-12-13 23:26   ` Jonathan D. Amery
2001-12-14  0:02 ` brian [this message]

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=20011213160215.A14006@top.worldcontrol.com \
    --to=brian@worldcontrol.com \
    --cc=jdamery@chiark.greenend.org.uk \
    --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