ACPI: Error installing notify handler

[Marco]

[ 25.596000] ACPI: Error installing notify handler
[ 25.596000] Device 'dock.0' does not have a release() function, it is broken and must be fixed.
[ 25.596000] BUG: at drivers/base/core.c:104 device_release()
[ 25.596000] [<c01ec9c9>] kobject_cleanup+0x49/0x90
[ 25.596000] [<c01eca10>] kobject_release+0x0/0x10
[ 25.596000] [<c01ed6cb>] kref_put+0x2b/0xa0
[ 25.596000] [<e0444723>] find_dock+0x1d0/0x1f0 [dock]
[ 25.596000] [<c021b8ad>] acpi_ns_walk_namespace+0xf9/0x114
[ 25.596000] [<c021a064>] acpi_walk_namespace+0x57/0x74
[ 25.596000] [<e0444553>] find_dock+0x0/0x1f0 [dock]
[ 25.596000] [<e01e603c>] dock_init+0x3c/0x55 [dock]
[ 25.596000] [<e0444553>] find_dock+0x0/0x1f0 [dock]
[ 25.596000] [<c0143e8d>] sys_init_module+0x15d/0x1ba0
[ 25.596000] [<c0107a5d>] sys_mmap2+0xcd/0xd0
[ 25.596000] [<c0103280>] syscall_call+0x7/0xb
[ 25.596000] =======================

[Marco (mfj)]

uname -a
Linux amilo 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

[Tim Gardner (timg-tpi)]

I sent a note to the authors.

[Marco (mfj)]

Ok. Thanks!

[Giuseppe Iuculano (giuseppe-iuculano)]

I can confirm this bug.

# uname -a
Linux SD6-Mobile 2.6.20-12-lowlatency #2 SMP PREEMPT Wed Mar 21 20:58:11 UTC 2007 i686 GNU/Linux

Toshiba Satellite a100-155

[Edoardo Batini (edoardo-batini)]

hi
same situation here:
Toshiba Satellite A100-646

uname -a
Linux newbu 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

BUG: at drivers/base/core.c:104 device_release()
   495 [ 75.008000] [<c01ed469>] kobject_cleanup+0x49/0x90
   496 [ 75.008000] [<c01ed4b0>] kobject_release+0x0/0x10
   497 [ 75.008000] [<c01ee16b>] kref_put+0x2b/0xa0
   498 [ 75.008000] [<f8c19723>] find_dock+0x1d0/0x1f0 [dock]
   499 [ 75.008000] [<c021ca7d>] acpi_ns_walk_namespace+0xf9/0x114
   500 [ 75.008000] [<c021b234>] acpi_walk_namespace+0x57/0x74
   501 [ 75.008000] [<f8c19553>] find_dock+0x0/0x1f0 [dock]
   502 [ 75.008000] [<f883f03c>] dock_init+0x3c/0x55 [dock]
   503 [ 75.008000] [<f8c19553>] find_dock+0x0/0x1f0 [dock]
   504 [ 75.008000] [<c014416d>] sys_init_module+0x15d/0x1ba0
   505 [ 75.008000] [<c0107a5d>] sys_mmap2+0xcd/0xd0
   506 [ 75.008000] [<c01031f0>] sysenter_past_esp+0x69/0xa9

hope they find a solution...
bye

[Edoardo Batini (edoardo-batini)]

oooppps!
forgot kernel log.

greets

[Dave Gilbert (ubuntu-treblig)]

Also seen on Toshiba Equium A100-306 on 2.6.20-15

[Matteo Z (matteozandi)]

Same problem here on Toshiba Satellite M40-281

[ 28.740000] ACPI: Error installing notify handler
[ 28.740000] Device 'dock.0' does not have a release() function, it is broken and must be fixed.
[ 28.740000] BUG: at drivers/base/core.c:104 device_release()
[ 28.740000] [<c01ed5f9>] kobject_cleanup+0x49/0x90
[ 28.740000] [<c01ed640>] kobject_release+0x0/0x10
[ 28.740000] [<c01ee2fb>] kref_put+0x2b/0xa0
[ 28.740000] [<f93a1723>] find_dock+0x1d0/0x1f0 [dock]
[ 28.740000] [<c021cb4d>] acpi_ns_walk_namespace+0xf9/0x114
[ 28.740000] [<c021b304>] acpi_walk_namespace+0x57/0x74
[ 28.740000] [<f93a1553>] find_dock+0x0/0x1f0 [dock]
[ 28.740000] [<f920603c>] dock_init+0x3c/0x55 [dock]
[ 28.740000] [<f93a1553>] find_dock+0x0/0x1f0 [dock]
[ 28.740000] [<c014421d>] sys_init_module+0x15d/0x1ba0
[ 28.740000] [<c0107a5d>] sys_mmap2+0xcd/0xd0
[ 28.744000] [<c01031f0>] sysenter_past_esp+0x69/0xa9
[ 28.744000] [<c02e0033>] xfrm_state_find+0x4e3/0x570
[ 28.744000] =======================

