From: Richard Weinberger <richard@nod.at>
To: Jaap de Jong <jaap.dejong@nedap.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Mounting issue with old uboot and new rootfs
Date: Wed, 13 Dec 2017 17:42:37 +0100 [thread overview]
Message-ID: <1850520.5cNxzxR8i7@blindfold> (raw)
In-Reply-To: <548ecb18-722c-f919-b245-d1b1c15c1697@nedap.com>
Am Mittwoch, 13. Dezember 2017, 11:18:02 CET schrieb Jaap de Jong:
> > Does everything work as expected if you don't set the resize flag in
> > ubinize? Maybe this is the culprit.
>
> Yes, that was my last experiment and that works. It turns off the code
> in the old uboot that modifies the volume in such a way that the new
> kernel is not able to deal with it.
> The strange thing is, that an old kernel doesn't mind.
Can you please rule out U-Boot first?
IOW don't attach UBI from U-Boot and load the kernel via TFTP/NFS, etc...
I'm still not sure whether this is a regression in Linux or U-Boot.
Thanks,
//richard
next prev parent reply other threads:[~2017-12-13 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 15:22 Mounting issue with old rootfs and new kernel Jaap de Jong
2017-11-30 15:28 ` Richard Weinberger
[not found] ` <e144d66c-c754-ad6d-bd0c-ef5384ae7a78@nedap.com>
2017-11-30 16:20 ` Richard Weinberger
2017-12-01 14:26 ` Jaap de Jong
2017-12-04 14:54 ` Jaap de Jong
[not found] ` <1513004605320.75417@nedap.com>
2017-12-12 16:29 ` Mounting issue with old uboot and new rootfs Richard Weinberger
2017-12-13 7:45 ` Jaap de Jong
2017-12-13 9:43 ` Richard Weinberger
2017-12-13 10:18 ` Jaap de Jong
2017-12-13 16:42 ` Richard Weinberger [this message]
2017-12-14 7:28 ` Jaap de Jong
2017-12-14 9:51 ` Jaap de Jong
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=1850520.5cNxzxR8i7@blindfold \
--to=richard@nod.at \
--cc=jaap.dejong@nedap.com \
--cc=linux-mtd@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 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).