public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Mark Brown <broonie@kernel.org>
Cc: Pavel Machek <pavel@denx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hagar@microsoft.com,
	chris.paterson2@renesas.com
Subject: Re: [PATCH 6.11 000/249] 6.11.7-rc2 review
Date: Thu, 7 Nov 2024 15:28:12 +0100	[thread overview]
Message-ID: <ZyzOfIPHTEjq5W1+@duo.ucw.cz> (raw)
In-Reply-To: <7a791358-63ff-41e1-b7f0-e687df21047b@sirena.org.uk>

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

Hi!

> > > This is the start of the stable review cycle for the 6.11.7 release.
> > > There are 249 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > 
> > CIP testing has problem with BeagleBone Black on 6.11:
> > 
> > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.11.y
> 
> My Beaglebone Black jobs ran fairly happily, eg:
> 
>    https://lava.sirena.org.uk/scheduler/job/951530
> 
> Looking at your logs:
> 
>    https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/8295477303
> 
> you seem to be seeing an infrastructure issue:
> 
> * lava.pdu-reboot [pass]
> * lava.bootloader-commands [fail]
> * lava.uboot-commands [fail]
> * lava.uboot-action [fail]
> * lava.power-off [pass]
> * lava.job [fail]
> 
> The job is failing in the bootloader:
> 
>    https://lava.ciplatform.org/scheduler/job/1218595
> 
> shows:
> 
> | => bootz 0x82000000 - 0x88000000
> | zimage: Bad magic!
> 
> I didn't check but this almost always indicates that the download to the
> board was corrupted due to some image size having grown large enough to
> overwrite the adjacent image, you'll need to adjust the load addresses.

Yep, thanks, it does not seem to be kernel issue. People from our Q&A
team are investigating.

Best regards,
								Pavel


-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

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

  reply	other threads:[~2024-11-07 14:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  6:47 [PATCH 6.11 000/249] 6.11.7-rc2 review Greg Kroah-Hartman
2024-11-07  8:24 ` Luna Jernberg
2024-11-07 12:54 ` Pavel Machek
2024-11-07 13:28   ` Mark Brown
2024-11-07 14:28     ` Pavel Machek [this message]
2024-11-07 13:43 ` Jon Hunter
2024-11-07 14:26 ` Peter Schneider
2024-11-07 14:55 ` Mark Brown
2024-11-07 19:57 ` Florian Fainelli
2024-11-08  2:09 ` Ron Economos
2024-11-08  7:14 ` [PATCH 6.11] " Hardik Garg
2024-11-08 11:44 ` [PATCH 6.11 000/249] " Naresh Kamboju
2024-11-08 15:02 ` Muhammad Usama Anjum
2024-11-08 15:46 ` Justin Forbes
2024-11-08 15:58 ` Markus Reichelt
2024-11-10 15:53 ` Guenter Roeck
2024-11-12  8:33   ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2024-11-07 16:44 Ronald Warsow

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=ZyzOfIPHTEjq5W1+@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=chris.paterson2@renesas.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hagar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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