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-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-

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 for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-artful

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  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:
  The following error is reported on boot:

  [    6.290553] pci 0004:21:00.0: BAR 0: failed to claim resource for

  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:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to