On Tue, 2006-05-23 at 22:03 -0700, Brown, Len wrote:
> Same panic with and without a docking station present?
>
> Does the panic go away with CONFIG_ACPI_DOCK=n?
>
> -Len
>
Can either Pavel or Andreas please try this little debugging patch and
send me the dmesg output? Please enable the CONFIG_DEBUG_KERNEL option
in your .config as well so that I can get additional info.
Len (or anyone),
I had a theory that perhaps I'm having a race condition between the two
drivers, however, I'm not sure if this is even a possibility at boot
time, so I wanted to run this theory by you and see if you thought it
could happen.
The dock driver calls acpi_walk_namespace to check for _DCK method.
When it finds it, it allocates a struct dock_station, and then calls
acpi_walk_namespace again to find all the dependent devices. This is
all done as part of the dock driver's init.
When acpiphp driver is called, it also calls acpi_walk_namespace to
check for pci devices dependent on the dock station. It calls a
function exported from the dock driver (is_dock_device) to determine
this. is_dock_device should only be called *after* the dock driver is
finished it's init, because the driver *must* have completed it's search
for dependent devices before it can answer the question
is_dock_device()?.
My understanding is that if your init routine is marked with the
module_init() macro, then all module init routines will be serialized
with respect to each other. i.e., Can I expect that the function
indicated by module_init() would be completed before the function marked
by acpiphp's module_init() would be called? How does the use of
acpi_walk_namespace affect serialization of the module_init? Does it
allow the possibility that the acpiphp driver may enter it's module_init
before the dock driver has completed it's init?
Thanks,
Kristen
---
drivers/acpi/dock.c | 4 ++++
1 file changed, 4 insertions(+)
--- 2.6-mm.orig/drivers/acpi/dock.c
+++ 2.6-mm/drivers/acpi/dock.c
@@ -190,6 +190,10 @@ static int is_dock(acpi_handle handle)
*/
int is_dock_device(acpi_handle handle)
{
+ if (!dock_station) {
+ printk(KERN_ERR "Dock station not done being initialized!!!\n");
+ return 0;
+ }
if (is_dock(handle) || find_dock_dependent_device(dock_station, handle))
return 1;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
