ubuntu@alekhin:~$ cat /proc/version Linux version 4.13.0-39-generic (buildd@bos02-arm64-024) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #44~16.04.1-Ubuntu SMP Thu Apr 5 16:44:45 UTC 2018 ubuntu@alekhin:~$ dmesg | grep "failed to claim resource for efifb"
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758375 Title: efifb broken on ThunderX-based Gigabyte nodes Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] The following error is reported on boot: [ 6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for efifb! This results in the efifb not being activated at boot. On this platform, the same device will be initialized by the astdrmfb driver later in boot, so this isn't fatal, so the real SRU justification here is getting rid of the error message. It is possible that there are platforms where the efifb is behind a PCI bridge, and there is no accelerated alternative that will load later. This (theoretical) issue is most likely to impact d-i installs, where only a subset of fb drivers are included. [Test Case] dmesg | grep "failed to claim resource for efifb" [Regression Risk] The fix for this has been upstream since v4.14 with no known regressions. The driver is only used on EFI systems, which limits the risk to a subset of x86/ARM platforms. Regression tested on a Dell PowerEdge T610 (x86/UEFI). I have a test fix in ppa:dannf/efifb for regression testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp