linux-kernel - Re: USB device cannot be reconnected and khubd "blocked for more than 120 seconds"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Jan 2013 09:22:54 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Ming Lei <ming.lei@...onical.com>
Cc:	Alex Riesen <raa.lkml@...il.com>,
	Alan Stern <stern@...land.harvard.edu>,
	Jens Axboe <axboe@...nel.dk>, linux-usb@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: USB device cannot be reconnected and khubd "blocked for more than 120 seconds"

On Monday 14 January 2013 11:47:57 Ming Lei wrote:
> [  181.175323] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [  181.183624] modprobe        D c04f1920     0  2462   2461 0x00000000
> [  181.183685] [<c04f1920>] (__schedule+0x5fc/0x6d4) from [<c005eba4>]
> (async_synchronize_cookie_domain+0xdc/0x
> 168)
> [  181.183715] [<c005eba4>]
> (async_synchronize_cookie_domain+0xdc/0x168) from [<c005ed04>]
> (async_synchronize_f
> ull+0x3c/0x60)
> [  181.183776] [<c005ed04>] (async_synchronize_full+0x3c/0x60) from
> [<c0085610>] (load_module+0x1aac/0x1cdc)
> [  181.183807] [<c0085610>] (load_module+0x1aac/0x1cdc) from
> [<c0085944>] (sys_init_module+0x104/0x110)
> [  181.183837] [<c0085944>] (sys_init_module+0x104/0x110) from
> [<c000dfe0>] (ret_fast_syscall+0x0/0x48)
> [  271.175506] INFO: task modprobe:2462 blocked for more than 90 seconds.
> [  271.182373] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> disables this message.
> [  271.190826] modprobe        D c04f1920     0  2462   2461 0x00000000
> [  271.190887] [<c04f1920>] (__schedule+0x5fc/0x6d4) from [<c005eba4>]
> (async_synchronize_cookie_domain+0xdc/0x
> 168)
> [  271.190917] [<c005eba4>]
> (async_synchronize_cookie_domain+0xdc/0x168) from [<c005ed04>]
> (async_synchronize_f
> ull+0x3c/0x60)
> [  271.190948] [<c005ed04>] (async_synchronize_full+0x3c/0x60) from
> [<c0085610>] (load_module+0x1aac/0x1cdc)
> [  271.190948] [<c0085610>] (load_module+0x1aac/0x1cdc) from
> [<c0085944>] (sys_init_module+0x104/0x110)
> [  271.190979] [<c0085944>] (sys_init_module+0x104/0x110) from
> [<c000dfe0>] (ret_fast_syscall+0x0/0x48)

OK, your trace is totally different. If your hangs are related, as is likely,
my explanation goes out of the window.

	Regards
		Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/