All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Landon <cld795@163.com>
Cc: "fercerpav@gmail.com" <fercerpav@gmail.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"a.kartashev@yadro.com" <a.kartashev@yadro.com>
Subject: Re: OpenBMC appear SQUASHFS error problem
Date: Fri, 17 Dec 2021 07:09:16 -0600	[thread overview]
Message-ID: <YbyL/AVWd0MCEJdb@heinlein> (raw)
In-Reply-To: <473d9b80.264c.17dbc330d1d.Coremail.cld795@163.com>

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

On Wed, Dec 15, 2021 at 11:46:42AM +0800, Landon wrote:
> The error appear sometimes,  It doesn't always come up.
> Do you know what the problem is ?
> 
> [   28.829750] proc: Bad value for 'hidepid'
> [   29.253033] SQUASHFS error: xz decompression failed, data probably corrupt
> [   29.260761] SQUASHFS error: squashfs_read_data failed to read block 0x1b3f8cc

The data in the SquashFS volume is corrupted.  By "the error appears sometimes"
do you mean that:

1. Sometimes you build an image and it is garbage but other times you build an
   image and it works fine?

2. Some machines can be flashed with an image and they work, but other machines
   can be flashed with an image and they fail?

3. The same machine can be flashed with an image and sometimes it works and
   sometimes it doesn't?

4. A machine can be flashed once and then some reboots work fine and some
   reboots do not?

#1 would likely be a problem with your flash layout where the squashfs is
getting corrupted by an earlier part of the image being too big.

#2-4 would likely be some hardware and/or SPI configuration issue.

I would likely try slowing down the SPI bus speeds and/or turning of QSPI if
you have that enabled to get something stable and then work from there.  If this
is a new board it is possible you have some SI issues on the SPI line
(reflections, bad capacitance, incorrect level shifter IC for SPI speeds, etc.).

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-12-17 13:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1637828525.15424.openbmc@lists.ozlabs.org>
2021-11-25  8:29 ` openBMC pwm-fan control policy Landon
2021-11-25  8:46   ` Paul Fertser
2021-11-26  5:26     ` Landon
2021-11-26  5:55       ` Landon
2021-11-26 21:57         ` Paul Fertser
2021-11-29  9:43           ` Landon
2021-11-29 10:22             ` Andrei Kartashev
2021-12-02  9:11               ` Landon
2021-12-07  1:45                 ` Landon
2021-12-07  7:37                   ` Landon
2021-12-07  8:05                     ` Andrei Kartashev
2021-12-15  2:39                       ` Landon
2021-12-15  3:21                       ` OpenBMC web sometimes jump back to the login screen problem Landon
2021-12-15  3:46                         ` OpenBMC appear SQUASHFS error problem Landon
2021-12-15  5:36                           ` Landon
2021-12-16  3:19                           ` Landon
2021-12-17  6:39                           ` Landon
2021-12-17 13:09                           ` Patrick Williams [this message]
2021-12-15 18:51                         ` OpenBMC web sometimes jump back to the login screen problem Bills, Jason M
2021-12-16  7:05                       ` Landon
2021-12-17 13:10                         ` Patrick Williams
2022-01-21  3:12                           ` OpenBMC Switching function of web Landon
2022-01-21  4:24                           ` Landon
2022-01-24  8:24                             ` Landon
2022-06-13  7:49                               ` OpenBMC state manager problem Landon
2022-06-16  7:34                                 ` CHLI30
2022-06-13  8:13                               ` Landon
2022-06-14  1:58                                 ` Landon
2022-06-15  7:42                                   ` Landon

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=YbyL/AVWd0MCEJdb@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=a.kartashev@yadro.com \
    --cc=cld795@163.com \
    --cc=fercerpav@gmail.com \
    --cc=openbmc@lists.ozlabs.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.