24 Sep 21:16
possible recursive locking in ps2_command
From: Michael S. Tsirkin <m.s.tsirkin <at> gmail.com>
Subject: possible recursive locking in ps2_command
Newsgroups: gmane.linux.kernel.input, gmane.linux.kernel
Date: 2008-09-24 19:17:58 GMT
Subject: possible recursive locking in ps2_command
Newsgroups: gmane.linux.kernel.input, gmane.linux.kernel
Date: 2008-09-24 19:17:58 GMT
I got the following on resume on my T60p, this might indicate
a potential deadlock I think.
[33491.050660] psmouse.c: Failed to enable mouse on isa0060/serio1
[33491.054938] PM: Removing info for No Bus:mouse1
[33491.064134] PM: Removing info for No Bus:event8
[33491.080154] PM: Removing info for No Bus:input8
[33491.089117]
[33491.089120] =============================================
[33491.089128] [ INFO: possible recursive locking detected ]
[33491.089133] 2.6.27-rc7-mst #53
[33491.089137] ---------------------------------------------
[33491.089141] kseriod/147 is trying to acquire lock:
[33491.089146] (&ps2dev->cmd_mutex){--..}, at: [<c028cdf3>] ps2_command+0x43/0x3a0
[33491.089162]
[33491.089163] but task is already holding lock:
[33491.089168] (&ps2dev->cmd_mutex){--..}, at: [<c028cdf3>] ps2_command+0x43/0x3a0
[33491.089179]
[33491.089180] other info that might help us debug this:
[33491.089185] 4 locks held by kseriod/147:
[33491.089189] #0: (serio_mutex){--..}, at: [<c028b612>] serio_thread+0x22/0x340
[33491.089204] #1: (&serio->drv_mutex){--..}, at: [<c028aad4>] serio_connect_driver+0x24/0x50
[33491.089218] #2: (psmouse_mutex){--..}, at: [<f8a355ca>] psmouse_connect+0x1a/0x250 [psmouse]
[33491.089246] #3: (&ps2dev->cmd_mutex){--..}, at: [<c028cdf3>] ps2_command+0x43/0x3a0
[33491.089259]
[33491.089260] stack backtrace:
[33491.089266] Pid: 147, comm: kseriod Not tainted 2.6.27-rc7-mst #53
[33491.089272] [<c014b924>] validate_chain+0xbd4/0xeb0
[33491.089282] [<c014978a>] ? find_usage_backwards+0x1a/0x100
[33491.089293] [<c014be39>] __lock_acquire+0x239/0x950
(Continue reading)
RSS Feed