From: Peter Martuccelli <peterm@redhat.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: len.brown@intel.com, akpm@osdl.com, linux-kernel@vger.kernel.org,
minyard@mvista.com
Subject: Re: [PATCH 2.6.12.4] ACPI oops during ipmi_si driver init
Date: Tue, 16 Aug 2005 16:50:02 -0400 [thread overview]
Message-ID: <1124225401.7130.797.camel@redrum.boston.redhat.com> (raw)
In-Reply-To: <200508151613.10389.bjorn.helgaas@hp.com>
On Mon, 2005-08-15 at 18:13, Bjorn Helgaas wrote:
> On Friday 12 August 2005 1:44 pm, Peter Martuccelli wrote:
> > Stumbled into this problem working on the ipmi_si driver. When the
> > ipmi_si driver initialization fails the acpi_tb_get_table
> > call, after rsdt_info has been allocated, acpi_get_firmware_table()
> > will oops trying to reference off rsdt_info->pointer in the cleanup
> > code.
>
> I don't know whether the ACPI patch is correct or desirable, but
> I think the ipmi_si ACPI discovery is bogus (it was probably
> written before the current ACPI and PNPACPI driver registration
> interfaces were stable).
>
> Currently, ipmi_si uses the static SPMI table to locate the
> device. But the static table should only be used if we need
> the device very early, before the ACPI namespace is available.
>
> I don't think we use the device early, so we should use
> pnp_register_driver() to claim the appropriate PNP IDs.
> Or we might have to use acpi_bus_register_driver() since
> it looks like it uses ACPI-specific features like GPEs.
Adding in Corey to the discussion regarding ipmi_si initialization,
waiting on Len to decide on the ACPI fix.
next prev parent reply other threads:[~2005-08-16 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 19:44 Peter Martuccelli
2005-08-15 22:13 ` Bjorn Helgaas
2005-08-16 20:50 ` Peter Martuccelli [this message]
2005-08-17 20:30 ` Corey Minyard
2005-08-17 21:09 ` Bjorn Helgaas
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=1124225401.7130.797.camel@redrum.boston.redhat.com \
--to=peterm@redhat.com \
--cc=akpm@osdl.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@mvista.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
all inboxes | Powered by JetHome®