Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1012210: linux-image-5.10.0-14-amd64: Kernels of Bullseye and Testing (5.10 and 5.17) hang at boot
126 views
Skip to first unread message
Markus Kolb
Jun 1, 2022, 6:30:04 AM6/1/22
to
Package: src:linux
Version: 5.10.113-1
Severity: important
Dear Maintainer,
I've updated an older typewriter computer from Stretch to Buster and
from there to Bullseye.
The kernel linux-image-4.19.0-20-amd64 from Buster works.
This one is used at the moment for reportbug!
But anything from the newer versions hangs during boot.
I've tried the release kernel of Bullseye,
the security-updated linux-image-5.10.0-14-amd64,
the newest one from backports
and the latest version from testing, which has been a 5.17 version.
I've tried to start up with boot option boot_delay=1000, but then it
already hangs/crashes after the line of loading the initial ramdisk.
Can only switch off/on the computer afterwards. Num-lock switch is
dead.
Without the boot_delay option, there is some fast kernel output and I've
filmed with my camera.
Between working and crashing kernel there is some difference in the SATA
ports. And these are the last lines of output before the screen becomes
black and there isn't any reaction of the computer any longer.
This is a working boot with the Buster-kernel:
[ 1.800181] hub 7-0:1.0: USB hub found
[ 1.800226] hub 7-0:1.0: 2 ports detected
[ 1.816820] scsi host1: ahci
[ 1.817122] scsi host3: ahci
[ 1.817395] scsi host4: ahci
[ 1.817663] scsi host5: ahci
[ 1.817939] scsi host6: ahci
[ 1.818297] scsi host7: ahci
[ 1.818430] ata3: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6100 irq 25
[ 1.818489] ata4: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6180 irq 25
[ 1.818547] ata5: DUMMY
[ 1.818582] ata6: DUMMY
[ 1.818618] ata7: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6300 irq 25
[ 1.818678] ata8: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6380 irq 25
[ 1.819353] scsi host2: ata_generic
[ 1.819448] ata1: PATA max UDMA/100 cmd 0x1218 ctl 0x1240 bmdma
0x1200 irq 18
[ 1.819494] ata2: PATA max UDMA/100 cmd 0x1220 ctl 0x1244 bmdma
0x1208 irq 18
[ 1.879056] pci 0000:00:00.0: Intel Q35 Chipset
[ 1.879122] pci 0000:00:00.0: detected gtt size: 524288K total,
262144K mappable
[ 1.879855] pci 0000:00:00.0: detected 8192K stolen memory
[ 1.879947] [drm] Replacing VGA console driver
[ 1.880476] Console: switching to colour dummy device 80x25
[ 1.880940] [drm] ACPI BIOS requests an excessive sleep of 1124034056
ms, using 1500 ms instead
[ 1.884726] [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[ 1.884730] [drm] Driver supports precise vblank timestamp query.
With Bullseye-kernel I can't see the line for scsi hosts 1 and 3.
But maybe the order is differently and it is not viewable before the
screen becomes black. So maybe also a problem with console switching and
i915 graphic?
I'll upload the video to opened bug report.
I hope you can help me?! Do you know some boot options for the kernel I
could try to get the newer kernels to work?
br
Markus
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: Hewlett-Packard
product_name: HP Compaq dc7800p Small Form Factor
product_version:
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: 786F1 v01.35
board_vendor: Hewlett-Packard
board_name: 0AA8h
board_version:
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02)
Subsystem: Hewlett-Packard Company 82Q35 Express DRAM Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 82Q35 Express Integrated Graphics Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f0100000 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 1210 [size=8]
Region 2: Memory at e0000000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at f0000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02)
Subsystem: Hewlett-Packard Company 82Q35 Express MEI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f01a7100 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel modules: mei_me
00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
Subsystem: Hewlett-Packard Company 82Q35 Express PT IDER Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 0: I/O ports at 1218 [size=8]
Region 1: I/O ports at 1240 [size=4]
Region 2: I/O ports at 1220 [size=8]
Region 3: I/O ports at 1244 [size=4]
Region 4: I/O ports at 1200 [size=16]
Capabilities: <access denied>
Kernel driver in use: ata_generic
Kernel modules: ata_generic
00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company 82Q35 Express Serial KT Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at 1228 [size=8]
Region 1: Memory at f01a4000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02)
Subsystem: Hewlett-Packard Company 82566DM-2 Gigabit Network Connection [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 26
Region 0: Memory at f0180000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f01a5000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 1100 [disabled] [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 4: I/O ports at 1120 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at 1140 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 22
Region 4: I/O ports at 1160 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB2 EHCI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 22
Region 0: Memory at f01a6800 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) HD Audio Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 24
Region 0: Memory at f01a0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=20, subordinate=20, sec-latency=0
I/O behind bridge: 00002000-00002fff [size=4K]
Memory behind bridge: f8000000-f81fffff [size=2M]
Prefetchable memory behind bridge: 00000000f8200000-00000000f83fffff [size=2M]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 21
Bus: primary=00, secondary=30, subordinate=30, sec-latency=0
I/O behind bridge: 00003000-00003fff [size=4K]
Memory behind bridge: f8400000-f85fffff [size=2M]
Prefetchable memory behind bridge: 00000000f8600000-00000000f87fffff [size=2M]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 4: I/O ports at 1180 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at 11a0 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB2 EHCI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 0: Memory at f01a6c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=32
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller [8086:2914] (rev 02)
Subsystem: Hewlett-Packard Company 82801IO (ICH9DO) LPC Interface Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 25
Region 0: I/O ports at 1230 [size=8]
Region 1: I/O ports at 1248 [size=4]
Region 2: I/O ports at 1238 [size=8]
Region 3: I/O ports at 124c [size=4]
Region 4: I/O ports at 11c0 [size=32]
Region 5: Memory at f01a6000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
** USB devices:
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-20-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-5.10.0-14-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.140
ii kmod 28-1
ii linux-base 4.6
Versions of packages linux-image-5.10.0-14-amd64 recommends:
pn apparmor <none>
pn firmware-linux-free <none>
Versions of packages linux-image-5.10.0-14-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.04-20
pn linux-doc-5.10 <none>
Versions of packages linux-image-5.10.0-14-amd64 is related to:
pn firmware-amd-graphics <none>
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>
pn firmware-linux-nonfree <none>
ii firmware-misc-nonfree 20210315-3
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
Version: 5.10.113-1
Severity: important
Dear Maintainer,
I've updated an older typewriter computer from Stretch to Buster and
from there to Bullseye.
The kernel linux-image-4.19.0-20-amd64 from Buster works.
This one is used at the moment for reportbug!
But anything from the newer versions hangs during boot.
I've tried the release kernel of Bullseye,
the security-updated linux-image-5.10.0-14-amd64,
the newest one from backports
and the latest version from testing, which has been a 5.17 version.
I've tried to start up with boot option boot_delay=1000, but then it
already hangs/crashes after the line of loading the initial ramdisk.
Can only switch off/on the computer afterwards. Num-lock switch is
dead.
Without the boot_delay option, there is some fast kernel output and I've
filmed with my camera.
Between working and crashing kernel there is some difference in the SATA
ports. And these are the last lines of output before the screen becomes
black and there isn't any reaction of the computer any longer.
This is a working boot with the Buster-kernel:
[ 1.800181] hub 7-0:1.0: USB hub found
[ 1.800226] hub 7-0:1.0: 2 ports detected
[ 1.816820] scsi host1: ahci
[ 1.817122] scsi host3: ahci
[ 1.817395] scsi host4: ahci
[ 1.817663] scsi host5: ahci
[ 1.817939] scsi host6: ahci
[ 1.818297] scsi host7: ahci
[ 1.818430] ata3: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6100 irq 25
[ 1.818489] ata4: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6180 irq 25
[ 1.818547] ata5: DUMMY
[ 1.818582] ata6: DUMMY
[ 1.818618] ata7: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6300 irq 25
[ 1.818678] ata8: SATA max UDMA/133 abar m2048@0xf01a6000 port
0xf01a6380 irq 25
[ 1.819353] scsi host2: ata_generic
[ 1.819448] ata1: PATA max UDMA/100 cmd 0x1218 ctl 0x1240 bmdma
0x1200 irq 18
[ 1.819494] ata2: PATA max UDMA/100 cmd 0x1220 ctl 0x1244 bmdma
0x1208 irq 18
[ 1.879056] pci 0000:00:00.0: Intel Q35 Chipset
[ 1.879122] pci 0000:00:00.0: detected gtt size: 524288K total,
262144K mappable
[ 1.879855] pci 0000:00:00.0: detected 8192K stolen memory
[ 1.879947] [drm] Replacing VGA console driver
[ 1.880476] Console: switching to colour dummy device 80x25
[ 1.880940] [drm] ACPI BIOS requests an excessive sleep of 1124034056
ms, using 1500 ms instead
[ 1.884726] [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[ 1.884730] [drm] Driver supports precise vblank timestamp query.
With Bullseye-kernel I can't see the line for scsi hosts 1 and 3.
But maybe the order is differently and it is not viewable before the
screen becomes black. So maybe also a problem with console switching and
i915 graphic?
I'll upload the video to opened bug report.
I hope you can help me?! Do you know some boot options for the kernel I
could try to get the newer kernels to work?
br
Markus
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor: Hewlett-Packard
product_name: HP Compaq dc7800p Small Form Factor
product_version:
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: 786F1 v01.35
board_vendor: Hewlett-Packard
board_name: 0AA8h
board_version:
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02)
Subsystem: Hewlett-Packard Company 82Q35 Express DRAM Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company 82Q35 Express Integrated Graphics Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f0100000 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 1210 [size=8]
Region 2: Memory at e0000000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at f0000000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02)
Subsystem: Hewlett-Packard Company 82Q35 Express MEI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f01a7100 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel modules: mei_me
00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
Subsystem: Hewlett-Packard Company 82Q35 Express PT IDER Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 18
Region 0: I/O ports at 1218 [size=8]
Region 1: I/O ports at 1240 [size=4]
Region 2: I/O ports at 1220 [size=8]
Region 3: I/O ports at 1244 [size=4]
Region 4: I/O ports at 1200 [size=16]
Capabilities: <access denied>
Kernel driver in use: ata_generic
Kernel modules: ata_generic
00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company 82Q35 Express Serial KT Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 17
Region 0: I/O ports at 1228 [size=8]
Region 1: Memory at f01a4000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: serial
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02)
Subsystem: Hewlett-Packard Company 82566DM-2 Gigabit Network Connection [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 26
Region 0: Memory at f0180000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f01a5000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 1100 [disabled] [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 4: I/O ports at 1120 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at 1140 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 22
Region 4: I/O ports at 1160 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB2 EHCI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin C routed to IRQ 22
Region 0: Memory at f01a6800 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) HD Audio Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 24
Region 0: Memory at f01a0000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=20, subordinate=20, sec-latency=0
I/O behind bridge: 00002000-00002fff [size=4K]
Memory behind bridge: f8000000-f81fffff [size=2M]
Prefetchable memory behind bridge: 00000000f8200000-00000000f83fffff [size=2M]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin B routed to IRQ 21
Bus: primary=00, secondary=30, subordinate=30, sec-latency=0
I/O behind bridge: 00003000-00003fff [size=4K]
Memory behind bridge: f8400000-f85fffff [size=2M]
Prefetchable memory behind bridge: 00000000f8600000-00000000f87fffff [size=2M]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 4: I/O ports at 1180 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB UHCI Controller [103c:2818]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 21
Region 4: I/O ports at 11a0 [size=32]
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) USB2 EHCI Controller [103c:2818]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 20
Region 0: Memory at f01a6c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) (prog-if 01 [Subtractive decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=07, subordinate=07, sec-latency=32
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller [8086:2914] (rev 02)
Subsystem: Hewlett-Packard Company 82801IO (ICH9DO) LPC Interface Controller [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [103c:2818]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 25
Region 0: I/O ports at 1230 [size=8]
Region 1: I/O ports at 1248 [size=4]
Region 2: I/O ports at 1238 [size=8]
Region 3: I/O ports at 124c [size=4]
Region 4: I/O ports at 11c0 [size=32]
Region 5: Memory at f01a6000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
Kernel modules: ahci
** USB devices:
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-20-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-5.10.0-14-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.140
ii kmod 28-1
ii linux-base 4.6
Versions of packages linux-image-5.10.0-14-amd64 recommends:
pn apparmor <none>
pn firmware-linux-free <none>
Versions of packages linux-image-5.10.0-14-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.04-20
pn linux-doc-5.10 <none>
Versions of packages linux-image-5.10.0-14-amd64 is related to:
pn firmware-amd-graphics <none>
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>
pn firmware-linux-nonfree <none>
ii firmware-misc-nonfree 20210315-3
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
Diederik de Haas
Jun 1, 2022, 7:30:03 AM6/1/22
to
Control: found -1 linux/5.17.3-1
On Wednesday, 1 June 2022 12:17:56 CEST Markus Kolb wrote:
> The kernel linux-image-4.19.0-20-amd64 from Buster works.
> This one is used at the moment for reportbug!
>
> But anything from the newer versions hangs during boot.
> I've tried the release kernel of Bullseye,
> the security-updated linux-image-5.10.0-14-amd64,
> the newest one from backports
> and the latest version from testing, which has been a 5.17 version.
>
> ...
and that got fixed in version 5.17.6-1, but due to the openssl transition, that
didn't get into Testing (which currently has 5.17.3-1).
The current version in Sid/Unstable is 5.17.11-1 and it would be useful if you
could test that as well.
This does seem like a different issue as it happens with much older kernels
then that bug report, so I don't expect it to fix it.
But it's still useful info and it may result in some extra info.
On Wednesday, 1 June 2022 12:17:56 CEST Markus Kolb wrote:
> The kernel linux-image-4.19.0-20-amd64 from Buster works.
> This one is used at the moment for reportbug!
>
> But anything from the newer versions hangs during boot.
> I've tried the release kernel of Bullseye,
> the security-updated linux-image-5.10.0-14-amd64,
> the newest one from backports
> and the latest version from testing, which has been a 5.17 version.
>
>
> Between working and crashing kernel there is some difference in the SATA
> ports. And these are the last lines of output before the screen becomes
> black and there isn't any reaction of the computer any longer.
Bug https://bugs.debian.org/1006149 was also about a boot failure (and SATA)
> Between working and crashing kernel there is some difference in the SATA
> ports. And these are the last lines of output before the screen becomes
> black and there isn't any reaction of the computer any longer.
and that got fixed in version 5.17.6-1, but due to the openssl transition, that
didn't get into Testing (which currently has 5.17.3-1).
The current version in Sid/Unstable is 5.17.11-1 and it would be useful if you
could test that as well.
This does seem like a different issue as it happens with much older kernels
then that bug report, so I don't expect it to fix it.
But it's still useful info and it may result in some extra info.
Diederik de Haas
Jun 1, 2022, 7:40:03 AM6/1/22
to
On Wednesday, 1 June 2022 13:23:26 CEST Diederik de Haas wrote:
> The current version in Sid/Unstable is 5.17.11-1 and it would be useful if
> you could test that as well.
In the screenshot you sent to the bug report, I saw mentions of an USB hub.
> The current version in Sid/Unstable is 5.17.11-1 and it would be useful if
> you could test that as well.
Could you try to unplug any peripherals that are not strictly needed?
IOW: only attach a keyboard and monitor and see if that makes a difference.
Diederik de Haas
Jun 1, 2022, 1:00:04 PM6/1/22
to
Hi Markus,
On Wednesday, 1 June 2022 17:22:35 CEST Markus Kolb wrote:
> I've just tested
> linux-image-5.17.0-2-amd64 5.17.6-1+b1
> but also doesn't boot.
I was expecting 5.17.11-1, but that version does have the SATA fix from the
other bug report too. And there's another thing to focus on ...
> The computer has only attached USB mouse. The keyboard is PS/2. Next to
> this only Ethernet cable and VGA is connected.
Ok, that is fine.
> In the meantime I've built
> linux-image-5.10.119
> from kernel.org sources and it boots successful.
... and this is VERY significant (afaict) :-)
> I've used localmodconfig while running the
> linux-image-4.19.0-20-amd64 4.19.235-1
> and afterwards used mostly defaults for new config options but also
> deactivated many options and modules, I don't need and was quite sure
> about it, for faster build finishing.
The exact implications of this is 'above my pay grade', but hopefully one of
the kernel maintainers (who should understand this) chimes in.
> I've attached dmesg output, config and lsmod output for my 5.10.119.
> Maybe it helps to find the right patch.
Via https://packages.debian.org/bullseye/linux-config-5.10 I retrieved the
Debian kernel config for 5.10.106-1 (which is likely close enough) and compared
it with the config you attached.
The diff was *huge*, but the fact that you were able to boot your self-built
5.10 kernel while the Debian 5.10 kernel failed, points (strongly) towards a
Debian kernel configuration difference which is the cause of this bug.
I have no idea how to make any intelligent recommendations wrt kernel config
changes, so I have to defer to people 'smarter' then me (wrt this).
> Next I build 5.10.114 which is date corresponding to the 5.17.6 and see
> if I can find the version with patch with going upwards.
> Or someone already any idea what it could be? :-)
Building 5.10.113 with your custom config sounds like a good test case.
Debian's 5.10.113 didn't boot (with Debian's config), but if the (exact) same
version with a different config does work, then it seems almost certain to me
that the bug is in the Debian kernel configuration.
Cheers,
Diederik
On Wednesday, 1 June 2022 17:22:35 CEST Markus Kolb wrote:
> linux-image-5.17.0-2-amd64 5.17.6-1+b1
> but also doesn't boot.
I was expecting 5.17.11-1, but that version does have the SATA fix from the
other bug report too. And there's another thing to focus on ...
> The computer has only attached USB mouse. The keyboard is PS/2. Next to
> this only Ethernet cable and VGA is connected.
Ok, that is fine.
> In the meantime I've built
> linux-image-5.10.119
> from kernel.org sources and it boots successful.
... and this is VERY significant (afaict) :-)
> I've used localmodconfig while running the
> linux-image-4.19.0-20-amd64 4.19.235-1
> and afterwards used mostly defaults for new config options but also
> deactivated many options and modules, I don't need and was quite sure
> about it, for faster build finishing.
The exact implications of this is 'above my pay grade', but hopefully one of
the kernel maintainers (who should understand this) chimes in.
> I've attached dmesg output, config and lsmod output for my 5.10.119.
> Maybe it helps to find the right patch.
Via https://packages.debian.org/bullseye/linux-config-5.10 I retrieved the
Debian kernel config for 5.10.106-1 (which is likely close enough) and compared
it with the config you attached.
The diff was *huge*, but the fact that you were able to boot your self-built
5.10 kernel while the Debian 5.10 kernel failed, points (strongly) towards a
Debian kernel configuration difference which is the cause of this bug.
I have no idea how to make any intelligent recommendations wrt kernel config
changes, so I have to defer to people 'smarter' then me (wrt this).
> Next I build 5.10.114 which is date corresponding to the 5.17.6 and see
> if I can find the version with patch with going upwards.
> Or someone already any idea what it could be? :-)
Building 5.10.113 with your custom config sounds like a good test case.
Debian's 5.10.113 didn't boot (with Debian's config), but if the (exact) same
version with a different config does work, then it seems almost certain to me
that the bug is in the Debian kernel configuration.
Cheers,
Diederik
Ben Hutchings
Jun 2, 2022, 11:40:08 AM6/2/22
to
On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
> In the patches
>
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch
>
> there is introduced the kernel config option
> INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
> but it is not handled anywhere in the code.
It is handled implicitly. When that config symbol is enabled, both
INTEL_IOMMU_DEFAULT_ON and INTEL_IOMMU_DEFAULT_OFF are disabled.
> I think you have mixed up the defaults of the configuration and settings
> of igfx_off and intgpu_off somehow which sets something up resulting in
> a wrong config for my boot. intgpu_off boot config itself doesn't change
> anything, with the Debian kernel I need igfx_off.
>
> At
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch#L66
> you should compare 10 chars and not only 8, but is more or less
> correctness.
Well spotted. This is because at some point in development I changed
the name of the option from igpu_off to intgpu_off. The patch
description also has the earlier name. I'll correct that.
> Maybe this
> static int dmar_map_intgpu =
> IS_ENABLED(CONFIG_INTEL_IOMMU_DEFAULT_ON);
> at
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch#L74
> should be
> static int dmar_map_intgpu =
> IS_ENABLED(INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF);
No, the whole point of INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF is to turn
that off by default while still enabling the IOMMU for other devices.
Based on the log from your self-built kernel, it seems like your system
should work with the kernel parameter "intel_iommu=on". Can you test
whether that makes a difference with the Debian kernels?
Ben.
> or the negated value, not sure at the moment, what a y or n should mean
> in this config and if the assignments of 0 or 1 are correct everywhere.
--
Ben Hutchings
Humour is the best antidote to reality.
[...]
> In the patches
>
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch
>
> there is introduced the kernel config option
> INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
> but it is not handled anywhere in the code.
It is handled implicitly. When that config symbol is enabled, both
INTEL_IOMMU_DEFAULT_ON and INTEL_IOMMU_DEFAULT_OFF are disabled.
> I think you have mixed up the defaults of the configuration and settings
> of igfx_off and intgpu_off somehow which sets something up resulting in
> a wrong config for my boot. intgpu_off boot config itself doesn't change
> anything, with the Debian kernel I need igfx_off.
>
> At
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch#L66
> you should compare 10 chars and not only 8, but is more or less
> correctness.
Well spotted. This is because at some point in development I changed
the name of the option from igpu_off to intgpu_off. The patch
description also has the earlier name. I'll correct that.
> Maybe this
> static int dmar_map_intgpu =
> IS_ENABLED(CONFIG_INTEL_IOMMU_DEFAULT_ON);
> at
>
> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch#L74
> should be
> static int dmar_map_intgpu =
> IS_ENABLED(INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF);
No, the whole point of INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF is to turn
that off by default while still enabling the IOMMU for other devices.
Based on the log from your self-built kernel, it seems like your system
should work with the kernel parameter "intel_iommu=on". Can you test
whether that makes a difference with the Debian kernels?
Ben.
> or the negated value, not sure at the moment, what a y or n should mean
> in this config and if the assignments of 0 or 1 are correct everywhere.
--
Ben Hutchings
Humour is the best antidote to reality.
Markus Kolb
Jun 2, 2022, 2:30:03 PM6/2/22
to
Am 02.06.2022 17:27, schrieb Ben Hutchings:
> On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
> On Thu, 2022-06-02 at 15:42 +0200, Markus Kolb wrote:
[...]
>> there is introduced the kernel config option
>> INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
>> but it is not handled anywhere in the code.
>
> It is handled implicitly. When that config symbol is enabled, both
> INTEL_IOMMU_DEFAULT_ON and INTEL_IOMMU_DEFAULT_OFF are disabled.
[...]
>> INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF
>> but it is not handled anywhere in the code.
>
> It is handled implicitly. When that config symbol is enabled, both
> INTEL_IOMMU_DEFAULT_ON and INTEL_IOMMU_DEFAULT_OFF are disabled.
> No, the whole point of INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF is to turn
> that off by default while still enabling the IOMMU for other devices.
Yes, I got this, but not sure if the code logic is really correct.
> that off by default while still enabling the IOMMU for other devices.
With this INTEL_IOMMU_DEFAULT_ON is "implicitly" falsy and the code is
supposed to run like it would be truthy.
> Based on the log from your self-built kernel, it seems like your system
> should work with the kernel parameter "intel_iommu=on". Can you test
> whether that makes a difference with the Debian kernels?
intel_iommu=on
and also not with
intel_iommu=on,intgpu_off (which should be the same like nothing
specified).
Really only possibility intel_iommu=on,igfx_off.
Vicente Olivert Riera
Jun 2, 2022, 11:40:03 PM6/2/22
to
Package: src:linux
Followup-For: Bug #1012210
X-Debbugs-Cc: vincent.ol...@gmail.com
I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021.
The software I'm using is UTM, which uses QEMU under the hood.
Yesterday I did a system upgrade:
aptitude -y update && aptitude -y full-upgrade && apt -y autoremove
I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After that
Debian was unable to boot. Choosing the previous kernel image available
from Grub (5.10.0-13) allowed Debian to boot normally.
Regards,
Vincent
Followup-For: Bug #1012210
X-Debbugs-Cc: vincent.ol...@gmail.com
I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021.
The software I'm using is UTM, which uses QEMU under the hood.
Yesterday I did a system upgrade:
aptitude -y update && aptitude -y full-upgrade && apt -y autoremove
I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After that
Debian was unable to boot. Choosing the previous kernel image available
from Grub (5.10.0-13) allowed Debian to boot normally.
Regards,
Vincent
Diederik de Haas
Jun 3, 2022, 7:10:04 AM6/3/22
to
Control: clone -1 -2
Control: notfound -2 linux/5.17.3-1
Control: retitle -2 linux-image-5.10.0-14-amd64: boot failure in VM after upgrading from -13
Control: tag -2 moreinfo
On Friday, 3 June 2022 05:35:15 CEST Vicente Olivert Riera wrote:
> Package: src:linux
> Followup-For: Bug #1012210
This seems to be completely unrelated to that bug, so I've cloned it into a new
bug. When responding please only respond to that new bug report/number.
> I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021.
> The software I'm using is UTM, which uses QEMU under the hood.
>
> Yesterday I did a system upgrade:
> aptitude -y update && aptitude -y full-upgrade && apt -y autoremove
General tip: don't do that!
With 'update' it seems pointless
With 'full-upgrade' you REALLY should review what is about to happen before
agreeing to that as it could remove packages (important for you)
I'd recommend reviewing the 'autoremove' result too before committing it
> I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After
> that Debian was unable to boot. Choosing the previous kernel image
> available from Grub (5.10.0-13) allowed Debian to boot normally.
Bug 1012210 is about a boot failure on a (wide) variety of kernels, likely
related to igpu.
Your issue is a regression from -13 to -14.
I assumed that you're running Debian Stable *in* a VM (on what host OS?).
Please clarify whether that is correct or not. Also provide more info about
YOUR boot failure and sent that to the NEW bug number that you should receive.
Control: notfound -2 linux/5.17.3-1
Control: retitle -2 linux-image-5.10.0-14-amd64: boot failure in VM after upgrading from -13
Control: tag -2 moreinfo
On Friday, 3 June 2022 05:35:15 CEST Vicente Olivert Riera wrote:
> Package: src:linux
> Followup-For: Bug #1012210
bug. When responding please only respond to that new bug report/number.
> I'm running Debian stable on a VM from an Apple MacBook Pro M1 14" 2021.
> The software I'm using is UTM, which uses QEMU under the hood.
>
> Yesterday I did a system upgrade:
> aptitude -y update && aptitude -y full-upgrade && apt -y autoremove
With 'update' it seems pointless
With 'full-upgrade' you REALLY should review what is about to happen before
agreeing to that as it could remove packages (important for you)
I'd recommend reviewing the 'autoremove' result too before committing it
> I noticed the kernel was upgraded to 5.10.0-14 so I rebooted the VM. After
> that Debian was unable to boot. Choosing the previous kernel image
> available from Grub (5.10.0-13) allowed Debian to boot normally.
related to igpu.
Your issue is a regression from -13 to -14.
I assumed that you're running Debian Stable *in* a VM (on what host OS?).
Please clarify whether that is correct or not. Also provide more info about
YOUR boot failure and sent that to the NEW bug number that you should receive.
Markus Kolb
Jun 3, 2022, 10:10:04 AM6/3/22
to
Am 02.06.2022 23:26, schrieb Markus Kolb:
> Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb <deb...@tower-net.de>:
[...]
>> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
>> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch
> [...]
> I've patched the kernel.org 5.10.113 just with these 2 Debian patches
> and at least I can confirm, that these changes are the cause.
> Although I don't understand at the moment where the difference of
> intel_iommu=on with patch and the defaults without patch could be.
> Will have a closer look tomorrow.
I've found the difference, somehow I've had the opinion that with the
kernel.org and Debian Buster kernel dmar_disabled would be set to false
by default or CONFIG_INTEL_IOMMU_DEFAULT_ON would be enabled by default.
But this is not the case. So dmar_disabled is true there without boot
config.
With the Debian patch in Bullseye and newer this has been enabled
implicitly via CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y and
dmar_disabled became false.
With the older kernels you had to enable it per boot config, and now you
need to disable it.
So added now this to drivers/iommu/intel/iommu.c and my computer boots
without any required kernel boot option with Debian kernels:
--- a/drivers/iommu/intel/iommu.c 2022-06-03 14:50:52.248268257 +0200
+++ b/drivers/iommu/intel/iommu.c 2022-06-03 14:48:12.695769217 +0200
@@ -6186,6 +6186,9 @@
dmar_map_gfx = 0;
}
+/* Q35 integrated gfx dmar support is totally busted. */
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x29b2,
quirk_iommu_igfx);
+
/* G4x/GM45 integrated gfx dmar support is totally busted. */
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2a40,
quirk_iommu_igfx);
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e00,
quirk_iommu_igfx);
The only related to problem, I've found, is this discussion without
result 5 years ago:
https://lore.kernel.org/linux-iommu/20161205215841.GA20819@beast/
And this nearly 4 year old bug report without attention:
https://bugzilla.kernel.org/show_bug.cgi?id=201185
I've opened https://bugzilla.kernel.org/show_bug.cgi?id=216064
Would you add this patch to Debian kernels?
> Am 2. Juni 2022 13:42:54 UTC schrieb Markus Kolb <deb...@tower-net.de>:
[...]
>> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-kconfig-option-to-exclude-igpu-by-default.patch
>> https://salsa.debian.org/kernel-team/linux/-/blob/bullseye-security/debian/patches/features/x86/intel-iommu-add-option-to-exclude-integrated-gpu-only.patch
> [...]
> I've patched the kernel.org 5.10.113 just with these 2 Debian patches
> and at least I can confirm, that these changes are the cause.
> Although I don't understand at the moment where the difference of
> intel_iommu=on with patch and the defaults without patch could be.
> Will have a closer look tomorrow.
I've found the difference, somehow I've had the opinion that with the
kernel.org and Debian Buster kernel dmar_disabled would be set to false
by default or CONFIG_INTEL_IOMMU_DEFAULT_ON would be enabled by default.
But this is not the case. So dmar_disabled is true there without boot
config.
With the Debian patch in Bullseye and newer this has been enabled
implicitly via CONFIG_INTEL_IOMMU_DEFAULT_ON_INTGPU_OFF=y and
dmar_disabled became false.
With the older kernels you had to enable it per boot config, and now you
need to disable it.
So added now this to drivers/iommu/intel/iommu.c and my computer boots
without any required kernel boot option with Debian kernels:
--- a/drivers/iommu/intel/iommu.c 2022-06-03 14:50:52.248268257 +0200
+++ b/drivers/iommu/intel/iommu.c 2022-06-03 14:48:12.695769217 +0200
@@ -6186,6 +6186,9 @@
dmar_map_gfx = 0;
}
+/* Q35 integrated gfx dmar support is totally busted. */
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x29b2,
quirk_iommu_igfx);
+
/* G4x/GM45 integrated gfx dmar support is totally busted. */
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2a40,
quirk_iommu_igfx);
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e00,
quirk_iommu_igfx);
The only related to problem, I've found, is this discussion without
result 5 years ago:
https://lore.kernel.org/linux-iommu/20161205215841.GA20819@beast/
And this nearly 4 year old bug report without attention:
https://bugzilla.kernel.org/show_bug.cgi?id=201185
I've opened https://bugzilla.kernel.org/show_bug.cgi?id=216064
Would you add this patch to Debian kernels?
0 new messages