Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1059928 > unrolled thread

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-23 12:10 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Salvatore Bonaccorso <carnil@debian.org> - 2021-05-23 13:40 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-25 10:30 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-29 17:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-29 21:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-30 07:30 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-30 09:40 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-05-30 18:10 +0200
    Bug#989010: Severity raise jim_p <pitsiorisj@gmail.com> - 2021-05-31 17:40 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Salvatore Bonaccorso <carnil@debian.org> - 2021-05-31 21:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-01 06:40 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-02 10:20 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-04 09:20 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Laurențiu Păncescu <lpancescu@gmail.com> - 2021-06-04 12:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-05 19:40 +0200
      Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Ben Hutchings <ben@decadent.org.uk> - 2021-06-05 21:10 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-06 07:10 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-13 10:30 +0200
      Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Bernhard Übelacker <bernhardu@mailbox.org> - 2021-06-13 17:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-14 07:10 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-06-26 09:50 +0200
      Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 Steve McIntyre <93sam@debian.org> - 2021-07-03 03:50 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-07-05 13:00 +0200
    Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38 jim_p <pitsiorisj@gmail.com> - 2021-07-19 11:40 +0200

Page 1 of 2  [1] 2  Next page →

#1059928 — Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

Package: src:linux
Version: 5.10.38-1
Severity: important
X-Debbugs-Cc: pitsiorisj@gmail.com

Preface.
I have disabled sleep, hibernate etc via systemd as you can see below.

$ systemctl status sleep.target suspend.target hibernate.target hybrid-
sleep.target
● sleep.target
     Loaded: masked (Reason: Unit sleep.target is masked.)
     Active: inactive (dead)

● suspend.target
     Loaded: masked (Reason: Unit suspend.target is masked.)
     Active: inactive (dead)

● hibernate.target
     Loaded: masked (Reason: Unit hibernate.target is masked.)
     Active: inactive (dead)

● hybrid-sleep.target
     Loaded: masked (Reason: Unit hybrid-sleep.target is masked.)
     Active: inactive (dead)

and I have set my keyboard's sleep button to shutdown the system via systemctl

    <keybind key="XF86Sleep">
      <action name="Execute">
        <command>systemctl poweroff</command>
      </action>
    </keybind>

So when I press the sleep button, the system shuts down. And I have been using
it like so for the last 5+ years.

But today, after I upgraded to 5.10.38 and rebooted, I pressed sleep and the
system... must have gone to sleep. Pressing the powerbutton did not get me to
post or grub or anything. It was just working with nothing on screen. I could
ssh to it from my phone or my laptop, so I ran reboot and it hypothetically
rebooted. I say "hypothetically", because there was no post, grub, boot
messages or desktop again. I rebooted it with reisub, but same thing happened.
Both network (leds on nic) and usb (light on optical mouse) showed that it was
really powered on, on all the forementioned situations.

Since I can ssh to it, I ran dmesg and it showed nothing weird. Systemd-analyze
blade showed no delays or issues too. I installed 5.10.28 again (because I
remove every old kernel when the new one works) and now I am able to see my
desktop and write all this.

