Bug#940138: marked as done (linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources)
Your message dated Sun, 27 Nov 2022 17:03:25 +0100 (CET)
with message-id <20221127160325.AAD43BE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #940138,
regarding linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
940138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940138
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources
- From: Kendy Kutzner <kendy.kutzner@gmail.com>
- Date: Thu, 12 Sep 2019 23:36:18 +0200
- Message-id: <156832417862.3150.1342778763478170774.reportbug@server>
Package: src:linux
Version: 5.2.9-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
aptitude upgrade && aptitude update && reboot
* What exactly did you do (or not do) that was effective (or
ineffective)?
booting into resuce mode for 5.2.0-2 leads to the same kernel panic
booting into 4.19.0-5 works just fine
Screenshots of the panic and the boot menu: https://photos.app.goo.gl/299ykmDM77NBJeDo6
For reference and searchability, the screenshot says
"
RIP ... pci_assign_unassigned_root_bus_resources
...
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
"
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1604
board_vendor: ASUSTeK Computer INC.
board_name: P7H55D-M EVO
board_version: Rev 1.xx
** PCI devices:
<snip. I'm happy to supply if this is really relevant>
** USB devices:
<snip. I'm happy to supply if this is really relevant>
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-5.2.0-2-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.135
ii kmod 26-1
ii linux-base 4.6
Versions of packages linux-image-5.2.0-2-amd64 recommends:
ii apparmor 2.13.3-5
ii firmware-linux-free 3.4
Versions of packages linux-image-5.2.0-2-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.04-3
pn linux-doc-5.2 <none>
Versions of packages linux-image-5.2.0-2-amd64 is related to:
ii firmware-amd-graphics 20190717-2
pn firmware-atheros <none>
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-brcm80211 <none>
pn firmware-cavium <none>
pn firmware-intel-sound <none>
pn firmware-intelwimax <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-libertas <none>
ii firmware-linux-nonfree 20190717-2
ii firmware-misc-nonfree 20190717-2
pn firmware-myricom <none>
pn firmware-netxen <none>
pn firmware-qlogic <none>
pn firmware-realtek <none>
pn firmware-samsung <none>
pn firmware-siano <none>
pn firmware-ti-connectivity <none>
pn xen-hypervisor <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
Reply to: