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: Wed, 21 Oct 2015 22:11:04 +0100 [thread overview]
Message-ID: <1445461864.32735.21.camel@debian.org> (raw)
In-Reply-To: <5627F4E8.3030907@mcfarlanes.me>
On Wed, 2015-10-21 at 21:26 +0100, Iain McFarlane wrote:
> Summary of progress:
Thanks for the info. I've reinstated the CC list here.
> I ended up connecting using a serial cable which was invaluable as my
> initrd was not working (see below)
>
> I tried going backwards:
> 4.2.0 - SATA errors when flashing initrd
> 4.1.0 - SATA errors when flashing initrd
> 4.0.0 - SATA errors when flashing initrd
> 3.16 - No SATA errors when updating initrd - the kernel is flashed using
> dtb but how do I tell if it is used?
/proc/device-tree will exist. Also the Hardware field in /proc/cpuinfo
would differ, IIRC with a board file it says "QNAP TS-119/TS-219" and
with DTB it says "QNAP TS219 family".
Ian.
> it didn't help that somewhere along the line udev/initramfs/systemd is
> broken so that I had to remove all the UUID values from my fstab and go
> back to device names.
>
>
> On 20/10/15 22:40, Iain McFarlane wrote:
> > Posting from archive as previously not subscribed.
> >
> > I have a qnap ts-219p (kirkwood) in pieces at the moment as it is
> > failing to boot the 4.2 kernel from a brand new install of stretch.
> >
> > I am also seeing problems with the sata controller interacting with the
> > mtdblock driver
> >
> > I am going to see if rolling back a version or 2 of the kernel will work
> > tomorrow and will feedback to the list.
> >
> > Regards
> >
> > Iain
> >
>
>
next prev parent reply other threads:[~2015-10-21 21: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
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 [this message]
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=1445461864.32735.21.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.