http://bugzilla.kernel.org/show_bug.cgi?id=9772





------- Comment #17 from [EMAIL PROTECTED]  2008-02-04 16:44 -------
I was able to get one hang to happen, but I applied your debug patch, turned on
ACPI debugging in my kernel config, and now I can't get the failure to happen
at all.  

Dmesg output after the failed ejection is a bit insightful, though this was
from before I had debugging turned on or the additional information:

events/0      R  running task        0     7      2
events/1      D ffffffff805ff778     0     8      2
 ffff81000144fbe0 0000000000000046 ffff81000fa26800 ffff81000ffd6040
 ffff81000ffd6040 ffffffff8022f327 ffff81000fa26800 ffff8100015317c0
 000000000000000f 0000000000000007 ffff81000fa26800 0000000000000001
Call Trace:
 [<ffffffff8022f327>] update_curr_load+0x87/0xa0
 [<ffffffff80231a46>] try_to_wake_up+0x66/0x370
 [<ffffffff80447572>] wait_for_completion+0xa2/0xf0
 [<ffffffff80231d50>] default_wake_function+0x0/0x10
 [<ffffffff8024e0f8>] kthread_stop+0x58/0x80
 [<ffffffff8024a4c9>] cleanup_workqueue_thread+0x19/0x30
 [<ffffffff8024a57f>] workqueue_cpu_callback+0x9f/0x150
 [<ffffffff8044bdc5>] notifier_call_chain+0x45/0x90
 [<ffffffff8025773f>] _cpu_down+0x1df/0x2c0
 [<ffffffff80257854>] cpu_down+0x34/0x60
 [<ffffffff80357f25>] acpi_processor_remove+0x63/0x140
 [<ffffffff8035282d>] acpi_device_remove+0x53/0x79
 [<ffffffff80390452>] __device_release_driver+0x82/0xc0
 [<ffffffff80390978>] device_release_driver+0x38/0x60
 [<ffffffff8035291c>] acpi_bus_remove+0x39/0x72
 [<ffffffff803529cf>] acpi_bus_trim+0x7a/0x106
 [<ffffffff80351433>] acpi_bus_data_handler+0x0/0x1
 [<ffffffff80352a91>] acpi_bus_hot_remove_device+0x36/0xc1
 [<ffffffff80338957>] acpi_os_execute_notify+0x0/0x2c
 [<ffffffff8033897a>] acpi_os_execute_notify+0x23/0x2c
 [<ffffffff8024a22f>] run_workqueue+0x7f/0x110
 [<ffffffff8024ad60>] worker_thread+0x0/0x130
 [<ffffffff8024ae25>] worker_thread+0xc5/0x130
 [<ffffffff8024e5b0>] autoremove_wake_function+0x0/0x30
 [<ffffffff8024ad60>] worker_thread+0x0/0x130
 [<ffffffff8024ad60>] worker_thread+0x0/0x130
 [<ffffffff8024e1eb>] kthread+0x4b/0x80
 [<ffffffff8020cd38>] child_rip+0xa/0x12
 [<ffffffff8024e1a0>] kthread+0x0/0x80
 [<ffffffff8020cd2e>] child_rip+0x0/0x12

Maybe I just didn't wait long enough, and it would have eventually completed?

I'll update if I can get this problem to reproduce.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to