From: Pintu Agarwal <pintu.ping@gmail.com> To: open list <linux-kernel@vger.kernel.org>, linux-fsdevel <linux-fsdevel@vger.kernel.org>, linux-mtd <linux-mtd@lists.infradead.org>, linux-fsdevel@kvack.org, Phillip Lougher <phillip@squashfs.org.uk>, Sean Nyekjaer <sean@geanix.com> Subject: Kernel 4.14: SQUASHFS error: xz decompression failed, data probably corrupt Date: Mon, 14 Jun 2021 16:09:15 +0530 [thread overview] Message-ID: <CAOuPNLi8_PDyxtt+=j8AsX9pwLWcT4LmVWKj+UcyFOnj4RDBzg@mail.gmail.com> (raw) Hi All, With Kernel 4.14 we are getting squashfs error during bootup resulting in kernel panic. The details are below: Device: ARM-32 board with Cortex-A7 (Single Core) Storage: NAND Flash 512MiB Kernel Version: 4.14.170 (maybe with some Linaro updates) File system: Simple busybox with systemd (without Android) File system type: UBIFS + SQUASHFS UBI Volumes supported: rootfs (ro), others (rw) ------------------- When we try to flash the UBI images and then try to boot the device, we observe the below errors: {{{ [ 5.608810] SQUASHFS error: xz decompression failed, data probably corrupt [ 5.608846] SQUASHFS error: squashfs_read_data failed to read block 0x4d7ffe [ 5.614745] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.621939] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.628274] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.634934] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.641309] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.647954] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.654304] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.660977] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.667309] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.673997] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.680497] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [....] }}} We also observed that some of our Yocto build images will work and boots fine, while sometimes the build images cause this issue. So we wanted to know: a) What could be the root cause of this issue ? b) Is it related to squashfs ? c) If yes, are there any fixes available already in the latest mainline ? Please share some references. Please let us know if anybody encountered this similar issue with squashfs and how did you handle it ? Note: Our current commit in fs/squashfs is pointing at: Squashfs: Compute expected length from inode size rather than block length Thanks, Pintu
WARNING: multiple messages have this Message-ID (diff)
From: Pintu Agarwal <pintu.ping@gmail.com> To: open list <linux-kernel@vger.kernel.org>, linux-fsdevel <linux-fsdevel@vger.kernel.org>, linux-mtd <linux-mtd@lists.infradead.org>, linux-fsdevel@kvack.org, Phillip Lougher <phillip@squashfs.org.uk>, Sean Nyekjaer <sean@geanix.com> Subject: Kernel 4.14: SQUASHFS error: xz decompression failed, data probably corrupt Date: Mon, 14 Jun 2021 16:09:15 +0530 [thread overview] Message-ID: <CAOuPNLi8_PDyxtt+=j8AsX9pwLWcT4LmVWKj+UcyFOnj4RDBzg@mail.gmail.com> (raw) Hi All, With Kernel 4.14 we are getting squashfs error during bootup resulting in kernel panic. The details are below: Device: ARM-32 board with Cortex-A7 (Single Core) Storage: NAND Flash 512MiB Kernel Version: 4.14.170 (maybe with some Linaro updates) File system: Simple busybox with systemd (without Android) File system type: UBIFS + SQUASHFS UBI Volumes supported: rootfs (ro), others (rw) ------------------- When we try to flash the UBI images and then try to boot the device, we observe the below errors: {{{ [ 5.608810] SQUASHFS error: xz decompression failed, data probably corrupt [ 5.608846] SQUASHFS error: squashfs_read_data failed to read block 0x4d7ffe [ 5.614745] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.621939] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.628274] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.634934] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.641309] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.647954] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.654304] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.660977] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.667309] SQUASHFS error: Unable to read data cache entry [4d7ffe] [ 5.673997] SQUASHFS error: Unable to read page, block 4d7ffe, size 7a3c [ 5.680497] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [....] }}} We also observed that some of our Yocto build images will work and boots fine, while sometimes the build images cause this issue. So we wanted to know: a) What could be the root cause of this issue ? b) Is it related to squashfs ? c) If yes, are there any fixes available already in the latest mainline ? Please share some references. Please let us know if anybody encountered this similar issue with squashfs and how did you handle it ? Note: Our current commit in fs/squashfs is pointing at: Squashfs: Compute expected length from inode size rather than block length Thanks, Pintu ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-06-14 10:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 10:39 Pintu Agarwal [this message] 2021-06-14 10:39 ` Kernel 4.14: SQUASHFS error: xz decompression failed, data probably corrupt Pintu Agarwal 2021-06-14 22:22 ` Florian Fainelli 2021-06-14 22:22 ` Florian Fainelli 2021-06-15 5:12 ` Pintu Agarwal 2021-06-15 5:12 ` Pintu Agarwal 2021-06-15 10:01 ` Pintu Agarwal 2021-06-15 10:01 ` Pintu Agarwal 2021-06-16 11:54 ` Pintu Agarwal 2021-06-16 11:54 ` Pintu Agarwal
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='CAOuPNLi8_PDyxtt+=j8AsX9pwLWcT4LmVWKj+UcyFOnj4RDBzg@mail.gmail.com' \ --to=pintu.ping@gmail.com \ --cc=linux-fsdevel@kvack.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=phillip@squashfs.org.uk \ --cc=sean@geanix.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: linkBe 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.