This bug was fixed in the package linux-raspi - 5.11.0-1003.3

---------------
linux-raspi (5.11.0-1003.3) hirsute; urgency=medium

  * hirsute/linux-raspi: 5.11.0-1003.3 -proposed tracker (LP: #1917734)

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants
    - [Packaging] update update.conf

  * Miscellaneous Ubuntu changes
    - [Packaging] raspi: Initial version of linux-raspi for Hirsute
    - [Config] raspi: updateconfigs after rebase to Ubuntu-5.11.0-11.12
    - [Packaging] raspi: Set disable_d_i=true in hooks.mk
    - [Packaging] raspi: Add dctrl-tools to Build-Depends
    - [Packaging] raspi: Correctly implement noudeb build profiles
    - [Packaging] raspi: remove Provides: aufs-dkms

  [ Ubuntu: 5.11.0-11.12 ]

  * hirsute/linux: 5.11.0-11.12 -proposed tracker (LP: #1917335)
  * Packaging resync (LP: #1786013)
    - update dkms package versions
    - [Packaging] update variants
  * Support no udeb profile (LP: #1916095)
    - [Packaging] replace custom filter script with dctrl-tools
    - [Packaging] correctly implement noudeb build profiles.
  * Miscellaneous Ubuntu changes
    - [Packaging] dkms-versions -- remove nvidia-graphics-drivers-440-server
    - [Debian] run ubuntu-regression-suite for linux-unstable
    - [Packaging] remove Provides: aufs-dkms
    - [Packaging] Change source package name to linux
    - [Config] update gcc version in config due to toolchain update
  * Miscellaneous upstream changes
    - Revert "UBUNTU: [Config] disable nvidia and nvidia_server builds"
    - Xen/x86: don't bail early from clear_foreign_p2m_mapping()
    - Xen/x86: also check kernel mapping in set_foreign_p2m_mapping()
    - Xen/gntdev: correct dev_bus_addr handling in gntdev_map_grant_pages()
    - Xen/gntdev: correct error checking in gntdev_map_grant_pages()
    - xen/arm: don't ignore return errors from set_phys_to_machine
    - xen-blkback: don't "handle" error by BUG()
    - xen-netback: don't "handle" error by BUG()
    - xen-scsiback: don't "handle" error by BUG()
    - xen-blkback: fix error handling in xen_blkbk_map()
    - tty: protect tty_write from odd low-level tty disciplines
    - Bluetooth: btusb: Always fallback to alt 1 for WBS
    - media: pwc: Use correct device for DMA
    - bpf: Fix truncation handling for mod32 dst reg wrt zero
    - HID: make arrays usage and value to be the same
    - USB: quirks: sort quirk entries
    - usb: quirks: add quirk to start video capture on ELMO L-12F document 
camera
      reliable
    - ntfs: check for valid standard information attribute
    - Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working
    - arm64: tegra: Add power-domain for Tegra210 HDA
    - hwmon: (dell-smm) Add XPS 15 L502X to fan control blacklist
    - KVM: x86: Zap the oldest MMU pages, not the newest
    - KVM: do not assume PTE is writable after follow_pfn
    - mm: provide a saner PTE walking API for modules
    - KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped()

 -- Juerg Haefliger <jue...@canonical.com>  Thu, 04 Mar 2021 14:42:19
+0100

** Changed in: linux-raspi (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1907432

Title:
  Raspberry Pi 400 Kernel Panic

Status in linux-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi source package in Groovy:
  Fix Released

Bug description:
  When I power the Pi 400 down (with the key-combination on the pi 400
  or with the navigation from the top right), a line like this is on
  screen:

  [59095.049506] reboot: Power down

  or that:
  [25784.810857] reboot: Power down

  Under this line, the cursor is frozen.
  After a while, suddenly, the text scrolls and stops after a while. I can read 
something about "Kernel Panic" on screen.

  I cannot power the device off. I have to pull the power plug to shut
  it down, or to re-plug it to reset it. The power-button (2sec) does
  not work, 10 seconds reset signal, neither.

  Here you can find my initial question to this phenomenon:
  https://answers.launchpad.net/ubuntu/+question/694349

  This I should include:
  Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 
10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu 
SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020

  I hope this report includes enough information. If not, please do not
  hesitate to contact me! Thanks so much for this project and thx for
  being a part of it! <3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-1008-raspi 5.8.0-1008.11
  ProcVersionSignature: Ubuntu 5.8.0-1008.11-raspi 5.8.17
  Uname: Linux 5.8.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  9 10:40:08 2020
  ImageMediaBuild: 20201022
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1907432/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to