On 11/16/2010 06:19 AM, Tejun Heo wrote:
Nov 15 13:12:13 localhost kernel: Showing all locks held in the system: Nov 15 13:12:13 localhost kernel: 3 locks held by kworker/0:1/19: Nov 15 13:12:13 localhost kernel: #0: (events){+.+.+.}, at: [<78446e6f>] process_one_work+0x13e/0x2bf Nov 15 13:12:13 localhost kernel: #1: (wireless_nlevent_work){+.+.+.}, at: [<78446e6f>] process_one_work+0x13e/0x2bf Nov 15 13:12:13 localhost kernel: #2: (rtnl_mutex){+.+.+.}, at: [<786ffe97>] rtnl_lock+0xf/0x11 Nov 15 13:12:13 localhost kernel: 3 locks held by kworker/0:2/1054: Nov 15 13:12:13 localhost kernel: #0: (events){+.+.+.}, at: [<78446e6f>] process_one_work+0x13e/0x2bf Nov 15 13:12:13 localhost kernel: #1: ((&rdev->conn_work)){+.+.+.}, at: [<78446e6f>] process_one_work+0x13e/0x2bf Nov 15 13:12:13 localhost kernel: #2: (rtnl_mutex){+.+.+.}, at: [<786ffe97>] rtnl_lock+0xf/0x11Where are the backtraces for kworker/u:5, 0:1 and 0:2?
They are not in /var/log/messages either, at least not in the sysrq-t dump. I think at least some of them are in there from the blocked-task printouts. I've uploaded the /var/log/messages file here, in case you want to look at it: http://www.candelatech.com/~greearb/messages.gz Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
