From: Zhang Rui <rui.zhang@intel.com>
To: John Keller <jpk@sgi.com>
Cc: len.brown@intel.com,
"linux-acpi@vger" <linux-acpi@vger.kernel.org>,
akpm@osdl.org, ayoung@sgi.com, shaohua.li@intel.com
Subject: Re: acpi_bus_register_driver() and latest acpi trees
Date: Thu, 01 Feb 2007 09:58:35 +0800 [thread overview]
Message-ID: <1170295115.24637.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200701311611.l0VGBCwY395506@fcbayern.americas.sgi.com>
On Wed, 2007-01-31 at 10:11 -0600, John Keller wrote:
> Len,
> When building kernels from your ACPI release or test trees,
> as well as the -mm tree, SN Altix boots are crashing in the
> kobject code when calling acpi_bus_register_driver().
> The crash is because kset->list has not been initialized yet.
>
> kobject_add()
> list_add_tail(&kobj->entry,&kobj->kset->list);
>
>
> Is there now a restriction on how early acpi_bus_register_driver()
> can be called? If so, at what point in time can calls be made,
> and is it still possible to register a driver early enough such
> that it will be called at device discovery time vs registration time?
>
Yes, this is caused by the recent ACPI sysfs conversion changes.
Now we make ACPI use driver model.
All the ACPI drivers should register after the ACPI bus has registered,
i.e. we can not call acpi_bus_register_driver() before acpi_scan_init()
in drivers/acpi/scan.c.
next prev parent reply other threads:[~2007-02-01 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 16:11 acpi_bus_register_driver() and latest acpi trees John Keller
2007-02-01 1:58 ` Zhang Rui [this message]
2007-02-08 2:29 ` Len Brown
2007-02-10 0:27 ` John Keller
2007-02-11 6:03 ` Len Brown
2007-02-14 17:29 ` John Keller
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=1170295115.24637.5.camel@localhost.localdomain \
--to=rui.zhang@intel.com \
--cc=akpm@osdl.org \
--cc=ayoung@sgi.com \
--cc=jpk@sgi.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=shaohua.li@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