Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1023123: linux-image-5.19.0-1-arm64: RPi3 fails to boot when headless
2 views
Skip to first unread message
Jan Huijsmans
Oct 30, 2022, 8:40:03 AM10/30/22
to
Package: linux-image-5.19.0-1-arm64
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After upgrading from linux-image-5.18.0-4-arm64 to linux-image-5.19.0-1-arm64
the RPi model 3Bs I have in use headless refuse to boot. The moment you boot
the RPi with screen to check what's happening, it boots.
This issue is for all Raspberry Pi 3 Model B Rev 1.2 devices I have active.
Both RPi 4s run without issue when headless.
Issue found in all kernels > 5.18, only way to solve this is to revert back
to the 5.18 kernel by editing the config.txt on the firmware partition.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.18.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After upgrading from linux-image-5.18.0-4-arm64 to linux-image-5.19.0-1-arm64
the RPi model 3Bs I have in use headless refuse to boot. The moment you boot
the RPi with screen to check what's happening, it boots.
This issue is for all Raspberry Pi 3 Model B Rev 1.2 devices I have active.
Both RPi 4s run without issue when headless.
Issue found in all kernels > 5.18, only way to solve this is to revert back
to the 5.18 kernel by editing the config.txt on the firmware partition.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.18.0-4-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Diederik de Haas
Oct 30, 2022, 7:50:03 PM10/30/22
to
Control: found -1 5.19.6-1
Control: severity -1 important
Control: tag -1 moreinfo
On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans <huys...@trillian.koffie.nu> wrote:
> Package: linux-image-5.19.0-1-arm64
> Severity: critical
> Justification: breaks the whole system
Only affecting RPi3 in certain conditions, thus lowering severity.
Also a factor is https://bugs.debian.org/984873 and
https://bugs.debian.org/984873 where the same bug submitter did not respond to
questions for more info, probably due to email bounces.
Control: severity -1 important
Control: tag -1 moreinfo
On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans <huys...@trillian.koffie.nu> wrote:
> Package: linux-image-5.19.0-1-arm64
> Severity: critical
> Justification: breaks the whole system
Also a factor is https://bugs.debian.org/984873 and
https://bugs.debian.org/984873 where the same bug submitter did not respond to
questions for more info, probably due to email bounces.
Diederik de Haas
Nov 3, 2022, 7:50:04 AM11/3/22
to
Control: found -1 6.0.5-1
Control: fixed -1 6.0.6-2
Control: fixed -1 6.1~rc3-1~exp1
Control: severity -1 grave
Control: tag -1 -moreinfo
Control: tag -1 upstream fixed-upstream
Control: retitle -1 RPi 0-3 fail to boot on kernel 5.19+ without HDMI connected
Control: forwarded -1 https://lore.kernel.org/all/20220929-rpi-pi3-unplugge...@cerno.tech/
On Monday, 31 October 2022 00:37:54 CET Diederik de Haas wrote:
> Control: found -1 5.19.6-1
> Control: severity -1 important
> Control: tag -1 moreinfo
>
> On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans <huys...@trillian.koffie.nu> wrote:
> > Package: linux-image-5.19.0-1-arm64
> > Severity: critical
> > Justification: breaks the whole system
>
> Only affecting RPi3 in certain conditions, thus lowering severity.
I was able to reproduce this on a RPi 1, found that is was reported upstream here:
https://lore.kernel.org/dri-devel/20220922145448....@pengutronix.de/
and found the patches that were applied upstream in 6.1-rc2 where there were
2 commits and saw that 1 commit was backported to the linux-6.0 branch, but
that seemed sufficient as installing kernel 6.0.6-2 from unstable, fixed the
issue.
Control: fixed -1 6.0.6-2
Control: fixed -1 6.1~rc3-1~exp1
Control: severity -1 grave
Control: tag -1 -moreinfo
Control: tag -1 upstream fixed-upstream
Control: retitle -1 RPi 0-3 fail to boot on kernel 5.19+ without HDMI connected
Control: forwarded -1 https://lore.kernel.org/all/20220929-rpi-pi3-unplugge...@cerno.tech/
On Monday, 31 October 2022 00:37:54 CET Diederik de Haas wrote:
> Control: found -1 5.19.6-1
> Control: severity -1 important
> Control: tag -1 moreinfo
>
> On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans <huys...@trillian.koffie.nu> wrote:
> > Package: linux-image-5.19.0-1-arm64
> > Severity: critical
> > Justification: breaks the whole system
>
> Only affecting RPi3 in certain conditions, thus lowering severity.
https://lore.kernel.org/dri-devel/20220922145448....@pengutronix.de/
and found the patches that were applied upstream in 6.1-rc2 where there were
2 commits and saw that 1 commit was backported to the linux-6.0 branch, but
that seemed sufficient as installing kernel 6.0.6-2 from unstable, fixed the
issue.
0 new messages