All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Weiss <luca@z3ntu.xyz>
To: linux-arm-msm@vger.kernel.org
Cc: linux-mtd@lists.infradead.org,
	Richard Weinberger <richard@nod.at>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Boot fail with UBIFS_FS=y on Qualcomm msm8974/msm8226
Date: Thu, 22 Sep 2022 17:55:51 +0200	[thread overview]
Message-ID: <2845511.e9J7NaK4W3@g550jk> (raw)

Hey all,

sometime last year (June 2021?) I first noticed that with arm32 qcom_defconfig 
under some circumstances I get weird boot failures on msm8974-fairphone-fp2, 
and lately also seeing similar with apq8026-lg-lenok.

In short, with CONFIG_UBIFS_FS=y there's nothing from serial console, nothing 
from earlycon, just nothing on serial at all. As soon as I disable this config 
option and rebuild it boots up fine again.

At some point I also got this from fp2 logs, after I changed something in the 
boot procedure (maybe fastboot boot instead of fastboot flash? I don't recall)

> Error: invalid dtb and unrecognized/unsupported machine ID
>   r1=0x00000000, r2=0x00000000
> Available machine support:
> 
> ID (hex)        NAME
> ffffffff        Generic DT based system
> 
> Please check your kernel config and/or bootloader.

With CONFIG_UBIFS_FS=m and loading the module at runtime seems to work fine (at 
least nothing visibly broke) although I didn't try mounting anything with that 
file system.

Does anyone maybe have an idea what might cause this and/or how to debug this? 
While just disabling UBIFS_FS in my config solves the issue I feel like this 
should be resolved, because I also sometimes forget that I have to disable 
this from qcom_defconfig and then wonder why my boards aren't booting.

Regards
Luca



WARNING: multiple messages have this Message-ID (diff)
From: Luca Weiss <luca@z3ntu.xyz>
To: linux-arm-msm@vger.kernel.org
Cc: linux-mtd@lists.infradead.org,
	Richard Weinberger <richard@nod.at>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Boot fail with UBIFS_FS=y on Qualcomm msm8974/msm8226
Date: Thu, 22 Sep 2022 17:55:51 +0200	[thread overview]
Message-ID: <2845511.e9J7NaK4W3@g550jk> (raw)

Hey all,

sometime last year (June 2021?) I first noticed that with arm32 qcom_defconfig 
under some circumstances I get weird boot failures on msm8974-fairphone-fp2, 
and lately also seeing similar with apq8026-lg-lenok.

In short, with CONFIG_UBIFS_FS=y there's nothing from serial console, nothing 
from earlycon, just nothing on serial at all. As soon as I disable this config 
option and rebuild it boots up fine again.

At some point I also got this from fp2 logs, after I changed something in the 
boot procedure (maybe fastboot boot instead of fastboot flash? I don't recall)

> Error: invalid dtb and unrecognized/unsupported machine ID
>   r1=0x00000000, r2=0x00000000
> Available machine support:
> 
> ID (hex)        NAME
> ffffffff        Generic DT based system
> 
> Please check your kernel config and/or bootloader.

With CONFIG_UBIFS_FS=m and loading the module at runtime seems to work fine (at 
least nothing visibly broke) although I didn't try mounting anything with that 
file system.

Does anyone maybe have an idea what might cause this and/or how to debug this? 
While just disabling UBIFS_FS in my config solves the issue I feel like this 
should be resolved, because I also sometimes forget that I have to disable 
this from qcom_defconfig and then wonder why my boards aren't booting.

Regards
Luca



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2022-09-22 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 15:55 Luca Weiss [this message]
2022-09-22 15:55 ` Boot fail with UBIFS_FS=y on Qualcomm msm8974/msm8226 Luca Weiss
2022-09-22 16:45 ` Brian Masney
2022-09-22 16:45   ` Brian Masney

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=2845511.e9J7NaK4W3@g550jk \
    --to=luca@z3ntu.xyz \
    --cc=alexeymin@postmarketos.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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.