From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: [PATCH 0/3] [2.6.25-rc5] Handle a common BIOS bug on recent ASUS BIOS updates gracefully
Date: Wed, 12 Mar 2008 01:06:02 +0100 [thread overview]
Message-ID: <1205280362.8194.42.camel@linux-2bdv.site> (raw)
Hi Len,
the first patch fixes a memory corruption in ACPICA.
Memory corruption should legitimate this as 2.6.25-rc5 material (also
because this looks rather safe to do and seem to pop up on a lot recent
BIOS updates).
The second patch catches the NULL pointer which is passed on
evaluate_reference now, instead of a corrupted pointer.
The third patch tells the user that his BIOS has an invalid reference as
a passive cooling device (the invalid reference is the NULL handle now).
I have checked this working (ran into the corrupted memory and NULL
pointer) by invalidating a passive trip point and simulate the broken
ASUS BIOSes by overriding a DSDT on another system.
The first report which verifies the patches working with a 2.6.24 kernel
patched on a real broken ASUS Bios can be found here:
https://bugzilla.novell.com/show_bug.cgi?id=350017
Comment #40:
"Works on the Asus M2N-E and M2A VM HDMI."
Thanks,
Thomas
reply other threads:[~2008-03-12 0:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1205280362.8194.42.camel@linux-2bdv.site \
--to=trenn@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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