From: ijc@debian•org (Ian Campbell)
To: linux-arm-kernel@lists•infradead.org
Subject: I/O issues with writing to mtdblock devices on kirkwood
Date: Sun, 06 Sep 2015 13:11:44 +0100 [thread overview]
Message-ID: <1441541504.23553.46.camel@debian.org> (raw)
In-Reply-To: <20150905210846.GF6040@lunn.ch>
On Sat, 2015-09-05 at 23:08 +0200, Andrew Lunn wrote:
> On Fri, Aug 21, 2015 at 01:24:17PM +0100, Ian Campbell wrote:
> > Hi kirkwood-upstream,
> >
> > We (Debian) have had a couple of reports of I/O errors running
> Debian
> > on kirkwood, specifically it seems to relate to later kernels (e.g.
> > 4.0+) and I _suspect_ (without proof) that it may be due to the
> switch
> > from board files to the DTS based kernel, or some change implied by
> > this (e.g. different SATA driver now or timeouts have changed
> > perhaps?).
>
> Hi Ian
>
> I've not reproduced this exactly, but something similar.
It sounds likely to be the same underlying issue.
> I do a find / and in parallel a cat /dev/mtdblock3 > /dev/null
FYI it was reported this morning[0] that using flashcp doesn't exhibit
this behaviour. Since AIUI flashcp goes directly at the /dev/mtdN
device, rather than via mtdblockN, this seems to point towards
something in the mtdblock layer perhaps?
> While the cat is active, the find grinds to a halt. I don't get any
> SATA timeouts, but that could be because /dev/mtdblock3 is small
> enough that the timers don't expire.
Agreed.
Thanks,
Ian.
[0] http://article.gmane.org/gmane.linux.debian.ports.arm/15767
> So i will now try to track down if there is a lock getting contended,
> or at least why only the cat process makes progress.
>
> Andrew
>
>
next prev parent reply other threads:[~2015-09-06 12:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 12:24 I/O issues with writing to mtdblock devices on kirkwood Ian Campbell
2015-08-21 13:07 ` Andrew Lunn
2015-08-21 20:23 ` Ian Campbell
2015-09-05 21:08 ` Andrew Lunn
2015-09-06 12:11 ` Ian Campbell [this message]
2015-10-11 14:37 ` JM
2015-10-11 15:35 ` Andrew Lunn
2015-10-12 14:29 ` JM
2015-10-12 16:05 ` Rob J. Epping
2015-10-12 16:21 ` Andrew Lunn
2015-10-13 7:51 ` Ian Campbell
[not found] ` <5626B4DC.8000407@mcfarlanes.me>
[not found] ` <5627F4E8.3030907@mcfarlanes.me>
2015-10-21 21:11 ` Ian Campbell
2015-10-21 21:22 ` Iain McFarlane
2015-10-21 21:28 ` JM
2015-10-21 21:31 ` Iain McFarlane
2015-10-22 0:38 ` Andrew Lunn
2015-10-22 6:40 ` Ian Campbell
2015-10-22 6:40 ` Ian Campbell
2016-01-11 23:00 ` Martin Michlmayr
2016-01-11 23:22 ` Mark Brown
2016-01-11 23:43 ` Andrew Lunn
2016-01-12 1:21 ` Mark Brown
2016-01-12 0:07 ` Martin Michlmayr
2016-01-12 0:47 ` Mark Brown
2016-01-12 1:19 ` Andrew Lunn
2016-01-12 1:31 ` Mark Brown
2016-01-12 16:29 ` Arnd Bergmann
2016-01-12 18:02 ` Mark Brown
2016-01-12 21:49 ` Arnd Bergmann
2016-01-12 22:00 ` Mark Brown
2016-01-12 22:41 ` Arnd Bergmann
2016-01-13 11:42 ` Mark Brown
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=1441541504.23553.46.camel@debian.org \
--to=ijc@debian$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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