From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: "Alex Riesen" <fork0@users.sourceforge.net>,
acpi-devel@lists.sourceforge.net, torvalds@osdl.org,
mail@hboeck.de, len.brown@intel.com, Greek0@gmx.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Work around asus_acpi driver oopses on Samsung P30s and the like due to the ACPI implicit return
Date: Mon, 20 Feb 2006 10:45:02 +0100 [thread overview]
Message-ID: <81b0412b0602200145r77e99ddbvea55ce9aff07b575@mail.gmail.com> (raw)
In-Reply-To: <20060219211852.05d08f55.akpm@osdl.org>
On 2/20/06, Andrew Morton <akpm@osdl.org> wrote:
> Alex Riesen <fork0@users.sourceforge.net> wrote:
> >
> > FWIW, I need the patch below to stop ACPI freezing at boot on Asus S1300N.
> > There is a BIOS update from Asus, but no mention of any fixes in ACPI,
> > so as I have no means to backup the BIOS in case something goes wrong
> > I didn't do the update.
>
> I think it'd be worth trying the update anyway please. Normally those
> updating programs are pretty careful to not give you a dead box.
You think? ... Still, it'll have to wait till the next weekend. I really
cannot afford a "dead box" midweek.
> > I found out (by putting printks in the initialization code) that a
> > call to INI (whatever it is) of VGA_ (whatever this is) immediately
> > freezes the notebook and the fan goes on shortly afterwards.
> >
>
> Is this a recent problem, or did earlier 2.6.x kernels also fail?
Yes. I think I got the notebook around 2.6.9, and it already had the problem.
I don't remember what I did back than, probably run it with ACPI disabled,
or maybe I made that workaround immediately (there were some sound
problems without ACPI, I recall).
prev parent reply other threads:[~2006-02-20 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 19:06 asus_acpi still broken on Samsung P30/P35 Brown, Len
2005-12-22 10:53 ` Karol Kozimor
2005-12-22 17:42 ` [PATCH] Work around asus_acpi driver oopses on Samsung P30s and the like due to the ACPI implicit return Karol Kozimor
2005-12-23 11:33 ` Christian Aichinger
2005-12-23 12:19 ` Karol Kozimor
2006-01-16 11:03 ` Hanno Böck
2006-01-17 1:06 ` Karol Kozimor
2006-02-19 12:52 ` Alex Riesen
2006-02-20 5:18 ` Andrew Morton
2006-02-20 9:45 ` Alex Riesen [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=81b0412b0602200145r77e99ddbvea55ce9aff07b575@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Greek0@gmx.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=fork0@users.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@hboeck.de \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).