Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
sumitted upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=108984
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
On Thu, 6 Dec 2018 18:11:11 +0100 Norbert Brondeau wrote: > > > > lspci | grep -i VGA > 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 > Integrated Graphics Controller (primary) (rev 0c) > > Don't work ! drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5 _UN_commit fb5bbae9b1333d44023713946fdd28db0cd85751 upstream. Fix this bug.
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Package: src:linux Followup-For: Bug #914495 Dear Maintainer, I've the same symptom with linux-image-4.18.0-3-686-pae My laptop have this graphic : # lspci|grep VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Regards François -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information ** Network interface configuration: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.18.0-3-686-pae depends on: ii initramfs-tools [linux-initramfs-tool] 0.132 ii kmod25-2 ii linux-base 4.5 Versions of packages linux-image-4.18.0-3-686-pae recommends: ii apparmor 2.13.1-3+b1 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-0.1 Versions of packages linux-image-4.18.0-3-686-pae suggests: ii debian-kernel-handbook 1.0.19 ii extlinux3:6.04~git20171011.af7e95c3+dfsg1-5 ii grub-pc 2.02+dfsg1-8 ii linux-doc-4.18 4.18.20-2 Versions of packages linux-image-4.18.0-3-686-pae is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Bjørn Mork writes:
> Given this, there is an extremely suspicious commit added in v4.18.20:
>
> 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for
> gen4/gen5")
>
> I do have an old laptop with an affected chipset generation, and
> verified that it had the same symptoms. But never got the time to
> actually test any further. Still, I do think that there is good reason
> to simply try a revert of that commit.
FWIW, I have now verified that reverting commit 06e562e7f515
("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5") fixes
this issue for me.
Bjørn
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
On Wed, 5 Dec 2018 06:45:58 +0100 TS wrote: > TS schrieb/wrote: > > > -- -- > > > > For completeness: > > % lspci | grep -i vga > > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset > > Integrated Graphics Controller (rev 07) > lspci | grep -i VGA 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) Don't work !
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
TS schrieb/wrote: -- -- > For completeness: > % lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset > Integrated Graphics Controller (rev 07) Two machines with: # unameALL Linux desk 4.18.0-3-amd64 #1 SMP Debian 4.18.20-2 (2018-11-23) x86_64 GNU/Linux # lspci | grepE vga 00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) and # unameALL Linux G5000 4.18.0-3-686-pae #1 SMP Debian 4.18.20-2 (2018-11-23) i686 GNU/Linux # lspci | grepE vga 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) boot just fine. kind regards, Thilo
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Bjørn Mork schrieb/wrote:
-- --
> Given this, there is an extremely suspicious commit added in v4.18.20:
>
> 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for
> gen4/gen5")
-- --
> Still, I do think that there is good reason to simply try a revert of that
> commit.
In case such a kernel would be available somewhere i happily would test it.
Making such package myself is sadly beyond the limited scope of personal
expertise.
For completeness:
% lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
kind regards,
Thilo
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Ben Hutchings writes:
> On Mon, 2018-12-03 at 23:08 +0100, TS wrote:
>
>> Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to
>> unstable. This issue here seems not to be wide spread, or reproducible?
>
> Hard to tell. There are a few people that reported the same *symptom*,
> but that doesn't mean they found the same bug.
True of course. But in this case there seems to be a very strong
correlation with Gen4 Intel GPUs. I believe every one of the reports
have had at least a lspci dump showing one of those. And a couple of
the reports had stack traces pointing to gen4_render_ring_flush as well.
Given this, there is an extremely suspicious commit added in v4.18.20:
06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5")
I do have an old laptop with an affected chipset generation, and
verified that it had the same symptoms. But never got the time to
actually test any further. Still, I do think that there is good reason
to simply try a revert of that commit.
Bjørn
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
On Mon, 2018-12-03 at 23:08 +0100, TS wrote: > Ben Hutchings schrieb/wrote: > > -- -- > > > > Since the issue happens very early in boot process debugging is quit > > > difficult. > > > Assistance with further debugging is required if you need additional > > > informations. > > > > You can use a serial console or netconsole to send the kernel log to > > another computer: > > https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html > > https://www.kernel.org/doc/Documentation/networking/netconsole.txt > > Will look into that. My current schedule suggests this will not happen before > weekend though. > > Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to > unstable. This issue here seems not to be wide spread, or reproducible? Hard to tell. There are a few people that reported the same *symptom*, but that doesn't mean they found the same bug. Ben. > This computer here is somewhat lucky in finding special bugs. Last time it was > in Zsh. If i had understand Peter correctly some sort of race condition it was > there. > > Could be something like that here, too. > > > kind regards, > > Thilo -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: This is a digitally signed message part
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Ben Hutchings schrieb/wrote: -- -- >> Since the issue happens very early in boot process debugging is quit >> difficult. >> Assistance with further debugging is required if you need additional >> informations. > > You can use a serial console or netconsole to send the kernel log to > another computer: > https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html > https://www.kernel.org/doc/Documentation/networking/netconsole.txt Will look into that. My current schedule suggests this will not happen before weekend though. Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to unstable. This issue here seems not to be wide spread, or reproducible? This computer here is somewhat lucky in finding special bugs. Last time it was in Zsh. If i had understand Peter correctly some sort of race condition it was there. Could be something like that here, too. kind regards, Thilo
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Control: severity -1 important Control: tag -1 moreinfo On Fri, 2018-11-23 at 22:37 +0100, TS wrote: > Package: src:linux > Version: 4.18.20-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainers, > > linux-image-4.18.0-3-amd64 does not boot on this computer. > After grub shortly cursor is blinking upper left (when usually the initrd is > deflating and systemd starts). > After that nothing happens. > HDD LED does not signalling activity. > Display stays dark, no messages appear with > GRUB_CMDLINE_LINUX_DEFAULT="quiet consoleblank=0 systemd.show_status=1" > set. > > initrd has been rebuild manually before rebooting with > dpkg-reconfigure linux-image-... > > as i get used to. > > Booting linux-image-4.18.0-2-amd64 instead solves the issue. > > Since the issue happens very early in boot process debugging is quit > difficult. > Assistance with further debugging is required if you need additional > informations. You can use a serial console or netconsole to send the kernel log to another computer: https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html https://www.kernel.org/doc/Documentation/networking/netconsole.txt Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: This is a digitally signed message part
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
I have got the same poblem lspci gives: 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03) 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 14:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) 1c:03.0 CardBus bridge: O2 Micro, Inc. OZ711SP1 Memory CardBus Controller (rev 01) 1c:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02) Login-in via ssh and running journalctl -b -p 4: -- Logs begin at Mon 2018-07-09 09:09:01 CEST, end at Fri 2018-11-23 10:42:39 CET. -- Nov 23 10:17:29 apollon-alt kernel: core: PEBS disabled due to CPU errata Nov 23 10:17:29 apollon-alt kernel: pmd_set_huge: Cannot satisfy [mem 0xf800-0xf820] with a huge-page mapping due to MTRR override. Nov 23 10:17:29 apollon-alt kernel: pci :00:1e.0: bridge has subordinate 1d but max busn 20 Nov 23 10:17:30 apollon-alt kernel: Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Nov 23 10:17:40 apollon-alt kernel: excluding 0xfc40-0xfc40 Nov 23 10:17:40 apollon-alt kernel: iwl4965 :14:00.0: can't disable ASPM; OS doesn't have ASPM control Nov 23 10:17:40 apollon-alt kernel: BUG: unable to handle kernel NULL pointer dereference at 0008 Nov 23 10:17:40 apollon-alt kernel: Oops: [#1] SMP PTI Nov 23 10:17:40 apollon-alt kernel: CPU: 1 PID: 345 Comm: systemd-udevd Not tainted 4.18.0-3-amd64 #1 Debian 4.18.20-1 Nov 23 10:17:40 apollon-alt kernel: Hardware name: FUJITSU SIEMENS LIFEBOOK P8010/FJNB1E3, BIOS Version 1.08 08/20/2008 Nov 23 10:17:40 apollon-alt kernel: RIP: 0010:gen4_render_ring_flush+0x55/0xf0 [i915] Nov 23 10:17:40 apollon-alt kernel: Code: 00 be 16 00 00 00 48 89 ef e8 87 fe ff ff 48 3d 00 f0 ff ff 77 69 89 18 c7 40 04 02 40 00 7a 48 8b 55 78 48 8b 92 10 02 00 00 <48> 8b 52 08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 Nov 23 10:17:40 apollon-alt kernel: RSP: 0018:a49200a73a88 EFLAGS: 00010287 Nov 23 10:17:40 apollon-alt kernel: RAX: a49210303000 RBX: 0202 RCX: 0001ff68 Nov 23 10:17:40 apollon-alt kernel: RDX: RSI: 01a8 RDI: 0150 Nov 23 10:17:40 apollon-alt kernel: RBP: 89e0e92adb00 R08: 0001 R09: 0004 Nov 23 10:17:40 apollon-alt kernel: R10: a49200a73a58 R11: R12: 89e0e7a68000 Nov 23 10:17:40 apollon-alt kernel: R13: 89e0e96f8800 R14: R15: 89e0e92adb00 Nov 23 10:17:40 apollon-alt kernel: FS: 7fac6dd658c0() GS:89e0efd0() knlGS: Nov 23 10:17:40 apollon-alt kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 23 10:17:40 apollon-alt kernel: CR2: 0008 CR3: 000127a2c000 CR4: 06e0 Nov 23 10:17:40 apollon-alt kernel: Call Trace: Nov 23 10:17:40 apollon-alt kernel: i915_request_alloc+0x243/0x360 [i915] Nov 23 10:17:40 apollon-alt kernel: i915_gem_init+0x284/0x480 [i915] Nov 23 10:17:40 apollon-alt kernel: i915_driver_load+0xb22/0xef0 [i915] Nov 23 10:17:40 apollon-alt kernel: ? mutex_lock+0xe/0x30 Nov 23 10:17:40 apollon-alt kernel: ? acpi_dev_found+0x5f/0x70 Nov 23 10:17:40 apollon-alt kernel: local_pci_probe+0x42/0xa0 Nov 23 10:17:40
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Amy Kos schrieb/wrote: > Could be graphics related, boot stops at: > > fb: switching to inteldrmfb from EFI VGA > > Disabling kernel mode setting with parameter nomodeset boots to tty. > confirming, adding 'nomodeset' to linux boot options lets linux-image-4.18.0-3-amd64 boot. Thanks Amy for the hint. HTH kind regards, Thilo
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Could be graphics related, boot stops at: fb: switching to inteldrmfb from EFI VGA Disabling kernel mode setting with parameter nomodeset boots to tty.
Bug#914495: linux-image-4.18.0-3-amd64: does not boot here
Package: src:linux Version: 4.18.20-1 Severity: critical Justification: breaks the whole system Dear Maintainers, linux-image-4.18.0-3-amd64 does not boot on this computer. After grub shortly cursor is blinking upper left (when usually the initrd is deflating and systemd starts). After that nothing happens. HDD LED does not signalling activity. Display stays dark, no messages appear with GRUB_CMDLINE_LINUX_DEFAULT="quiet consoleblank=0 systemd.show_status=1" set. initrd has been rebuild manually before rebooting with dpkg-reconfigure linux-image-... as i get used to. Booting linux-image-4.18.0-2-amd64 instead solves the issue. Since the issue happens very early in boot process debugging is quit difficult. Assistance with further debugging is required if you need additional informations. kind regards, Thilo -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: TOSHIBA product_name: Satellite L300 product_version: PSLB8E-12T018GR chassis_vendor: Chassis Manufacturer chassis_version: Chassis Version bios_vendor: INSYDE bios_version: 1.80 board_vendor: TOSHIBA board_name: Portable PC board_version: Base Board Version ** Network interface configuration: auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 iface ethernet inet static network 192.168.10.0 gateway 192.168.10.1 broadcast 192.168.10.255 netmask 255.255.255.0 dns-nameservers 127.0.0.1 allow-hotplug eth0 iface eth0 inet static inherits ethernet address 192.168.10.4 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Memory Controller Hub [1179:ff66] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff67] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff67] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI]) Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB UHCI Controller [1179:ff66] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 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 03) (prog-if 00 [UHCI]) Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB UHCI Controller [1179:ff66] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 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 03) (prog-if 20 [EHCI]) Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) USB2 EHCI Controller [1179:ff66] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 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 03) Subsystem: Toshiba America Info Systems 82801I (ICH9 Family) HD Audio Controller [1179:ff66] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]:
