linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Huang <jamienstar@163.com>
To: linux-mmc@vger.kernel.org
Subject: RT throttling and mmc hardware interrupt timeout
Date: Sat, 12 Nov 2016 17:56:32 +0800	[thread overview]
Message-ID: <20161112175632.310c819a@JAMIE> (raw)

Hi all:
	Recently, I do test with btrfs filesystem on emmc. When I see
	the message "sched: RT throttling activated", uart, network and
	other peripherals are not responding.
	But, the timer is ok, so I can see the following messages:
	"mmc0: Timeout waiting for hardware interrupt." again and again.
	Finally, "I/O error" messages are coming and the btrfs
	filesystem crashes.

	I think, because I use threadirqs, so most irqs are processed
	in threads, yes, RT threads. When "sched: RT throttling
	activated" comes out, RT threads can not be execute for some
	time, so, we can see mmc interrupt timeout message.

	My kernel version is 3.10.55, I know that's very old. Still,
	I want to know, is there any patch for this problem? Or does
	any one encounter the same problem?  Thank you.


                 reply	other threads:[~2016-11-12  9:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161112175632.310c819a@JAMIE \
    --to=jamienstar@163.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).