DMC here stands for Display Micro-Controller, and the blobs are firmware
for DMC. So that's probably a question for VGA and/or BIOS vendors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
@Kent
Is there any comment on why this issue only happened on the config from
customer, but not on our configs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1857883
Title:
This should affect all linux-firmware >= 1.157.13 (factory image has
1.157.12~somerville4, xenial-updates has 1.157.22).
The only work-around so far is to remove
/lib/firmware/i915/kbl_dmc_ver1_01.bin (and
/lib/firmware/i915/kbl_dmc_ver1_04.bin if available).
--
You received this bug
By the way, with kernel newer than 4.18, at the first time
suspend/resume may succeed, but the second time and on it will always
hang.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Filed public issue https://gitlab.freedesktop.org/drm/intel/issues/933.
Since this affects all kernel and linux-firmware versions, removing
kbl_dmc_ver1_*.bin doesn't seem a viable solution that we'll accept
globally. Need further inputs. Pending.
** Bug watch added:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=1156e62c5ec45061955a29e1b9299ffda58479d3 this
commit introduced an update (v1.04 vs. v1.01) to the i915 DMC for Kaby
Lake and has been included in linux-firmware/bionic and on. However this
doesn't fix this
This issue can be reproduced only on:
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620
[8086:5917] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Dell UHD Graphics 620 [1028:0817]
Latest v5.5-rc5 mainline kernel + korg HEAD linux-firmware doesn't fix
This commit was first cherry-picked to linux-firmware from upstream in
bug 1637481 as https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source
/linux-
firmware/commit/?h=xenial=f428ce858f2bcd5a5e5c0869db6ac09a1a110d79
for bringing in firmware blobs from yakkety, and was then reverted as
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-
firmware/commit/?h=xenial=4c85562e738eaf5c8b96ef832954aeb10523f970 is
the first broken commit that may hang the system in the first or second
suspend/resume process when booting with 4.4.0-100-generic kernel, and
linux-firmware
I can reproduce with following steps:
1. do factory recovery (Xenial oem install)
2. upgrade linux-firmware along to 1.157.22
3. completely power off and reboot after 1 minute
4. trigger system suspend
In the beginning CAP lock indicator is blinking, and then keyboard may
have one flash, then
10 matches
Mail list logo
