| 2018-03-23 15:50:25 |
dann frazier |
bug |
|
|
added bug |
| 2018-03-23 15:50:37 |
dann frazier |
nominated for series |
|
Ubuntu Artful |
|
| 2018-03-23 15:50:37 |
dann frazier |
bug task added |
|
linux (Ubuntu Artful) |
|
| 2018-03-23 15:50:44 |
dann frazier |
linux (Ubuntu): status |
New |
Fix Released |
|
| 2018-03-23 15:51:06 |
dann frazier |
linux (Ubuntu Artful): status |
New |
In Progress |
|
| 2018-03-23 15:51:08 |
dann frazier |
linux (Ubuntu Artful): assignee |
|
dann frazier (dannf) |
|
| 2018-03-23 19:29:37 |
dann frazier |
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. |
[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.
I have a test fix in ppa:dannf/efifb for regression testing. |
|
| 2018-03-23 20:06:16 |
dann frazier |
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.
I have a test fix in ppa:dannf/efifb for regression testing. |
[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. |
|
| 2018-04-03 15:21:29 |
Kleber Sacilotto de Souza |
linux (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2018-04-10 09:32:45 |
Brad Figg |
tags |
|
verification-needed-artful |
|
| 2018-04-10 16:26:55 |
dann frazier |
tags |
verification-needed-artful |
verification-done-artful |
|
| 2018-04-23 09:21:59 |
Launchpad Janitor |
linux (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2018-04-23 09:21:59 |
Launchpad Janitor |
cve linked |
|
2017-5715 |
|
| 2018-04-23 09:21:59 |
Launchpad Janitor |
cve linked |
|
2017-5754 |
|
| 2018-04-23 09:21:59 |
Launchpad Janitor |
cve linked |
|
2018-8043 |
|
