From: Marek Vasut <marek.vasut@gmail.com>
To: loody <miloody@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: Kernel coredump about kblockd deadlock
Date: Sat, 14 Jan 2012 01:29:34 +0100 [thread overview]
Message-ID: <201201140129.34399.marek.vasut@gmail.com> (raw)
In-Reply-To: <CANudz+um5XG2Qua6a1O7ENnBeYcfiG5mOyyA6-=ctccXMYEFhg@mail.gmail.com>
> Dear all:
> I use kernel 2.6.35.13 and cpu for mips
Does this happen with anything less ancient ?
M
> When I plug in/out usb stick for several times I got following warning
> messages as I append at the end of mail.
>
> is it possible correlate to below issue
> http://thread.gmane.org/gmane.linux.kernel/1177383/focus=69879
> Thanks for your help,
>
>
> INFO: task kblockd/0:10 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> kblockd/0 D [87016a78] 802d1e48 0 10 0x00100000 2
> 11 9 (kernel thread)
> Stack : 00000001 80107148 8562ed80 800e9098 00000001 00000001 7fffffff
> 00000000 00000000 7fffffff 87053d38 ffffffff 87053d38 87053d28 872ff00c
> 802d1e48 00000001 00000009 00000102 80071c80 00005965 0056addf 00005965
> 00000001 00000000 00000000 7fffffff 80020c64 00000000 00000002 00000000
> 00000000 7fffffff 802d1ca8 00000000 80024538 00000004 0000000a 00000001
> 87016a78 ...
> Call Trace:
> [<802d1764>] schedule+0x648/0x70c from[<802d1e48>]
> schedule_timeout+0x30/0x324 [<802d1e48>] schedule_timeout+0x30/0x324
> from[<802d1ca8>]
> wait_for_common+0xf8/0x1c0
> [<802d1ca8>] wait_for_common+0xf8/0x1c0 from[<80044400>]
> __cancel_work_timer+0x188/0x210
> [<80044400>] __cancel_work_timer+0x188/0x210 from[<801a48c4>]
> blk_cleanup_queue+0x18/0x6c
> [<801a48c4>] blk_cleanup_queue+0x18/0x6c from[<802098f4>]
> scsi_device_dev_release_usercontext+0x174/0x1e4
> [<802098f4>] scsi_device_dev_release_usercontext+0x174/0x1e4
> from[<80043aa8>] execute_in_process_context+0x30/0x5c
> [<80043aa8>] execute_in_process_context+0x30/0x5c from[<801eeda8>]
> device_release+0x54/0x90
> [<801eeda8>] device_release+0x54/0x90 from[<801b0180>]
> kobject_release+0x70/0xa8 [<801b0180>] kobject_release+0x70/0xa8
> from[<801b17bc>] kref_put+0x80/0x98 [<801b17bc>] kref_put+0x80/0x98
> from[<80203c04>] scsi_request_fn+0x51c/0x61c [<80203c04>]
> scsi_request_fn+0x51c/0x61c from[<801a482c>]
> generic_unplug_device+0x38/0x7c
> [<801a482c>] generic_unplug_device+0x38/0x7c from[<80043e90>]
> worker_thread+0x1ec/0x2d4
> [<80043e90>] worker_thread+0x1ec/0x2d4 from[<800482c4>] kthread+0x7c/0x84
> [<800482c4>] kthread+0x7c/0x84 from[<80007818>]
> kernel_thread_helper+0x10/0x18
>
> ---------------------------------------------------------------------------
> ---------- hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
> hub 1-0:1.0: port 1, status 0000, change 0001, 12 Mb/s
> usb 1-1: USB disconnect, address 35
> usb 1-1: unregistering device
> usb 1-1: unregistering interface 1-1:1.0
> usb 1-1: usb_disable_device nuking all URBs
> hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x0
> hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
> ehci-ehci ehci-ehci.0: GetStatus port 1 status 000803 sig=j CSC CONNECT
> hub 1-0:1.0: port 1, status 0401, change 0001, 480 Mb/s
> hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x401
> ehci-ehci ehci-ehci.0: port 1 high speed
> ehci-ehci ehci-ehci.0: GetStatus port 1 status 00000d sig=se0 PEC PE
> CONNECT usb 1-1: new high speed USB device using ehci-ehci and address 36
> ehci-ehci ehci-ehci.0: port 1 high speed
> ehci-ehci ehci-ehci.0: GetStatus port 1 status 00000d sig=se0 PEC PE
> CONNECT usb 1-1: default language 0x0409
> usb 1-1: udev 36, busnum 1, minor = 35
> ....
> .....
next prev parent reply other threads:[~2012-01-14 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 13:36 Kernel coredump about kblockd deadlock loody
2012-01-14 0:29 ` Marek Vasut [this message]
[not found] ` <CANudz+txP0tQQTjtxP99AqcnJcQadHdFEHVuoPXLYfKXB0EgAA@mail.gmail.com>
2012-01-15 15:07 ` Marek Vasut
[not found] ` <CANudz+uoY8pxCVEeKFhorfb0nqsD+re_Ai-6Ruz2b3ExtJChSA@mail.gmail.com>
2012-01-15 14:45 ` loody
2012-01-16 11:03 ` Jun'ichi Nomura
2012-02-01 6:44 ` loody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201201140129.34399.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=miloody@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox