All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 13 Oct 2015 08:51:37 +0100	[thread overview]
Message-ID: <1444722697.16876.55.camel@debian.org> (raw)
In-Reply-To: <20151012162107.GB3242@lunn.ch>

On Mon, 2015-10-12 at 18:21 +0200, Andrew Lunn wrote:
> > I've been on backports for some time. AFAIR the problems started
> > with the change to dtb/dts.
> 
> Which kernel version? Can you give me a kernel version when it was
> good and a version when it was bad?
> 
> For a few kernel versions it was possible to boot both DT and the old
> setup file. It would be great to confirm it was the swap to DT, and
> not some other kernel change at about the same time.
> 
> My gut feeling is that the change to DT is not the issue. But this is
> all speculation at the moment, we need some hard evidence.

IIRC someone mentioned that the SATA driver which got used changed with
boardfile vs DT? Not sure if that is true though.

If anyone would like to perform the suggested experiments then flash
-kernel in Debian currently appends a DTB for Linux >= v3.17-rc1.
However this can be adjusted by editing /etc/flash-kernel/db and
adding:

Machine: <...>
DTB-Append-From: v3.16

Where the Machine stanza is the one for your platform, check
/usr/share/flash-kernel/db/all.db. You may need to repeat the Machine
stanza to cope with board vs. dtb mode names, e.g.

    Machine: QNAP TS-41x
    Machine: QNAP TS419 family
    DTB-Append-From: 3.17-rc1

One name is from /proc/device-tree/model under DTB the other is
/proc/cpuinfo:Hardware under board file. Under DTB the
/proc/cpuinfo:Hardware field is generic and not useful here.

You can also do just DTB-Append: Yes.

In any case having fiddled with the db you need to rerun flash-kernel
to make it take affect.

I think the most profitable first test would be to boot the v3.16
Jessie kernel in both board (default in Jessie) and DTB mode (by
modifying /etc/flash-kernel/db as above) and see if the issue
reproduces in both modes.

Older kernel binaries can be found at 
http://snapshot.debian.org/package/linux/, I'm not sure how far back it
is safe to go with Debian's binaries while appending a DTB, I'd
recommend having a serial console available if you are going to try.

Ian.

  reply	other threads:[~2015-10-13  7:51 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
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 [this message]
     [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=1444722697.16876.55.camel@debian.org \
    --to=ijc@debian.org \
    --cc=linux-arm-kernel@lists.infradead.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.