Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #68539 > unrolled thread
| Started by | Alejandro Colomar <alx.manpages@gmail.com> |
|---|---|
| First post | 2020-11-10 22:10 +0100 |
| Last post | 2020-11-28 17:40 +0100 |
| Articles | 9 — 5 participants |
Back to article view | Back to linux.debian.kernel
Bug#974166: linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode Alejandro Colomar <alx.manpages@gmail.com> - 2020-11-10 22:10 +0100
Bug#974166: linux/5.9.6-1 (unstable) has the same bug "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> - 2020-11-14 12:40 +0100
Bug#974166: Boot logs "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> - 2020-11-14 13:00 +0100
Bug#974166: I'd like to help "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> - 2020-11-22 17:30 +0100
Bug#974166: I'd like to help Georgi Naplatanov <gosho@oles.biz> - 2020-11-22 18:10 +0100
Bug#974166: I'd like to help "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> - 2020-11-22 18:10 +0100
Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> - 2020-11-28 17:10 +0100
Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue Salvatore Bonaccorso <carnil@debian.org> - 2020-11-28 17:40 +0100
Bug#974166: marked as done (linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-11-28 17:40 +0100
| From | Alejandro Colomar <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-10 22:10 +0100 |
| Subject | Bug#974166: linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode |
| Message-ID | <B9J3P-2W1-1@gated-at.bofh.it> |
Package: src:linux
Version: 5.9.1-1
Severity: important
X-Debbugs-Cc: alx.manpages@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
When I upgreeaded from kernel 5.6 to 5.7 a long time ago, my system broke.
I first saw some firmware errors when booting.
But when I fixed those firmware errors by adding non-free and contrib repos,
and installing firmware-linux,
those errors disapeared.
Now it simply goes black at some point during the boot.
If I boot with linux 5.6, however, everything runs fine.
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
Ineffective: Upgrading the kernel to 5.8, or 5.9.
None of the kernels >= 5.7 work.
Worked: Run with kernel 5.6 (or older).
Ineffective: Clean install from DI-alpha2.
This provides two kernels: 5.4 (works) and 5.9 (doesn't work).
I also tried installing firmware directly from kernel.org:
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
sudo make install
but it didn't fix it.
*** End of the template - remove these template lines ***
-- Package-specific info:
** Kernel log: boot messages should be attached
I don't know how to get the boot messages from a system that doesn't boot.
** Model information
sys_vendor: ASUS
product_name: All Series
product_version: System Version
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: 2902
board_vendor: ASUSTeK COMPUTER INC.
board_name: Z97M-PLUS
board_version: Rev X.0x
** Network interface configuration:
*** /etc/network/interfaces:
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge - DMI [8086:1610] (rev 0a)
Subsystem: ASUSTeK Computer Inc. Broadwell-U Host Bridge - DMI [1043:8534]
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:01.0 PCI bridge [0604]: Intel Corporation Broadwell-U PCI Express x16 Controller [8086:1601] (rev 0a) (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 A routed to IRQ 24
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000efff [size=4K]
Memory behind bridge: f7100000-f71fffff [size=1M]
Prefetchable memory behind bridge: [disabled]
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:02.0 VGA compatible controller [0300]: Intel Corporation Iris Pro Graphics 6200 [8086:1622] (rev 0a) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: ASUSTeK Computer Inc. Iris Pro Graphics 6200 [1043:8534]
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 36
Region 0: Memory at f6000000 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at f000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 0a)
Subsystem: ASUSTeK Computer Inc. Broadwell-U Audio Controller [1043:8534]
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 39
Region 0: Memory at f7234000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB xHCI Controller [1043:8534]
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 29
Region 0: Memory at f7220000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba]
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family ME Interface [1043:8534]
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 35
Region 0: Memory at f723d000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-V [8086:15a1]
DeviceName: Onboard LAN
Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I218-V [1043:85c4]
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 28
Region 0: Memory at f7200000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f723b000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at f060 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad] (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB EHCI Controller [1043:8534]
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 16
Region 0: Memory at f723a000 (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 9 Series Chipset Family HD Audio Controller [8086:8ca0]
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family HD Audio Controller [1043:8630]
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 38
Region 0: Memory at f7230000 (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 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) (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 A routed to IRQ 25
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
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.3 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d0) (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, Cache Line Size: 64 bytes
Interrupt: pin D routed to IRQ 26
Bus: primary=00, secondary=03, subordinate=04, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
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.4 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 [8086:8c98] (rev d0) (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 A routed to IRQ 27
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
I/O behind bridge: [disabled]
Memory behind bridge: f7000000-f70fffff [size=1M]
Prefetchable memory behind bridge: [disabled]
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 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6] (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family USB EHCI Controller [1043:8534]
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 23
Region 0: Memory at f7239000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1f.0 ISA bridge [0601]: Intel Corporation Z97 Chipset LPC Controller [8086:8cc4]
Subsystem: ASUSTeK Computer Inc. Z97 Chipset LPC Controller [1043:8534]
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.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2]
Subsystem: ASUSTeK Computer Inc. 9 Series Chipset Family SMBus Controller [1043:8534]
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-
Interrupt: pin C routed to IRQ 18
Region 0: Memory at f7238000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at f040 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a802] (rev 01) (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a801]
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 16
NUMA node: 0
Region 0: Memory at f7110000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at e000 [size=256]
Expansion ROM at f7100000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: nvme
Kernel modules: nvme
03:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04) (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, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 255
Bus: primary=03, secondary=04, subordinate=04, sec-latency=32
I/O behind bridge: [disabled]
Memory behind bridge: [disabled]
Prefetchable memory behind bridge: [disabled]
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>
05:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev bb)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070]
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 37
Region 0: Memory at f7000000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
** USB devices:
Bus 004 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04b4:4009 Cypress Semiconductor Corp.
Bus 001 Device 003: ID 04d9:a09f Holtek Semiconductor, Inc. E-Signal LUOM G10 Mechanical Gaming Mouse
Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless interface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-5.9.0-1-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.139
ii kmod 27+20200310-2
ii linux-base 4.6
Versions of packages linux-image-5.9.0-1-amd64 recommends:
ii apparmor 2.13.5-1
ii firmware-linux-free 20200122-1
Versions of packages linux-image-5.9.0-1-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-efi-amd64 2.04-8
pn linux-doc-5.9 <none>
Versions of packages linux-image-5.9.0-1-amd64 is related to:
ii firmware-amd-graphics 20200918-1
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 20200918-1
ii firmware-misc-nonfree 20200918-1
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
[toc] | [next] | [standalone]
| From | "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-14 12:40 +0100 |
| Subject | Bug#974166: linux/5.9.6-1 (unstable) has the same bug |
| Message-ID | <Bb24q-14h-3@gated-at.bofh.it> |
| In reply to | #68539 |
I tried installing the new kernel from unstable, but I still can't boot with it. Same problems.
[toc] | [prev] | [next] | [standalone]
| From | "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-14 13:00 +0100 |
| Subject | Bug#974166: Boot logs |
| Message-ID | <Bb2nL-1b3-3@gated-at.bofh.it> |
| In reply to | #68539 |
I tried booting in recovery mode,
and it also didn't work.
However, I could see the some info.
The 3 last lines of the boot log were:
{
[ 4.817936] hub 4-0:1.0: 2 ports detected
[ 4.819372] i915 0000:00:02.0: [drm] Found 128MB of eDRAM
[ 4.819882] fb0: switching to inteldrmfb from EFI VGA
}
And then freeze.
These messages are not logged into /var/log/kern.log,
as the system doesn't even boot.
I had to copy them by hand.
Here's what I see when booting with kernel 5.4
at (more or less) the same part of the boot process:
{
[ 4.140383] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 4.172077] i915 0000:00:02.0: Found 128MB of eDRAM
[ 4.172105] checking generic (e0000000 300000) vs hw (e0000000 10000000)
[ 4.172106] fb0: switching to inteldrmfb from EFI VGA
[ 4.172311] Console: switching to colour dummy device 80x25
[ 4.172347] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 4.179379] iwlwifi 0000:05:00.0: Detected Intel(R) Dual Band
Wireless AC 7260, REV=0x144
[ 4.180399] snd_hda_codec_realtek hdaudioC1D0: autoconfig for
ALC887-VD: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[ 4.180400] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 4.180401] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1
(0x1b/0x0/0x0/0x0/0x0)
[ 4.180402] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
[ 4.180402] snd_hda_codec_realtek hdaudioC1D0: dig-out=0x11/0x0
[ 4.180403] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 4.180404] snd_hda_codec_realtek hdaudioC1D0: Front Mic=0x19
[ 4.180405] snd_hda_codec_realtek hdaudioC1D0: Rear Mic=0x18
[ 4.180405] snd_hda_codec_realtek hdaudioC1D0: Line=0x1a
[ 4.180736] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.180737] [drm] Driver supports precise vblank timestamp query.
[ 4.180977] i915 0000:00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 4.188068] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on
minor 0
[ 4.189872] ACPI: Video Device [GFX0] (multi-head: yes rom: no
post: no)
[ 4.189993] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4
[ 4.190545] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops
i915_audio_component_bind_ops [i915])
[ 4.196712] iwlwifi 0000:05:00.0: base HW address: 7c:5c:f8:a4:bb:27
[ 4.204867] input: HDA Intel PCH Front Mic as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input5
[ 4.204901] input: HDA Intel PCH Rear Mic as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input6
[ 4.204933] input: HDA Intel PCH Line as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input7
[ 4.204962] input: HDA Intel PCH Line Out Front as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input8
[ 4.204996] input: HDA Intel PCH Line Out Surround as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input9
[ 4.205028] input: HDA Intel PCH Line Out CLFE as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input10
[ 4.205059] input: HDA Intel PCH Line Out Side as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input11
[ 4.205088] input: HDA Intel PCH Front Headphone as
/devices/pci0000:00/0000:00:1b.0/sound/card1/input12
[ 4.230276] fbcon: i915drmfb (fb0) is primary device
[ 4.232087] input: HDA Intel HDMI HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:03.0/sound/card0/input13
[ 4.232120] input: HDA Intel HDMI HDMI/DP,pcm=7 as
/devices/pci0000:00/0000:00:03.0/sound/card0/input14
[ 4.232149] input: HDA Intel HDMI HDMI/DP,pcm=8 as
/devices/pci0000:00/0000:00:03.0/sound/card0/input15
[ 4.261519] usb 2-14: New USB device found, idVendor=04b4,
idProduct=4009, bcdDevice= 1.00
[ 4.261520] usb 2-14: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 4.271503] Console: switching to colour frame buffer device 240x67
[ 4.291128] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
}
[toc] | [prev] | [next] | [standalone]
| From | "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-22 17:30 +0100 |
| Subject | Bug#974166: I'd like to help |
| Message-ID | <Be0ps-2XV-13@gated-at.bofh.it> |
| In reply to | #68539 |
Hi, I received no answer at all, so I guess you are very busy. I know the bug was introduced somewhere between 5.6 and 5.7. If you have an idea of what the source of the bug could be, I'd like to help by testing on my computers, or providing code. I have two computers with similar CPUs (i5-5675C & i7-5775C), and both have the same problem. Basically I'm limited to kernel <= 5.6, right now. I can't boot from a more recent kernel. Thanks, Alex
[toc] | [prev] | [next] | [standalone]
| From | Georgi Naplatanov <gosho@oles.biz> |
|---|---|
| Date | 2020-11-22 18:10 +0100 |
| Subject | Bug#974166: I'd like to help |
| Message-ID | <Be129-3qz-1@gated-at.bofh.it> |
| In reply to | #68634 |
Hi, I have Intel i5 4th generation and I have no such problem with Linux kernel 5.9.6. Do you have "intel-microcode" package installed on those computers? Kind regards Georgi
[toc] | [prev] | [next] | [standalone]
| From | "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-22 18:10 +0100 |
| Subject | Bug#974166: I'd like to help |
| Message-ID | <Be129-3qz-3@gated-at.bofh.it> |
| In reply to | #68539 |
Hi, I suspect it may have to do with the 5th gen (Broadwell Desktop) only, as they have a very special (and powerful) iGPU. And maybe that's why the bug passed inadvertently so much time: those CPUs didn't sell very well. Yes, I have that package installed: ||/ Name Version Architecture Description +++-===============-============-============-=========================================== ii intel-microcode 3.20201110.1 amd64 Processor microcode firmware for Intel CPUs When I first upgraded to 5.7, I couldn't boot, and my first thought was: this seems to be such a big bug, so they probably have already noticed, and I didn't report it. It's been more than half a year, kernel 5.9, and the bug is still there, so I strongly suspect that the only affected CPUs are those with Intel Iris Pro 6200 (there are only 4 models with that iGPU). Thanks, Alex On 11/22/20 5:53 PM, Georgi Naplatanov wrote: > Hi, > > I have Intel i5 4th generation and I have no such problem with Linux > kernel 5.9.6. > > Do you have "intel-microcode" package installed on those computers? > > Kind regards > Georgi >
[toc] | [prev] | [next] | [standalone]
| From | "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com> |
|---|---|
| Date | 2020-11-28 17:10 +0100 |
| Subject | Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue |
| Message-ID | <BgaXn-iJ-1@gated-at.bofh.it> |
| In reply to | #68539 |
Hi, I'm glad to say that just now I upgraded to the unstable kernel: $ sudo apt-get install linux-image-amd64 and now I can boot normally: $ uname -a Linux debian 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux I'm curious: I'd like to see the changelog and the code to see what fixed the issue. Could you point me to it, or give me some hint so that I can search for it myself? Thanks, Alex
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2020-11-28 17:40 +0100 |
| Subject | Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue |
| Message-ID | <Bgbqp-sY-3@gated-at.bofh.it> |
| In reply to | #68721 |
Source: linux Source-Version: 5.9.11-1 On Sat, Nov 28, 2020 at 05:05:38PM +0100, Alejandro Colomar (man-pages) wrote: > Hi, > > I'm glad to say that just now I upgraded to the unstable kernel: > > $ sudo apt-get install linux-image-amd64 > > and now I can boot normally: > > $ uname -a > Linux debian 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 > GNU/Linux Thanks for confirming, then we can close the bug with that version. > I'm curious: I'd like to see the changelog and the code > to see what fixed the issue. > Could you point me to it, > or give me some hint so that I can search for it myself? You can find the Debian changelog in /usr/share/doc/linux-image-5.9.0-4-amd64/changelog.gz . Mostly apart what you will see on Debian changes it will list mostly (a filtered changelog as well from the repsective upstrema changes from the stable version imports). Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2020-11-28 17:40 +0100 |
| Subject | Bug#974166: marked as done (linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode) |
| Message-ID | <Bgbqp-sY-1@gated-at.bofh.it> |
| In reply to | #68539 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sat, 28 Nov 2020 17:34:23 +0100 with message-id <X8J8DxTcyaC2upRI@eldamar.lan> and subject line Re: Bug#974166: 5.9.0-1-amd64 (5.9.11-1) has fixed the issue has caused the Debian Bug report #974166, regarding linux-image-5.9.0-1-amd64: The system goes black when trying to boot graphical mode 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.) -- 974166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974166 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web