From: "Simon Raffeiner (SCC)" <simon.raffeiner@kit.edu>
To: sb@m-labs.hk
Cc: linux-mmc@vger.kernel.org
Subject: Re: "Timeout waiting for hardware interrupt" on Lenovo Thinkpad Tablet 10
Date: Mon, 2 Feb 2015 14:38:19 +0100 [thread overview]
Message-ID: <54CF7DCB.8070302@kit.edu> (raw)
Hello Sébastien,
I own a Lenovo Thinkpad Tablet 8, which is quite similar to the Thinkpad
Tablet 10, and we seem to run into the same issues with both devices.
I am currently trying to install Ubuntu 15.04 using an USB stick, so my
kernel version is 3.18.0-12-generic (which is based on the 3.18.3
upstream stable kernel).
As you reported, the tablet reliably freezes after about 15 to 20
minutes, regardless if "debug_quirks2=0xc0" is set or not. The last
kernel message is "mmc0: Timeout waiting for hardware interrupt". But in
my case, the tablet also crashes if the eMMC storage is not used as the
root filesystem, it also happens in the live environment booted off the
USB stick, e.g. when trying to do an mkfs on one of the eMMC partitions.
Thanks a lot for reporting this issue, I was already about to send the
device back because I thought the eMMC was broken.
regards,
Simon
Sébastien Bourdeauducq wrote:
> Hi,
>
> Under Linux, the most annoying problem that the Lenovo Thinkpad Tablet
> 10 has is the unreliable eMMC.
>
> I intermittently get an error "mmc0: Timeout waiting for hardware
> interrupt" followed by a crash of the machine (when the eMMC is used
> as rootfs).
>
> I have been able to work around this issue with kernel 3.13.0 by
> passing the debug_quirks2=0xc0 option to the sdhci module, which
> disables the HS200 and DDR50 transfer modes. The read data rate (as
> measured by hdparm -t) drops from 119MB/s to 42MB/s, but at least the
> computer no longer crashes every 20 minutes and my files are not
> corrupted anymore.
>
> Unfortunately, with more recent kernels such as 3.18.4, the sdhci
> module (still with debug_quirks2=0xc0) appears to select another
> problematic transfer mode. The read data rate jumps to 65MB/s and the
> bug manifests itself again.
>
> What changes in sdhci between 3.13.0 and 3.18.4 could cause that? I'd
> like to be able to use the eMMC reliably at least at 42MB/s using
> recent kernels, which hopefully will introduce fixes for the
> gazillion other problems that this crippled machine has under Linux
> (absolutely nothing works correctly except the CPU, display and USB).
>
> Thanks,
> Sébastien
next reply other threads:[~2015-02-02 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:38 Simon Raffeiner (SCC) [this message]
2015-02-02 14:06 ` "Timeout waiting for hardware interrupt" on Lenovo Thinkpad Tablet 10 Sébastien Bourdeauducq
2015-02-08 11:54 ` Simon Raffeiner (SCC)
-- strict thread matches above, loose matches on Subject: below --
2015-02-02 12:29 Sébastien Bourdeauducq
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=54CF7DCB.8070302@kit.edu \
--to=simon.raffeiner@kit.edu \
--cc=linux-mmc@vger.kernel.org \
--cc=sb@m-labs.hk \
/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