update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | initramfs-tools |
Undecided
|
Unassigned | ||
| | linux (Ubuntu) |
High
|
Joseph Salisbury | ||
| | Bionic |
High
|
Joseph Salisbury | ||
Bug Description
== SRU Justification ==
This firmware was optional when the MODULE_FIRMWARE statements were
removed in bug 1626740 by Bionic commit dc0f16f9b50. The firmware is now
available and in use, so these statements need to be added back.
Without these statements, The i915 Kabylake GuC firmware is failing to load
on boot, and generating dmesg errors.
== Fix ==
Revert Bionic commit dc0f16f9b5084e6
== Regression Potential ==
Low. Adding a statement back that was removed by a SAUCE patch.
== Test Case ==
A test kernel was built with this patch and tested by the original bug reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Report ==
The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org.
I then ran update-initramfs verbosely, and see that only /lib/firmware/
I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue?
Output and logs:
-----------------
ls -al /lib/firmware/
-rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/
lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/
-rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/
-rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/
sudo cat /sys/kernel/
GuC firmware status:
path: i915/kbl_
fetch: FAIL
load: NONE
version wanted: 9.14
version found: 0.0
header: offset is 0; size = 0
uCode: offset is 0; size = 0
RSA: offset is 0; size = 0
GuC status 0x00000001:
Bootrom status = 0x0
uKernel status = 0x0
MIA Core status = 0x0
Scratch registers:
0: 0x0
1: 0x0
2: 0x0
3: 0x0
4: 0x0
5: 0x0
6: 0x0
7: 0x0
8: 0x0
9: 0x0
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
sudo cat /sys/kernel/
HuC firmware status:
path: i915/kbl_
fetch: SUCCESS
load: SUCCESS
version wanted: 2.0
version found: 2.0
header: offset is 0; size = 128
uCode: offset is 128; size = 218304
RSA: offset is 218432; size = 256
HuC status 0x00006000:
dmesg
[ 1.052879] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[ 1.080320] rtsx_pci 0000:3b:00.0: enabling device (0000 -> 0002)
[ 1.082308] nvme nvme0: pci function 0000:3c:00.0
[ 1.095073] Setting dangerous option enable_guc_loading - tainting kernel
[ 1.095075] Setting dangerous option enable_
[ 1.097867] [drm] Memory usable by graphics device = 4078M
[ 1.097869] checking generic (90000000 1fb0000) vs hw (90000000 10000000)
[ 1.097869] fb: switching to inteldrmfb from EFI VGA
[ 1.097899] Console: switching to colour dummy device 80x25
[ 1.098049] [drm] Replacing VGA console driver
[ 1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.104157] [drm] Driver supports precise vblank timestamp query.
[ 1.112506] [drm] Finished loading DMC firmware i915/kbl_
[ 1.113055] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=
[ 1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
[ 1.298572] nvme0n1: p1 p2
[ 1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
[ 1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.433243] usb 1-1: Product: USB+PS2 Keyboard
[ 1.433244] usb 1-1: Manufacturer: Generic
[ 1.446460] usbcore: registered new interface driver usbhid
[ 1.446461] usbhid: USB HID core driver
[ 1.448067] input: Generic USB+PS2 Keyboard as /devices/
[ 1.508451] hid-generic 0003:0D62:
[ 1.508541] input: Generic USB+PS2 Keyboard as /devices/
[ 1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[ 1.568448] hid-generic 0003:0D62:
[ 1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
[ 1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.695657] usb 1-2: Product: USB Receiver
[ 1.695658] usb 1-2: Manufacturer: Logitech
[ 1.702641] logitech-djreceiver 0003:046D:
[ 1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
[ 1.835948] input: Logitech M510 as /devices/
[ 1.836129] logitech-
[ 1.838085] input: Logitech K750 as /devices/
[ 1.838283] logitech-
[ 1.896270] psmouse serio1: synaptics: queried max coordinates: x [..5666], y [..4734]
[ 1.927267] psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1118..]
[ 1.927271] psmouse serio1: synaptics: Your touchpad (PNP: DLL075b PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.
[ 1.938732] i915 0000:00:02.0: Direct firmware load for i915/kbl_
[ 1.938733] [drm] Failed to fetch valid uC firmware from i915/kbl_
[ 1.944000] [drm:intel_
[ 1.944027] [drm] Falling back from GuC submission to execlist mode
[ 1.944027] [drm] GuC firmware loading disabled
[ 1.944746] [drm] Initialized i915 1.6.0 20170619 for 0000:00:02.0 on minor 0
[ 1.948280] clocksource: Switched to clocksource tsc
[ 1.955378] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 1.956112] input: Video Bus as /devices/
[ 1.961603] usb 1-3: New USB device found, idVendor=0cf3, idProduct=e301
[ 1.961604] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
sudo update-initramfs -u -v -k all
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding module /lib/modules/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
| description: | updated |
| tags: | added: artful |
| description: | updated |
| tags: | added: firmware i915 |
| summary: |
- initramfs not adding i915 GuC firmware, firmware fails to load + update-initramfs not adding i915 GuC firmware, firmware fails to load |
| tags: | added: broxton kabylake |
| description: | updated |
| no longer affects: | initramfs-tools |
| spike speigel (frail-knight) wrote : Re: update-initramfs not adding i915 GuC firmware, firmware fails to load | #1 |
| spike speigel (frail-knight) wrote : | #2 |
UGH, apparently Launchpad like to link bugs for you, and in this case, it linked the Debian bug #s to unrelated projects/package bugs...Please disregard the links in Comment #1
| tags: | added: xenial zesty |
| Changed in initramfs-tools (Debian): | |
| status: | Unknown → Fix Released |
| spike speigel (frail-knight) wrote : | #3 |
I looked into this a bit more, and it seems Ubuntu is basing off of linux-firmware at kernel.org and not following Debian's use of firmware-
| Changed in initramfs-tools (Debian): | |
| importance: | Unknown → Undecided |
| status: | Fix Released → New |
| Launchpad Janitor (janitor) wrote : | #4 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in initramfs-tools (Ubuntu): | |
| status: | New → Confirmed |
| Paul Malmsten (pmalmsten) wrote : | #5 |
Also hit this issue on a Dell XPS 13 9360 (i7-8550U) running 17.10 and initramfs-tools 0.125ubuntu12. Until a fix is available, I was able to workaround the issue by adding my own initramfs-tools hook.
I created a hook script to copy the firmware:
$ cat /etc/initramfs-
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/
# Begin real processing below this line
copy_file firmware /lib/firmware/
exit 0
Marked the script as executable, and updated all initramfs images:
$ sudo chmod u+x /etc/initramfs-
$ sudo update-initramfs -k all -u
$ sudo update-grub
After reboot, success:
$ sudo cat /sys/kernel/
GuC firmware status:
path: i915/kbl_
fetch: SUCCESS
load: SUCCESS
version wanted: 9.14
version found: 9.14
header: offset is 0; size = 128
uCode: offset is 128; size = 142272
RSA: offset is 142400; size = 256
GuC status 0x800330ed:
Bootrom status = 0x76
uKernel status = 0x30
MIA Core status = 0x3
Scratch registers:
0: 0xf0000000
1: 0x0
2: 0x0
3: 0x5f5e100
4: 0x600
5: 0xd5fd3
6: 0x0
7: 0x8
8: 0x3
9: 0x74240
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
| spike speigel (frail-knight) wrote : | #6 |
Thanks Paul, that workaround helped me. The 9.14 GuC loads now. I tried downloading the new 9.39 GuC on intel's site, and changing the version in the hook script, but the 9.39 firmware would not load for some reason. Maybe due to both firmware versions existing in /lib/firmware/i915/ on my system and the older one being seen/used first. I might try again later and moving the older firmware, but am content with it loading as it is now.
| Thorsten (thorstenr-42) wrote : | #7 |
also happens on ubuntu 18.04 on a i7-8550U
[ 2.084195] i915 0000:00:02.0: Direct firmware load for i915/kbl_
[ 2.084196] [drm] GuC: Failed to fetch firmware i915/kbl_
[ 2.084197] [drm] GuC: Firmware can be downloaded from https:/
[ 2.089954] [drm] HuC: Loaded firmware i915/kbl_
[ 2.090000] [drm] GuC init failed. Firmware loading disabled.
[ 2.090003] [drm] Falling back from GuC submission to execlist mode
[ 2.090717] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 0
| tags: | added: bionic |
| tags: | added: xps |
| tags: | added: 9360 |
| tags: | added: i965 |
| tags: | added: kbl |
| tags: | added: bxt |
| tags: | added: intel |
| tags: | added: dell |
| no longer affects: | initramfs-tools (Debian) |
| dino99 (9d9) wrote : | #8 |
*******
Looks like its more a kernel issue related to the Dell drivers, not requesting the missing GuC.
https:/
I suppose initramfs is not faulty; maybe linux-firmware is.
Better opening a separate kernel bug on launchpad and upstream to get a fix chance (need to check the latest kernel version to know if that issue is solved)
*******
| Thorsten (thorstenr-42) wrote : | #9 |
i can just add that its working fine under arch. However the error occurs under ubuntu 18.04. Both use 4.15.
Moreover i have a thinkpad x1 gen 6 and not a dell
| dino99 (9d9) wrote : | #10 |
Good to know; so its mostly due to the ubuntu kernel patches added / custom settings.
| Jordan (j0rd-spam) wrote : | #11 |
Same problem.
x1 carbon gen6 like Thorsten, Ubuntu 18.04. Kernel 4.15.
| virgosun (hdefendme) wrote : | #12 |
Thanks for the work around!
Why it affects only my custom kernel 4.14.0.15 Artful?
| Ernst Sjöstrand (ernstp) wrote : | #13 |
mkinitramfs runs modinfo -F firmware i915 which only lists the following files:
i915/bxt_
i915/skl_
i915/kbl_
i915/skl_
i915/kbl_
i915/bxt_
i915/skl_
| tags: | added: carbon gen6 lenovo thinkpad x1 |
| mtvoid (mtvoid) wrote : | #14 |
This is the commit that is responsible for the Kabylake GuC firmware file not being registered in the i915 module on Ubuntu kernels: http://
This is the accompanying bug report: https:/
I've also commented there to bring the issue to their attention. The change should be reverted now that the formerly missing firmware files are present in linux-firmware.
| affects: | initramfs-tools (Ubuntu) → linux (Ubuntu) |
| summary: |
- update-initramfs not adding i915 GuC firmware, firmware fails to load + update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware + fails to load |
| spike speigel (frail-knight) wrote : | #15 |
Are they aware the same issue appears to be happening with the Broxton firmware as well? Should that be tracked under a separate issue?
| mtvoid (mtvoid) wrote : | #16 |
Reverting that commit will address the firmware loading issue for both kbl and bxt. Although as far as I understand, Intel had cancelled Broxton, and there are no chips based on it in the market, so it's basically Kaby Lake users that are affected.
| tags: | added: kernel-da-key |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → High |
| Joseph Salisbury (jsalisbury) wrote : | #17 |
I built a Bionic test kernel with a revert of the following commit:
dc0f16f9b508 ("UBUNTU: SAUCE: (no-up) i915: Remove MODULE_FIRMWARE statements for unreleased firmware")
The test kernel can be downloaded from:
http://
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the linux-image-
Thanks in advance!
| spike speigel (frail-knight) wrote : | #18 |
@mtvoid Thank you for clearing that up. I was not aware that Broxton was Atom. For some reason I thought it was an earlier generation x64 Core architecture.
@jsalisbury I am running Bionic. I've never tested a kernel before, but am willing to do so.
| spike speigel (frail-knight) wrote : | #19 |
@jsalisbury This does indeed fix the issue:
~$ sudo update-initramfs -u -v -k all|grep kbl
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
/usr/sbin/
/usr/sbin/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
/usr/sbin/
/usr/sbin/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
~$ uname -a
Linux 4.15.0-20-generic #21~lp1728238 SMP Mon May 7 16:50:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
~$ sudo cat /sys/kernel/
GuC firmware: i915/kbl_
status: fetch SUCCESS, load SUCCESS
version: wanted 9.14, found 9.14
header: offset 0, size 128
uCode: offset 128, size 142272
RSA: offset 142400, size 256
GuC status 0x800330ed:
Bootrom status = 0x76
uKernel status = 0x30
MIA Core status = 0x3
Scratch registers:
0: 0xf0000000
1: 0x0
2: 0x0
3: 0x5f5e100
4: 0x600
5: 0xcdfd3
6: 0x0
7: 0x8
8: 0x3
9: 0x70240
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
~$ sudo cat /sys/kernel/
HuC firmware: i915/kbl_
status: fetch SUCCESS, load SUCCESS
version: wanted 2.0, found 2.0
header: offset 0, size 128
uCode: offset 128, size 218304
RSA: offset 218432, size 256
HuC status 0x00006080:
| spike speigel (frail-knight) wrote : | #20 |
And to clarify when I ran:
sudo update-initramfs -u -v -k all|grep kbl
The first round of firmware files is for 4.15.0-21-generic while the second listing is for your patched kernel. Notice the added GuC entry. As you can see the GuC firmware loads when running your patched kernel.
Thank you for building the test kernel :)
| Changed in linux (Ubuntu): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| status: | Confirmed → In Progress |
| Changed in linux (Ubuntu Bionic): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Joseph Salisbury (jsalisbury) wrote : | #21 |
SRU request submitted:
https:/
| description: | updated |
| Changed in linux (Ubuntu Bionic): | |
| status: | In Progress → Fix Committed |
| Brad Figg (brad-figg) wrote : | #22 |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
| tags: | added: verification-needed-bionic |
| mtvoid (mtvoid) wrote : | #23 |
Using the 4.15.0-23-generic kernel from bionic-proposed correctly loads the GuC firmware as expected:
[ 1.470927] [drm] Finished loading DMC firmware i915/kbl_
[ 1.483832] [drm] HuC: Loaded firmware i915/kbl_
[ 1.494403] [drm] GuC: Loaded firmware i915/kbl_
[ 1.509669] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_
| tags: |
added: verification-done-bionic removed: 9360 carbon dell lenovo thinkpad verification-needed-bionic x1 xps |
| Launchpad Janitor (janitor) wrote : | #24 |
This bug was fixed in the package linux - 4.15.0-23.25
---------------
linux (4.15.0-23.25) bionic; urgency=medium
* linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
* arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
- arm64: mmu: add the entry trampolines start/end section markers into
sections.h
- arm64: sdei: Add trampoline code for remapping the kernel
* Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
- ACPI: APEI: handle PCIe AER errors in separate function
- ACPI: APEI: call into AER handling regardless of severity
* qla2xxx: Fix page fault at kmem_cache_
- scsi: qla2xxx: Fix session cleanup for N2N
- scsi: qla2xxx: Remove unused argument from qlt_schedule_
- scsi: qla2xxx: Serialize session deletion by using work_lock
- scsi: qla2xxx: Serialize session free in qlt_free_
- scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
- scsi: qla2xxx: Fix warning in qla2x00_
- scsi: qla2xxx: Prevent relogin trigger from sending too many commands
- scsi: qla2xxx: Fix double free bug after firmware timeout
- scsi: qla2xxx: Fixup locking for session deletion
* Several hisi_sas bug fixes (LP: #1768974)
- scsi: hisi_sas: dt-bindings: add an property of signal attenuation
- scsi: hisi_sas: support the property of signal attenuation for v2 hw
- scsi: hisi_sas: fix the issue of link rate inconsistency
- scsi: hisi_sas: fix the issue of setting linkrate register
- scsi: hisi_sas: increase timer expire of internal abort task
- scsi: hisi_sas: remove unused variable hisi_sas_
- scsi: hisi_sas: fix return value of hisi_sas_
- scsi: hisi_sas: Code cleanup and minor bug fixes
* [bionic] machine stuck and bonding not working well when nvmet_rdma module
is loaded (LP: #1764982)
- nvmet-rdma: Don't flush system_wq by default during remove_one
- nvme-rdma: Don't flush delete_wq by default during remove_one
* Warnings/hang during error handling of SATA disks on SAS controller
(LP: #1768971)
- scsi: libsas: defer ata device eh commands to libata
* Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
- ata: do not schedule hot plug if it is a sas host
* ISST-LTE:
ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
- powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
- powerpc/64s: return more carefully from sreset NMI
- powerpc/64s: sreset panic if there is no debugger or crash dump handlers
* fsnotify: Fix fsnotify_
- fsnotify: Fix fsnotify_
* Hang on network interface removal in Xen virtual machine (LP: #1771620)
- xen-netfront: Fix hang on device removal
* HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
- net: hns: Avoid action name truncation
* Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
- SAUCE: powerpc/perf: Fix memory allocation for...
| Changed in linux (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
| status: | Fix Committed → Fix Released |
| Changed in initramfs-tools: | |
| status: | New → Invalid |
| Changed in linux (Ubuntu): | |
| status: | In Progress → Fix Released |
| Joseph Salisbury (jsalisbury) wrote : | #27 |
It now appears reverting Bionic commit dc0f16f9b508 has introduced bug 1777242. We need to put now either revert the revert or find an alternative fix.
| Changed in linux (Ubuntu): | |
| status: | Fix Released → In Progress |
| Changed in linux (Ubuntu Bionic): | |
| status: | Fix Released → In Progress |
| mtvoid (mtvoid) wrote : | #28 |
On the face of it, I cannot see how this particular commit could in any way cause that other bug to arise. All it does is to allow the i915 driver to load a particular firmware file, and that too only if it's explicitly specified on the kernel command line.
I think bug 1777242 needs to be investigated further, to find the exact conditions under which it can be reliably replicated. The comment https:/
| spike speigel (frail-knight) wrote : | #29 |
So this is now broken again?
| Georgi Boiko (pandasauce) wrote : | #30 |
This issue with being unable to load GuC blobs also affects xenial at 4.13.0-45 kernel (latest).
| grek (greku) wrote : | #31 |
Hey,
I have a INTEL NUC with Pentium Silver J5005.
I got similar error with firmware loading.
uname -a
Linux darkstar 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
dmesg |grep i915
[ 2.042518] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=
[ 2.043007] i915 0000:00:02.0: Direct firmware load for i915/glk_
[ 2.043010] i915 0000:00:02.0: Failed to load DMC firmware i915/glk_
[ 2.043012] i915 0000:00:02.0: DMC firmware homepage: https:/
[ 2.045950] [drm] Initialized i915 1.6.0 20171023 for 0000:00:02.0 on minor 0
[ 2.231576] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 3.686381] snd_hda_intel 0000:00:0e.0: bound 0000:00:02.0 (ops i915_audio_
/lib/firmware/i915# ll
razem 1724
drwxr-xr-x 2 root root 4096 lip 27 15:06 ./
drwxr-xr-x 82 root root 20480 lip 27 15:06 ../
-rw-r--r-- 1 root root 8380 lis 17 2017 bxt_dmc_ver1_07.bin
lrwxrwxrwx 1 root root 19 lis 17 2017 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin
-rw-r--r-- 1 root root 140928 maj 18 20:09 bxt_guc_ver8_7.bin
-rw-r--r-- 1 root root 146432 maj 18 20:09 bxt_guc_ver9_29.bin
-rw-r--r-- 1 root root 154432 gru 5 2017 bxt_huc_
-rw-r--r-- 1 root root 11224 maj 18 20:09 cnl_dmc_ver1_06.bin
-rw-r--r-- 1 root root 11268 maj 18 20:09 cnl_dmc_ver1_07.bin
-rw-r--r-- 1 root root 8800 kwi 24 17:28 glk_dmc_ver1_04.bin
-rw-r--r-- 1 root root 8616 lis 17 2017 kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 8840 maj 18 20:09 kbl_dmc_ver1_04.bin
lrwxrwxrwx 1 root root 19 lis 17 2017 kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 142656 maj 18 20:09 kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 147776 maj 18 20:09 kbl_guc_ver9_39.bin
-rw-r--r-- 1 root root 218688 gru 5 2017 kbl_huc_
-rw-r--r-- 1 root root 8824 mar 30 2017 skl_dmc_ver1_23.bin
-rw-r--r-- 1 root root 8928 mar 30 2017 skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 8928 maj 18 20:09 skl_dmc_ver1_27.bin
lrwxrwxrwx 1 root root 19 mar 30 2017 skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin
-rw-r--r-- 1 root root 109636 maj 18 20:09 skl_guc_ver1.bin
-rw-r--r-- 1 root root 128320 maj 18 20:09 skl_guc_ver4.bin
-rw-r--r-- 1 root root 129024 mar 30 2017 skl_guc_ver6_1.bin
lrwxrwxrwx 1 root root 18 mar 30 2017 skl_guc_ver6.bin -> skl_guc_ver6_1.bin
-rw-r--r-- 1 root root 147520 maj 18 20:09 skl_guc_ver9_33.bin
-rw-r--r-- 1 root root 140992 gru 5 2017 skl_huc_
root@darkstar:
Adding module /lib/modules/
Adding module /lib/modules/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
Adding firmware /lib/firmware/
| Launchpad Janitor (janitor) wrote : | #32 |
This bug was fixed in the package linux - 4.17.0-6.7
---------------
linux (4.17.0-6.7) cosmic; urgency=medium
* linux: 4.17.0-6.7 -proposed tracker (LP: #1783396)
* [Regression] EXT4-fs error (device sda2): ext4_validate_
comm stress-ng: bg 4705: bad block bitmap checksum (LP: #1781709)
- SAUCE: Revert "UBUNTU: SAUCE: ext4: fix ext4_validate_
stress-ng: Corrupt inode bitmap"
- SAUCE: ext4: check for allocation block validity with block group locked
* Cosmic update to 4.17.9 stable release (LP: #1783201)
- userfaultfd: hugetlbfs: fix userfaultfd_
- mm: hugetlb: yield when prepping struct pages
- mm: teach dump_page() to correctly output poisoned struct pages
- PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM
- ACPICA: Drop leading newlines from error messages
- ACPI / battery: Safe unregistering of hooks
- drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c
- tracing: Avoid string overflow
- tracing: Fix missing return symbol in function_graph output
- scsi: sg: mitigate read/write abuse
- scsi: aacraid: Fix PD performance regression over incorrect qd being set
- scsi: target: Fix truncated PR-in ReadKeys response
- s390: Correct register corruption in critical section cleanup
- drbd: fix access after free
- vfio: Use get_user_
- ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl
- ARM: dts: omap3: Fix am3517 mdio and emac clock references
- ARM: dts: dra7: Disable metastability workaround for USB2
- cifs: Fix use after free of a mid_q_entry
- cifs: Fix memory leak in smb2_set_ea()
- cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting
- cifs: Fix infinite loop when using hard mount option
- drm: Use kvzalloc for allocating blob property memory
- drm/udl: fix display corruption of the last line
- drm/amdgpu: Add amdgpu_
- drm/amdgpu: Dynamically probe for ATIF handle (v2)
- jbd2: don't mark block as modified if the handle is out of credits
- ext4: add corruption check in ext4_xattr_
- ext4: always verify the magic number in xattr blocks
- ext4: make sure bitmaps and the inode table don't overlap with bg
descriptors
- ext4: always check block group bounds in ext4_init_
- ext4: only look at the bg_flags field if it is valid
- ext4: verify the depth of extent tree in ext4_find_extent()
- ext4: include the illegal physical block in the bad map ext4_error msg
- ext4: clear i_data in ext4_inode_info when removing inline data
- ext4: never move the system.data xattr out of the inode body
- ext4: avoid running out of journal credits when appending to an inline file
- ext4: add more inode number paranoia checks
- ext4: add more mount time checks of the superblock
- ext4: check superblock mapped prior to committing
- HID: i2c-hid: Fix "incomplete report" noise
- HID: hiddev: fix potential Spectre v1
- HID: debug: check length before copy_to_user()
- HID: core: allow concurrent registr...
| Changed in linux (Ubuntu): | |
| status: | In Progress → Fix Released |
| maravento (maravento) wrote : | #33 |
Bug Confirm in Ubuntu Mate 18.04.1 x64 kernel 4.15.0-39-generic (work around doesn't work)
| Changed in linux (Ubuntu Bionic): | |
| status: | In Progress → Fix Released |
It appears that bug #857997 in Debian's tracker was merged into Bug #854695. Just wanted to note that, and update the external tracker URL.