do you guys also have slow boot with syslogd taking 1 min to start? I'd like to understand if this is correlated to this acpi bug.

Thanks,
Matteo

[Kurt Huwig (k-huwig)]

Here someone suggested a solution:

http://lkml.org/lkml/2007/5/8/505

Happens with Toshiba A7.

@Matteo: I have no dealy on boot, but I say another bug related to this, I think with the first Feisty released, related to NetworkManager, but it has been fixed in the meantime.

[ 22.308000] ACPI: Error installing notify handler
[ 22.308000] Device 'dock.0' does not have a release() function, it is broken and must be fixed.
[ 22.308000] BUG: at drivers/base/core.c:104 device_release()
[ 22.308000] [<c01ed609>] kobject_cleanup+0x49/0x90
[ 22.308000] [<c01ed650>] kobject_release+0x0/0x10
[ 22.308000] [<c01ee30b>] kref_put+0x2b/0xa0
[ 22.308000] [<f8db5723>] find_dock+0x1d0/0x1f0 [dock]
[ 22.308000] [<c021cb5d>] acpi_ns_walk_namespace+0xf9/0x114
[ 22.308000] [<c021b314>] acpi_walk_namespace+0x57/0x74
[ 22.308000] [<f8db5553>] find_dock+0x0/0x1f0 [dock]
[ 22.308000] [<f8a4e03c>] dock_init+0x3c/0x55 [dock]
[ 22.308000] [<f8db5553>] find_dock+0x0/0x1f0 [dock]
[ 22.308000] [<c014422d>] sys_init_module+0x15d/0x1ba0
[ 22.308000] [<c0107a5d>] sys_mmap2+0xcd/0xd0
[ 22.308000] [<c01031f0>] sysenter_past_esp+0x69/0xa9
[ 22.308000] =======================
[ 22.308000] No dock devices found.

[Dave Gilbert (ubuntu-treblig)]

Still happens in Gutsy tribe-5 (2.6.22-10-generic from 2.6.22.10.11 package)

[ 70.749036] Device 'dock.0' does not have a release() function, it is broken and must be fixed.
[ 70.749039] WARNING: at /build/buildd/linux-source-2.6.22-2.6.22/drivers/base/core.c:107 device_release()
[ 70.749043]
[ 70.749043] Call Trace:
[ 70.749057] [<ffffffff80322b4c>] kobject_cleanup+0x5c/0xa0
[ 70.749062] [<ffffffff80322b90>] kobject_release+0x0/0x10
[ 70.749067] [<ffffffff80323c2f>] kref_put+0x3f/0x80
[ 70.749073] [<ffffffff883b787d>] :dock:find_dock+0x224/0x251
[ 70.749079] [<ffffffff803564a2>] acpi_ns_walk_namespace+0x122/0x148
[ 70.749085] [<ffffffff883b7659>] :dock:find_dock+0x0/0x251
[ 70.749091] [<ffffffff80354b1e>] acpi_walk_namespace+0x5f/0x83
[ 70.749098] [<ffffffff880a4037>] :dock:dock_init+0x37/0x53
[ 70.749104] [<ffffffff80256e6b>] sys_init_module+0x19b/0x19b0
[ 70.749121] [<ffffffff80209e8e>] system_call+0x7e/0x83
[ 70.749129]
[ 70.749171] No dock devices found.

[Dave Gilbert (ubuntu-treblig)]

OK, that's a screw up - sorry, I wanted to select 2.6.22 but seemed to have picked up baltix

[Dave Gilbert (ubuntu-treblig)]

I didn't mean to add baltix.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .

[TJ (tj)]

The suggested kernel patch pointed to by kurt (http://lkml.org/lkml/2007/5/8/510) was added to the mainline kernel in 2.6.22.2 and is in Gutsy.

Therefore if this issue is still occurring on Gutsy Tribe-5 we need to look more closely. Please attach the DSDT of the system using:

$ sudo apt-get install acpidump
$ sudo acpidump -b -t DSDT -o MODEL-BIOSVERSION.aml
$ tar -cjvf MODEL-BIOSVERSION.aml.tar.bz2 MODEL-BIOSVERSION.aml

replacing MODEL and BIOSVERSION with your PCs specific values.

[Dave Gilbert (ubuntu-treblig)]

I can confirm the oops has gone on Hardy beta (2.6.24-15-generic 64 bit); I still see the 'ACPI: Error installing notify handler' but that's now followed by 'No dock devices found'.

[Dave Gilbert (ubuntu-treblig)]

The ACPI: Error installing notify handler is no longer there on the Jaunty Beta either - all done?

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 93230

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.