Right now, I am on 5.10.28 (package linux-image-5.10.0-6-amd64) and I am trying
to figure out why all this happened.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: P35-DS3R
product_version: 
chassis_vendor: Gigabyte Technology Co., Ltd.
chassis_version: 
bios_vendor: Award Software International, Inc.
bios_version: F13
board_vendor: Gigabyte Technology Co., Ltd.
board_name: P35-DS3R
board_version: 

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02)
	Subsystem: Gigabyte Technology Co., Ltd 82G33/G31/P35/P31 Express DRAM Controller [1458:5000]
	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 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (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: 32 bytes
	Interrupt: pin A routed to IRQ 24
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff [size=4K]
	Memory behind bridge: f4000000-f6ffffff [size=48M]
	Prefetchable memory behind bridge: 00000000d0000000-00000000efffffff [size=512M]
	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:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) (prog-if 00 [UHCI])
	Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 4: I/O ports at e100 [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 e200 [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 18
	Region 4: I/O ports at e000 [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB2 EHCI Controller [1458:5006]
	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 18
	Region 0: Memory at f9104000 (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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) HD Audio Controller [1458:a002]
	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: 32 bytes
	Interrupt: pin A routed to IRQ 29
	Region 0: Memory at f9100000 (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: 32 bytes
	Interrupt: pin A routed to IRQ 25
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000a000-0000afff [size=4K]
	Memory behind bridge: f9200000-f93fffff [size=2M]
	Prefetchable memory behind bridge: 00000000f9400000-00000000f95fffff [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.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (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: 32 bytes
	Interrupt: pin D routed to IRQ 26
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff [size=4K]
	Memory behind bridge: f9000000-f90fffff [size=1M]
	Prefetchable memory behind bridge: 00000000f9600000-00000000f97fffff [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.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (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: 32 bytes
	Interrupt: pin A routed to IRQ 27
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff [size=4K]
	Memory behind bridge: f7000000-f8ffffff [size=32M]
	Prefetchable memory behind bridge: 00000000f9800000-00000000f99fffff [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 4: I/O ports at e300 [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 19
	Region 4: I/O ports at e400 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) (prog-if 00 [UHCI])
	Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB UHCI Controller [1458:5004]
	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 18
	Region 4: I/O ports at e500 [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: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB2 EHCI Controller [1458:5006]
	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 f9105000 (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=05, subordinate=05, sec-latency=32
	I/O behind bridge: 00009000-00009fff [size=4K]
	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 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02)
	Subsystem: Gigabyte Technology Co., Ltd 82801IR (ICH9R) LPC Interface Controller [1458:5001]
	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: Gigabyte Technology Co., Ltd 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [1458:b005]
	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 28
	Region 0: I/O ports at e600 [size=8]
	Region 1: I/O ports at e700 [size=4]
	Region 2: I/O ports at e800 [size=8]
	Region 3: I/O ports at e900 [size=4]
	Region 4: I/O ports at ea00 [size=32]
	Region 5: Memory at f9106000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
	Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) SMBus Controller [1458:5001]
	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 f9107000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at 0500 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
	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 30
	Region 0: Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at e0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at b000 [size=128]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: nvidia
	Kernel modules: nvidia

01:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1)
	Subsystem: ASUSTeK Computer Inc. High Definition Audio Controller [1043:8490]
	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: 32 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

03:00.0 SATA controller [0106]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 02) (prog-if 01 [AHCI 1.0])
	Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:b000]
	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: 32 bytes
	Interrupt: pin A routed to IRQ 19
	Region 5: Memory at f9000000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

03:00.1 IDE interface [0101]: JMicron Technology Corp. JMB363 SATA/IDE Controller [197b:2363] (rev 02) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
	Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:b000]
	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 16
	Region 0: I/O ports at c000 [size=8]
	Region 1: I/O ports at c100 [size=4]
	Region 2: I/O ports at c200 [size=8]
	Region 3: I/O ports at c300 [size=4]
	Region 4: I/O ports at c400 [size=16]
	Capabilities: <access denied>
	Kernel driver in use: pata_jmicron
	Kernel modules: pata_jmicron, ata_generic

04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
	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: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at d000 [size=256]
	Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=4K]
	Expansion ROM at f7000000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169


** USB devices:
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 09da:f012 A4Tech Co., Ltd. USB Device
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-5.10.0-7-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-7-amd64 recommends:
pn  apparmor             <none>
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-7-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20190206.bf6db5b4+dfsg1-3
ii  grub-pc                 2.04-17
pn  linux-doc-5.10          <none>

Versions of packages linux-image-5.10.0-7-amd64 is related to:
ii  firmware-amd-graphics     20210315-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    20210315-2
ii  firmware-misc-nonfree     20210315-2
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
ii  firmware-realtek          20210315-2
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#1059936

Control: tags -1 + moreinfo

Hi

On Sun, May 23, 2021 at 01:04:13PM +0300, jim_p wrote:
> Package: src:linux
> Version: 5.10.38-1
> Severity: important
> X-Debbugs-Cc: pitsiorisj@gmail.com
> 
> Preface.
> I have disabled sleep, hibernate etc via systemd as you can see below.
> 
> $ systemctl status sleep.target suspend.target hibernate.target hybrid-
> sleep.target
> ● sleep.target
>      Loaded: masked (Reason: Unit sleep.target is masked.)
>      Active: inactive (dead)
> 
> ● suspend.target
>      Loaded: masked (Reason: Unit suspend.target is masked.)
>      Active: inactive (dead)
> 
> ● hibernate.target
>      Loaded: masked (Reason: Unit hibernate.target is masked.)
>      Active: inactive (dead)
> 
> ● hybrid-sleep.target
>      Loaded: masked (Reason: Unit hybrid-sleep.target is masked.)
>      Active: inactive (dead)
> 
> and I have set my keyboard's sleep button to shutdown the system via systemctl
> 
>     <keybind key="XF86Sleep">
>       <action name="Execute">
>         <command>systemctl poweroff</command>
>       </action>
>     </keybind>
> 
> So when I press the sleep button, the system shuts down. And I have been using
> it like so for the last 5+ years.
> 
> But today, after I upgraded to 5.10.38 and rebooted, I pressed sleep and the
> system... must have gone to sleep. Pressing the powerbutton did not get me to
> post or grub or anything. It was just working with nothing on screen. I could
> ssh to it from my phone or my laptop, so I ran reboot and it hypothetically
> rebooted. I say "hypothetically", because there was no post, grub, boot
> messages or desktop again. I rebooted it with reisub, but same thing happened.
> Both network (leds on nic) and usb (light on optical mouse) showed that it was
> really powered on, on all the forementioned situations.
> 
> Since I can ssh to it, I ran dmesg and it showed nothing weird. Systemd-analyze
> blade showed no delays or issues too. I installed 5.10.28 again (because I
> remove every old kernel when the new one works) and now I am able to see my
> desktop and write all this.
> 
> Right now, I am on 5.10.28 (package linux-image-5.10.0-6-amd64) and I am trying
> to figure out why all this happened.

It looks from the attached information that you have a tainted kernel,
with proprietary modules loaded (nvidia at least?). Could you please
try without those loading?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#1060138

Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

Can I somehow determine that the button does run systemctl poweroff and not
sleep when I press it? All I can see in the shutdown messages, for that split
second they appear, is just the word "systemd" and nothing more. I want to
count out the possibility of failing hw.

[toc] | [prev] | [next] | [standalone]

#1060551

Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

Impending rant, because I think it is indeed a hardware failure that was caused
from the kernel upgrade.

I successfully downgraded linux-compiler-gcc-10-x86 and linux-kbuild-5.10 to
their 5.10.28 versions from testing.
As usual, it failed to boot properly after shutdown. I then decided to
completely remove nvidia legacy 340 and give nouveau a chance, although I hate
it and the room temperature was high already, so the risk of frying the card
was also high. Nothing changed, blank screen from boot to poweroff (via ssh).

Out of curiosity, I ran lsmod on both nouveau and nvidia (while it was already
installed). And none of them showed up in lsmod! Moreover, lightdm was not
running at all and I cound not even switch to a tty (not that I could when the
problem first started).
Then I got mad and went for a walk to calm down. I came back a few hours later
and I also borrowed an ati 6450 from a friend to try.

I pressed the power button and the system booted up as usual, using nouveau for
the very first time (maybe second) ever. I ran poweroff, it shut down, I
pressed the power button again and the same thing happened. Blank screen,
nothing on lsmod etc.
Then I replaced it with my friend's ati so as to be able to come back and write
all this text here.

I have no way to test the gpu (e.g. no spare pc), however, if it is a hw
failure, it will be the second time debian destroys one for me. First time was
on summer of 2011, when debian decided to remove fglrx from the repo and force
me to use radeon for my 3850 after the upgrade to a new kernel. Back then,
radeon was so limited in capabilities that it could not do powersaving. Long
story short, my 3850 gave up the ghost ~1 month later, after running in  max
clock speed for a month.

Sadly for me, history has probably repeated itself today, and I don't know why.
What was changed in that damn update that f-ed up my gpu so badly?
This gives me one more reason to leave debian after 13,5 years and move to
arch. I had taken the decision to go there if nouveau becomes my only way to
make my old gpu work in debian, now I have one more.

[toc] | [prev] | [next] | [standalone]

#1060573

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

I never thought I would say that, but radeon's capabilities are inferior even
to nvidia's legacy driver.
It has been a few hours now and I am still struggling to get vaapi working on
mpv and mplayer. 2d acceleration is bad, so bad that I can see the scrollbar on
ALL webpages "struggle" to keep up with the rest of the page when I scroll with
the wheel.

And on top of the above, 5.10.40 messed up the cpu temperature sensor readings
I get on my conky, so now I have nothing to look at. What a mess!

[toc] | [prev] | [next] | [standalone]

#1060597

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

And the same thing happened again today, with the ati card this time! I logged
in via ssh and, like with nvidia and nouveaum radeon was not found in lsmod. I
then checked lspci and the entire vga part was not there, as if a gpu was not
even connected!
What the fuck was on this update that fucked my only pcie-x slot that bad?
Since I get no replies and so far I have been troubleshooting it on my own, I
decided to move to arch by the end of the week, provided that one of the cards
still works.
Thanks for nothing, I will surely leave a bad review on distrowatch for the
rest of the people to see.

p.s. I had to borrow an fresh (yet old) nvidia card in order to make my system
boot again and right now I am using it with nouveau, which is godawful btw.

[toc] | [prev] | [next] | [standalone]

#1060600

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

One thing I forgot last time. The ati card was fucked up AFTER it ran on
5.10.40 for a couple of boots. I installed it because I wanted to check if it
works any better there (scrolling is laggy on all browsers).
Do you think it is a coincidence? 2 cards messed up after both running for a
while on the same kernel?
How can I raise the severity to critical? It seems to cause hw failure.

[toc] | [prev] | [next] | [standalone]

#1060630

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

I borrowed an old pc from a friend to test those 2 gpus. NONE of them reached
the post, which means they are damaged now. Moreover, when the ati was
connected, the system was beeping as if it had no vga on.
Thank you debian for destroying 2 perfectly working pieces of hardware. If I
could sue anyone who is responsible for this crap, I would.
How about someone tells me what was changed in that -7 version that made all
this mess. I compared the config files from testing's 5.10.28 and unstable's
5.10.38/5.10.40 and the changes were minimal.

As for nouveau, now that I have tested it for ~24 hours, I can definitely say
it is way below average. 3d acceleration is poor, 2d acceleration is so and so
and hardware video decoding (vaapi) seems to only exist on paper because I did
not manage to make it work on all 3 of my players (mpv, mplayer and kodi). With
all that going on, I did not have the time and the clear mind to check for the
temperatures so as to find out how bad its powersaving abilities are.

[toc] | [prev] | [next] | [standalone]

#1060741 — Bug#989010: Severity raise

Control: severity -1 critical

[toc] | [prev] | [next] | [standalone]

#1060756

Control: severity -1 important

Hi

Could you please extract as well the kernel logs form the kernels
where you firstly see those issues and attach them to this bugreport?
Since you say you can boot 5.10.28 but not 5.10.38, please do this in
two steps.

While I can understand you might be upset if something breaks, still I
would encourage you to reconsider the tone used.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#1060772

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

How would YOU feel if a system upgrade destroyed an (old yet) perfectly working
piece of important hardware? What if it destroyed another piece of similar
hardware a few days later?
How would you feel if all those days you had no support or feedback from anyone
that created that upgrade?
How would you feel if the only advice you were given changed absolutely nothing
and did not even prevent the loss of the second piece of hardware?
Btw, the word "tainted" has to be the worst characterization for a kernel that
must use a specific out-of-tree driver in order to make the related hw work at
100% of its capabilities.

From my point of view, all I see is a kernel that destroyed my hardware TWICE,
thus the raise of severity to critical, because it did break the entire system
hardware wise. The sad thing is that your attention was drawn after I raised
it.
And all the above can result to one thing from my side: anger. And don't expect
me to lower my tone while being angry.

As for the logs, please tell me where to find them and I will zip them and send
them straight to your email if you wish. And not only the ones from 5.10.38/40,
ALL 50/100/any number of logs systemd has kept.
On the other hand, how hard would it be to build a kernel with the latest
update but with the config used for 5.10.28? I did check the differences
between config-5.10.0-6-amd64 and config-5.10.0-7-amd64 last week, but I admit
I am not smart enough to see which change could cause all this mess.

[toc] | [prev] | [next] | [standalone]

#1060904

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

I came accross these 2 threads on r/debian and I am now thinking that my
problem too may not be related to debian packaging/patching/configuration but
to some upstream flaw(s) of 5.10.
The guy in the second thread has done some very extensive testing that prove
it.

https://old.reddit.com/r/debian/comments/npvzyt/intel_nuc_8_freezing_when_idle_on_most_kernels/
https://old.reddit.com/r/debian/comments/mrxx76/irritating_problem_with_the_bullseyes_kernel/

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash

[toc] | [prev] | [next] | [standalone]

#1061045

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com
Control: severity -1 critical

Now that I have your attention, because raising the severity is the only way to
get an answer here, let me begin.

I noticed that this mess of a kernel reached testing today. As it seems, its
original severity status was not enough to prevent this from happening. A
kernel that causes hardware failure will soon be in debian's stable release,
who would have thought!

So, right now I am forced to use an older kernel, thus miss all the security
updates from .28 on. And all that because I want my pc to work as it is
supposed to work. Because I want to press the power button in the morning and
see my pc boot the way it has been booting all those years that it had no
issues at all.
I would do more testing with liquirix's or xanmod's kernels of the same version
in order to prove that your kernel is problematic, but I have ran out of gpus.

Thank you for your non existant support. It was also non existant in a another
kernel related bug report for 4.19 (bug 919859), which I opened in late 2019.
It was closed a few days for lack of activity and it was a monologue with only
me reporting stuff and getting no feedback.
To be honest, if I knew they would become a monologue, I would not file bug
reports but I would open a blog instead. And who knows, maybe someone would
share his feedback there.

p.s. The only reason I am not in arch today, as I promised last week, is
because its installer has some minor issues. In the long term, my decision is
to remove debian from any of my machines, including an rpi4 with raspbian.

[toc] | [prev] | [next] | [standalone]

#1061057

Hi Jim,

Just another Debian user here (Geforce 9400M, on Buster). I found 
similar reports of not resuming from sleep and system freezes in 
Manjaro, Arch, Ubuntu and Fedora discussions, with kernels 5.10 and 5.12 
- nothing about damages cards, though. If you still have the Asus GT218 
and original PC (not the borrowed one), could you remove the power cable 
from the wall for a few minutes and try to boot from a live image, 
either a Debian Buster Live image or one of the Fedora Respins, with the 
latest upstream kernel? 5.10 is rumored to have some issues, not just 
with NVIDIA hardware - perhaps Buster's 4.19 kernel or Fedora's latest 
kernel work better. Both Buster and Fedora work fine on my Geforce 9400M.

Regarding video acceleration: it only work on nouveau, not Nvidia 
proprietary drivers, but you also have to install firmware-misc-nonfree 
for nouveau video acceleration to work. My CPU is too slow to play 
1080p60 video, it loses about half the frames, but with mpv --hwdec=auto 
it's very smooth and causes just 30% CPU usage.

In any case, it's highly unlikely a Debian issue - I had very frequent 
freezes with Fedora since kernel 5.9.0, when a very large patch 
improving power management for Nvidia cards, also removing some 
workarounds - they were fixed in 5.11, I think, and then backported to 
5.10. My next PC will definitely have either Intel or AMD graphics, both 
with open-source drivers written by the manufacturers.

[toc] | [prev] | [next] | [standalone]

#1061183

[Multipart message — attachments visible in raw view] — view raw

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

To no surprise, the severity was lowered again. Without a single suggestion or
reason, again.
Imho, that is the usual incompetence most devs here show, so I am not
surprised. It's a real shame however for a distro this size.

The attached file contains all the changes you devs have made in the kernel
configs from 5.10.28 (-6 package) to 5.10.38/.40 (-7 package). It was made with
meld.
~10 kernel parameters have changed and led to this mess, so I assume it would
be trivial for you to find the faulty one. I bet on the ones related to intel,
because my system's cpu and chipset are both made by intel.

p.s.1 I apologize to those few devs that actually helped with the issues I have
reported all those years. You really stand out of this mess and you will always
have my respect.

p.s.2 Above, I meant to write "it (= my psu) is NEWER than 5.10 is on debian".

[toc] | [prev] | [next] | [standalone]

#1061193

[Multipart message — attachments visible in raw view] — view raw

I've seen nothing to indicate that this is a kernel issue, rather than
hardware becoming flaky or possibly an nvidia driver issue.

It's easy to think that a hardware fault was caused by whatever else
recently changed.  But if there was a software change that broke Nvidia
cards, we would expect to receive lots of bug reports about it, not
just one.

We're still waiting for the requested logs from you.

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it
in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'

[toc] | [prev] | [next] | [standalone]

#1061215

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

About the logs. Did anyone of you reply to my question "where can I find those
logs?" and I missed it? All I have found, again BY MYSELF, is this file here
that when I run cat on it, gibberish shows up in the terminal. I can zip it and
send it to you if you want to examine it.

# du -h /var/log/journal/somenumbersandletters/system.journal
25M     /var/log/journal/somenumbersandletters/system.journal

I have no idea what it may contain, because if it stores the logs from last 50
boots, it has been 2 weeks now and I boot my pc ~3 times a day, so most of
those logs are probably gone.

As for the hardware, it has been almost a week now that it works flawlessly
with another nvidia gpu and 5.10.28 + nvidia 340xx.
Can you imagine how boring it is to press the power button and see your pc boot
just fine instead of checking the monitor to see if post/grub/boot
messages/desktop showed up?

How come this piece of hw did not become flaky, and the ones before it became
just after one day of running with the new kernel?
And what about nouveau and radeon? Running the "untainted" kernel on those (now
broken) gpus did not do a single thing. Neither the nvidia continued to work,
nor ati was saved from dying after the upgrade.

About the "lots of bug reports about nvidia". Out of the 900+ (according to
popcon) people (or systems) that run nvidia 340xx, how many of them do you
think run testing/unstable?
Judging from the feedback I get on my bug reports on every new kernel on which
nvidia 340xx fails to build, I would say me plus 2 or 3 more. And those 2-3
people probably have different hardware than me, e.g. amd cpu and amd chipset,
so the issue may not occur on their setups.

As for the why use nvidia's driver? Because in order to prefer nvidia over
nouvau you need to have demands and standards. If a simple user sees nouveau
draw its 2d desktop fine, he will say it is enough for him.
But, unlike that simple user, I, "unfortunately", want my driver to do hardware
decoding on videos (we have 2021 and not 2010, so this should have been a
standard now for all drivers), 3d and powersaving (also something that should
be a standard). Do you now see the difference between something that "works"
and something that works 110%?
That's why I insist on nvidia's driver.

[toc] | [prev] | [next] | [standalone]

#1061844

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

One more week passed with no issues. That's how things are when a kernel works
as it should and the gpu driver is flawless. Stability that matches the one of
a really stable distro or the one of windows 7.

As I expected, there were no replies on my issue, even now that you have full
logs of what was going on. Maybe it was because I did not raise the severity to
critical, so as to "force" you look at it.
Or, one simple word, incompetence. You just want to blame others'
configurations for your faulty builds and hide your irresponsibilities behind
words like "tainted", admit it.

As for the cards, now that they were tested by a different person, the ati is
totally dead and the nvidia one fails to build on 8 out of 10 times. So it is
not my hardware that makes them "seem dead". They ARE dead, thanks to that
garbage kernel update you made.

I read today that debian 11 will be released by the end of July, so I hope
there will be at least one more kernel upgrade until then. I will check if any
of the kernel parameters have changed by then and I will consider testing it
again.

[toc] | [prev] | [next] | [standalone]

#1061875

Hello Jim,
I am not involved in packaging, but came to this report by chance.


> The attached file contains all the changes you devs have made in the kernel
> configs from 5.10.28 (-6 package) to 5.10.38/.40 (-7 package). It was made with
> meld.
> ~10 kernel parameters have changed and led to this mess, so I assume it would
> be trivial for you to find the faulty one.

These parameters are not all that changed - there are around 1400 patches
added upstream to the kernel between v5.10.28 and v5.10.38.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v5.10.38


Kind regards,
Bernhard

[toc] | [prev] | [next] | [standalone]

#1061936

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsiorisj@gmail.com

Finally, a sane reply that does not blame nvidia's driver.

I have written above that something must have changed, at least regarding intel
hw, because I was missing the coretemp readings on my conky. However, from the
page you mention, only 2 commits refer to intel and I think both of them are
not related to my hardware.

If it is a kernel issue, which means I will come accross it on any distro I
choose, I should report it on kernel's github page... if it had issue reports.
Besides that, I think I am not smart enough to do it. I reported an similar
issue on openssh (bug 912087) some years ago, but I just could not follow the
conversation until it was resolved, because it was way too technical for me.
Shouldn't a maintainer do that for me like they did for openssh? Now they have
all the logs they need.

The other solution, hopefully, is to wait for the freeze to end, debian to move
to 5.12 or newer and me praying it won't have the same issue.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.bugs.dist

csiph-web