Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Egli, Samuel" <samuel.egli@siemens.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: autoresize causes insufficient reservation of PEBs for bad PEB handling
Date: Thu, 09 Jul 2015 12:29:58 +0200	[thread overview]
Message-ID: <559E4D26.5080203@nod.at> (raw)
In-Reply-To: <27E9275BC1C8554E840881B19B62BE421A9ADD@DENBGAT9EI1MSX.ww902.siemens.net>

Am 09.07.2015 um 12:23 schrieb Egli, Samuel:
> Hi Richard
> 
>>
>> There are more odds.
>>
>> I don't see a message like "[   90.757282] ubi0: volume 2
>> ("configuration") re-sized from 80 to 7948 LEBs"
>> in that log. So, re-size did not happen.
>>
>> Is this a pristine kernel or does it contain some vendor "tweaks"?
> 
> The issue didn't lie in linux kernel. We have in our ubi volume
> the uImage. So U-Boot needs to mount it and actually does
> the resize. In U-Boot version 2014.04 there is still a 
> older ubi driver that doesn't perform the resizing correctly.

Bah. ;-\

> With U-Boot v2015.04, however, the issue is resolved.

Thanks for letting me know.

> Thanks, for looking into this.

You're welcome!

Thanks,
//richard

  reply	other threads:[~2015-07-09 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 11:04 autoresize causes insufficient reservation of PEBs for bad PEB handling Egli, Samuel
2015-07-06 21:39 ` Richard Weinberger
2015-07-07  7:57   ` Egli, Samuel
2015-07-07 21:09     ` Richard Weinberger
2015-07-08  7:26       ` Egli, Samuel
2015-07-09 10:23       ` Egli, Samuel
2015-07-09 10:29         ` Richard Weinberger [this message]
2015-07-07 10:50 ` Richard Weinberger
2015-07-07 10:59   ` Egli, Samuel
2015-07-07 11:04     ` Richard Weinberger
2015-07-07 11:19       ` Egli, Samuel
2015-07-07 11:24         ` Richard Weinberger
2015-07-07 11:27           ` Egli, Samuel
2015-07-07 19:43             ` Richard Weinberger

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=559E4D26.5080203@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=samuel.egli@siemens.com \
    /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