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: More evidence that the gen4 adapter commit is at fault
On Tue, 4 Dec 2018 15:03:51 -0500 sixerjman wrote: > I have 3 Debian machines in the lab, and two booted 4.18.3 fine. One > has a Radeon GPU, the other is an Intel GM965. The one that gave me > the black screen at boot is: > > lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series > Chipset Integrated Graphics Controller (rev 07) I have the same output on an x200 thinkpad (Intel GM45) for lspci | grep -i vga and can confirm a black screen at "switching to inteldrmfb from efi vga"
Bug#914495: More evidence that the gen4 adapter commit is at fault
I have 3 Debian machines in the lab, and two booted 4.18.3 fine. One has a Radeon GPU, the other is an Intel GM965. The one that gave me the black screen at boot is: lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Bug#914495: nomodeset enabled boot
But the graphics mode is low res (1280x768). Also, 'nomodeset' is no longer documented in the kernel parameters doc ( https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt).
Processed: closing 780837
Processing commands for cont...@bugs.debian.org: > close 780837 Bug #780837 [src:linux] linux-image-3.16.0-4-amd64: USB flash disk does not work in USB 3 ports Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 780837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 915488 is important, reassign 915488 to lvm2
Processing commands for cont...@bugs.debian.org: > severity 915488 important Bug #915488 [initramfs-tools-core] initramfs-tools-core: after dist-upgrade to testing my system can't boot, need to go to recovery then init 5 Severity set to 'important' from 'critical' > reassign 915488 lvm2 Bug #915488 [initramfs-tools-core] initramfs-tools-core: after dist-upgrade to testing my system can't boot, need to go to recovery then init 5 Bug reassigned from package 'initramfs-tools-core' to 'lvm2'. No longer marked as found in versions initramfs-tools/0.132. Ignoring request to alter fixed versions of bug #915488 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 915488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > Found 914517 linux-image-4.18.0-3-amd64 Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set The source 'linux' and version 'linux-image-4.18.0-3-amd64' do not appear to match any binary packages Marked as found in versions linux/linux-image-4.18.0-3-amd64. > Found 914517 linux-image-4.9.0-8-amd64 Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set The source 'linux' and version 'linux-image-4.9.0-8-amd64' do not appear to match any binary packages Marked as found in versions linux/linux-image-4.9.0-8-amd64. > Thanks Stopping processing here. Please contact me if you need assistance. -- 914517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
