armhf kernel compiled with gcc-12 fails to boot on pi 3/2

Bug #1993120 reported by Juerg Haefliger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gcc-12 (Ubuntu)
Invalid
Undecided
Unassigned
Kinetic
Invalid
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Kinetic
Fix Released
Medium
Unassigned
linux-raspi (Ubuntu)
Fix Released
Undecided
Unassigned
Kinetic
Fix Released
Medium
Unassigned

Bug Description

Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4.

CVE References

Revision history for this message
Juerg Haefliger (juergh) wrote :

The console log sometimes shows:
[ 30.922073] Alignment trap: not handling instruction fffee3a0 at [<e3412e6e>]

Juerg Haefliger (juergh)
tags: added: kern-4618
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (51.6 KiB)

This bug was fixed in the package linux-raspi - 5.19.0-1004.10

---------------
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium

  * kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)

  * armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
    - [Packaging] raspi: Use gcc-11 for armhf
    - [Config] raspi: updateconfigs for gcc-11 for armhf

  [ Ubuntu: 5.19.0-21.21 ]

  * kinetic/linux: 5.19.0-21.21 -proposed tracker (LP: #1992639)
  * cannot change mount namespace (LP: #1991691)
    - SAUCE: apparmor: Fix getaatr mediation causing snap failures
  * Kernel regresses openjdk on riscv64 (LP: #1992484)
    - SAUCE: Revert "riscv: mmap with PROT_WRITE but no PROT_READ is invalid"

  [ Ubuntu: 5.19.0-20.20 ]

  * kinetic/linux: 5.19.0-20.20 -proposed tracker (LP: #1992408)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/master)
  * Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
    (LP: #1991704)
    - drm/i915: fix null pointer dereference
  * rcu_sched detected stalls on CPUs/tasks (LP: #1967130)
    - [Config] Disable VMAP_STACK on riscv64
  * Disable sv57 as the userspace is not ready (LP: #1991790)
    - SAUCE: riscv: mm: Force disable sv57
  * earlyconsole prints question marks on 5.19.0-1002-generic (LP: #1988984)
    - [Config] Set CONFIG_PWM_SIFIVE=m for riscv64
  * RCU stalls (LP: #1991951)
    - [Config] Harmonize RCU_CPU_STALL_TIMEOUT
  * backport dkms fixes to build modules correctly for hwe-5.19+ kernels with
    custom compiler (LP: #1991664)
    - [Packaging] use versioned gcc-12
    - [Packaging] Update configs with versioned compiler version
  * FTBFS on kinetic (LP: #1990964)
    - SAUCE: uapi: Fixup strace compile error
  * CVE-2022-40768
    - scsi: stex: Properly zero out the passthrough command structure
  * [22.10 FEAT] zKVM: Crypto Passthrough Hotplug - kernel part (LP: #1852741)
    - s390/vfio-ap: use new AP bus interface to search for queue devices
    - s390/vfio-ap: move probe and remove callbacks to vfio_ap_ops.c
    - s390/vfio-ap: manage link between queue struct and matrix mdev
    - s390/vfio-ap: introduce shadow APCB
    - s390/vfio-ap: refresh guest's APCB by filtering AP resources assigned to
      mdev
    - s390/vfio-ap: allow assignment of unavailable AP queues to mdev device
    - s390/vfio-ap: rename matrix_dev->lock mutex to matrix_dev->mdevs_lock
    - s390/vfio-ap: introduce new mutex to control access to the KVM pointer
    - s390/vfio-ap: use proper locking order when setting/clearing KVM pointer
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on assign/unassign
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on queue
      probe/remove
    - s390/vfio-ap: allow hot plug/unplug of AP devices when assigned/unassigned
    - s390/vfio-ap: hot plug/unplug of AP devices when probed/removed
    - s390/vfio-ap: reset queues after adapter/domain unassignment
    - s390/vfio-ap: implement in-use callback for vfio_ap driver
    - s390/vfio-ap: sysfs attribute to display the guest's matrix
    - s390/vfio-ap: handle config changed and scan complete notification...

Changed in linux-raspi (Ubuntu):
status: New → Fix Released
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1993120

tags: added: iso-testing
tags: added: rls-ll-incoming
Revision history for this message
Juerg Haefliger (juergh) wrote :
Stefan Bader (smb)
Changed in linux-raspi (Ubuntu Kinetic):
importance: Undecided → Medium
status: New → Fix Committed
status: Fix Committed → Invalid
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hey, is there anything that needs to be fixed for gcc-12 here? Or was this kernel specific? Can someone confirm?

Changed in gcc-12 (Ubuntu):
status: New → Incomplete
Revision history for this message
Dave Jones (waveform) wrote :

Is there actually an issue in gcc-12 here? Looking at the patch Juerg linked to, it appears to be a kernel issue only?

Revision history for this message
Juerg Haefliger (juergh) wrote :

It's a raspi kernel only issue. The downstream dwc_otg driver is not gcc-12 stack-protector safe.

Changed in linux-raspi (Ubuntu Kinetic):
status: Invalid → Fix Committed
Changed in linux (Ubuntu Kinetic):
status: Fix Committed → Invalid
Changed in gcc-12 (Ubuntu Kinetic):
status: New → Invalid
Changed in gcc-12 (Ubuntu):
status: Incomplete → Invalid
Changed in linux-raspi (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.19.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux verification-needed-kinetic
Juerg Haefliger (juergh)
tags: added: verification-done-kinetic
removed: verification-needed-kinetic
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (100.4 KiB)

This bug was fixed in the package linux - 5.19.0-28.29

---------------
linux (5.19.0-28.29) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-28.29 -proposed tracker (LP: #1999746)

  * mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux
    5.19.0-27.28 (LP: #1999094)
    - fix coredump breakage

linux (5.19.0-27.28) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-27.28 -proposed tracker (LP: #1997794)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * selftests/.../nat6to4 breaks the selftests build (LP: #1996536)
    - [Config] Disable selftests/net/bpf/nat6to4

  * Expose built-in trusted and revoked certificates (LP: #1996892)
    - [Packaging] Expose built-in trusted and revoked certificates

  * support for same series backports versioning numbers (LP: #1993563)
    - [Packaging] sameport -- add support for sameport versioning

  * Add cs35l41 firmware loading support (LP: #1995957)
    - ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code
    - ASoC: cs35l41: Add common cs35l41 enter hibernate function
    - ASoC: cs35l41: Do not print error when waking from hibernation
    - ALSA: hda: cs35l41: Don't dereference fwnode handle
    - ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations
    - ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR()
    - ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41
    - ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls
    - ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly
    - ALSA: hda: cs35l41: Save codec object inside component struct
    - ALSA: hda: cs35l41: Add initial DSP support and firmware loading
    - ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver
    - ALSA: hda: cs35l41: Support reading subsystem id from ACPI
    - ALSA: hda: cs35l41: Support multiple load paths for firmware
    - ALSA: hda: cs35l41: Support Speaker ID for laptops
    - ALSA: hda: cs35l41: Support Hibernation during Suspend
    - ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables
    - ALSA: hda: hda_cs_dsp_ctl: Add fw id strings
    - ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence
    - ALSA: hda: cs35l41: Support Firmware switching and reloading
    - ALSA: hda: cs35l41: Add module parameter to control firmware load
    - Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI
      configurations"
    - ALSA: hda/realtek: More robust component matching for CS35L41
    - [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS

  * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
    - net: wwan: t7xx: Add AP CLDMA

  * Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
    (LP: #1995573)
    - drm/mgag200: Optimize damage clips
    - drm/mgag200: Add FB_DAMAGE_CLIPS support
    - drm/mgag200: Enable atomic gamma lut update

  * TEE Support for CCP driver (LP: #1991608)
    - crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715)
    - platform/x86/amd: pmc: Read...

Changed in linux (Ubuntu Kinetic):
status: Invalid → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-ibm verification-needed-kinetic
removed: verification-done-kinetic
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.19.0-1018.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.19.0-1017.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency-hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19
tags: added: verification-done-jammy verification-done-kinetic
removed: verification-needed-jammy verification-needed-kinetic
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for linux-lowlatency-hwe-5.19 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.1.0-16.16

---------------
linux (6.1.0-16.16) lunar; urgency=medium

  * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- temporarily drop broken dkms

 -- Andrea Righi <email address hidden> Fri, 24 Feb 2023 14:24:48 +0100

Changed in linux (Ubuntu):
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.