From: Ondrej Zary <linux@rainbow-software.org>
To: hpa@zytor.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Enable A20 using KBC for some MSI laptops to fix S3 resume
Date: Mon, 5 Nov 2012 21:35:19 +0100 [thread overview]
Message-ID: <201211052135.20009.linux@rainbow-software.org> (raw)
In-Reply-To: <201210261056.44225.zary@gsystems.sk>
On Friday 26 October 2012 10:56:44 Ondrej Zary wrote:
> Some MSI laptop BIOSes are broken - INT 15h code uses port 92h to enable
> A20 line but resume code assumes that KBC was used.
> The laptop will not resume from S3 otherwise but powers off after a while
> and then powers on again stuck with a blank screen.
>
> Fix it by enabling A20 using KBC. Affected laptop list and DMI data are
> from bug reports at Ubuntu Launchpad.
>
> Also add kernel parameter to easily activate this quirk on any system.
>
> Only compile tested. The original patch was tested with EX600 and PR200.
>
> Fixes https://bugzilla.kernel.org/show_bug.cgi?id=12878
The bug was marked as RESOLVED CODE_FIX but I wonder what happened to this
patch. Was it applied? Or is someone working on a better way to fix this
problem?
--
Ondrej Zary
next prev parent reply other threads:[~2012-11-05 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 8:56 [PATCH v3] Enable A20 using KBC for some MSI laptops to fix S3 resume Ondrej Zary
2012-11-05 20:35 ` Ondrej Zary [this message]
2012-12-10 21:26 ` H. Peter Anvin
2012-12-10 22:51 ` Ondrej Zary
2012-12-11 18:59 ` Ondrej Zary
2012-12-11 19:07 ` H. Peter Anvin
2012-12-11 20:29 ` Ondrej Zary
2012-12-11 20:36 ` H. Peter Anvin
2012-12-11 20:50 ` Ondrej Zary
2012-12-11 20:56 ` H. Peter Anvin
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=201211052135.20009.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.