From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Paul Bain <prbain@essex.ac.uk>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.10 oops on startup
Date: Wed, 5 Jan 2005 14:24:48 +0800 [thread overview]
Message-ID: <2cd57c9005010422241a1e36da@mail.gmail.com> (raw)
In-Reply-To: <1104899778.1992.45.camel@sofa.co.uk>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On Wed, 05 Jan 2005 04:36:18 +0000, Paul Bain <prbain@essex.ac.uk> wrote:
> On Tue, 2005-01-04 at 18:46, Randy.Dunlap wrote:
> > Have you tested any 2.6.10-bk# versions to see if this has been
> > fixed by recent patches?
> > If not, please try that and let us know, then I'll look at it
> > more if needed.
> >
> > Thanks,
> > ~Randy
>
> Hi, thanks for the response. I tried it with 2.6.10-bk7 and it crashed
> with
>
This is a quick fix. Please try the attached patch.
coywolf
--
Coywolf Qi Hunt
Homepage http://sosdg.org/~coywolf/
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix-acpi_ex_load_op.patch --]
[-- Type: text/x-patch; name="fix-acpi_ex_load_op.patch", Size: 593 bytes --]
diff -Nrup linux-2.6.10/drivers/acpi/executer/exconfig.c linux-2.6.10-cy/drivers/acpi/executer/exconfig.c
--- linux-2.6.10/drivers/acpi/executer/exconfig.c 2004-10-19 05:54:32.000000000 +0800
+++ linux-2.6.10-cy/drivers/acpi/executer/exconfig.c 2005-01-05 14:19:18.000000000 +0800
@@ -368,7 +368,7 @@ acpi_ex_load_op (
*/
status = acpi_ex_read_data_from_field (walk_state, obj_desc, &buffer_desc);
if (ACPI_FAILURE (status)) {
- goto cleanup;
+ return_ACPI_STATUS (status);
}
table_ptr = ACPI_CAST_PTR (struct acpi_table_header, buffer_desc->buffer.pointer);
next prev parent reply other threads:[~2005-01-05 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 18:46 PROBLEM: 2.6.10 oops on startup Paul Bain
2005-01-04 18:46 ` Randy.Dunlap
2005-01-05 4:36 ` Paul Bain
2005-01-05 6:24 ` Coywolf Qi Hunt [this message]
2005-01-05 14:18 ` Paul Bain
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=2cd57c9005010422241a1e36da@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prbain@essex.ac.uk \
--cc=rddunlap@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 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.