From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Continuous SD IO causes hung task messages
Date: Tue, 27 Aug 2019 14:43:37 +0100 [thread overview]
Message-ID: <20190827134337.GK13294@shell.armlinux.org.uk> (raw)
Hi,
While dd'ing the contents of a SD card, I get hung task timeout
messages as per below. However, the dd is making progress. Any
ideas?
Presumably, mmc_rescan doesn't get a look-in while IO is progressing
for the card?
ARM64 host, Macchiatobin, uSD card.
Thanks.
root@arm-d06300000000:~# dd if=/dev/mmcblk1 | md5sum
INFO: task kworker/2:1:52 blocked for more than 120 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 120 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 241 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 362 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Continuous SD IO causes hung task messages
Date: Tue, 27 Aug 2019 14:43:37 +0100 [thread overview]
Message-ID: <20190827134337.GK13294@shell.armlinux.org.uk> (raw)
Hi,
While dd'ing the contents of a SD card, I get hung task timeout
messages as per below. However, the dd is making progress. Any
ideas?
Presumably, mmc_rescan doesn't get a look-in while IO is progressing
for the card?
ARM64 host, Macchiatobin, uSD card.
Thanks.
root@arm-d06300000000:~# dd if=/dev/mmcblk1 | md5sum
INFO: task kworker/2:1:52 blocked for more than 120 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 120 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 241 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
INFO: task kworker/2:1:52 blocked for more than 362 seconds.
Not tainted 5.2.0+ #309
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D 0 52 2 0x00000028
Workqueue: events_freezable mmc_rescan
Call trace:
__switch_to+0xb0/0x198
__schedule+0x22c/0x604
schedule+0x38/0xc8
__mmc_claim_host+0xcc/0x1ec
mmc_get_card+0x30/0x3c
mmc_sd_detect+0x1c/0x78
mmc_rescan+0x1c4/0x35c
process_one_work+0x14c/0x408
worker_thread+0x140/0x3f4
kthread+0xfc/0x128
ret_from_fork+0x10/0x18
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-08-27 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 13:43 Russell King - ARM Linux admin [this message]
2019-08-27 13:43 ` Continuous SD IO causes hung task messages Russell King - ARM Linux admin
2019-08-27 13:55 ` Ulf Hansson
2019-08-27 13:55 ` Ulf Hansson
2019-08-27 13:55 ` Ulf Hansson
2019-08-27 14:36 ` Russell King - ARM Linux admin
2019-08-27 14:36 ` Russell King - ARM Linux admin
2019-08-27 14:52 ` Russell King - ARM Linux admin
2019-08-27 14:52 ` Russell King - ARM Linux admin
2019-08-27 15:06 ` Russell King - ARM Linux admin
2019-08-27 15:06 ` Russell King - ARM Linux admin
2019-08-28 10:31 ` Ulf Hansson
2019-08-28 10:31 ` Ulf Hansson
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=20190827134337.GK13294@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.