Public bug reported:
[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. I have a test fix in
ppa:dannf/efifb for regression testing.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => dann frazier (dannf)
--
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:
In Progress
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. 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 : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
