efifb: cannot reserve video memory at 0xe0000000

Bug #1787260 reported by Tom Reynolds
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned
Bionic
Confirmed
Medium
Unassigned

Bug Description

Bionic's 4.15.0-32-generic #35-Ubuntu (Fri Aug 10 17:58:07 UTC 2018) fails while probing for efifb on this AMD Ryzen 1800x:

[ 0.786116] efifb: probing for efifb
[ 0.786118] efifb: cannot reserve video memory at 0xe0000000
[ 0.786120] ------------[ cut here ]------------
[ 0.786121] ioremap on RAM at 0x00000000e0000000 - 0x00000000e12fffff
[ 0.786127] WARNING: CPU: 1 PID: 1 at /build/linux-wuhukg/linux-4.15.0/arch/x86/mm/ioremap.c:166 __ioremap_caller+0x2a3/0x320
[ 0.786129] Modules linked in:
[ 0.786132] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-32-generic #35-Ubuntu
[ 0.786134] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P4.70 04/17/2018
[ 0.786136] RIP: 0010:__ioremap_caller+0x2a3/0x320
[ 0.786138] RSP: 0018:ffffa01c0005fbe0 EFLAGS: 00010286
[ 0.786140] RAX: 0000000000000000 RBX: 00000000e0000000 RCX: ffffffff8f062868
[ 0.786142] RDX: 0000000000000001 RSI: 0000000000000086 RDI: 0000000000000246
[ 0.786143] RBP: ffffa01c0005fc48 R08: 0000000000000000 R09: 000000000000029b
[ 0.786145] R10: ffff93c14f351000 R11: 0766073207310765 R12: 0000000001300000
[ 0.786146] R13: 0000000000000001 R14: 0000000001300000 R15: ffffffff8e1384a8
[ 0.786148] FS: 0000000000000000(0000) GS:ffff93c14ec40000(0000) knlGS:0000000000000000
[ 0.786150] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.786151] CR2: 0000000000000000 CR3: 000000056d00a000 CR4: 00000000003406e0
[ 0.786153] Call Trace:
[ 0.786157] ? _cond_resched+0x19/0x40
[ 0.786159] ioremap_wc+0x17/0x20
[ 0.786163] efifb_probe+0x318/0x7c0
[ 0.786166] platform_drv_probe+0x3e/0xa0
[ 0.786168] driver_probe_device+0x31e/0x490
[ 0.786171] ? set_debug_rodata+0x17/0x17
[ 0.786173] __driver_attach+0xa7/0xf0
[ 0.786175] ? driver_probe_device+0x490/0x490
[ 0.786177] bus_for_each_dev+0x70/0xc0
[ 0.786179] driver_attach+0x1e/0x20
[ 0.786180] bus_add_driver+0x1c7/0x270
[ 0.786183] ? vesafb_driver_init+0x19/0x19
[ 0.786185] driver_register+0x60/0xe0
[ 0.786187] ? vesafb_driver_init+0x19/0x19
[ 0.786189] __platform_driver_register+0x36/0x40
[ 0.786191] efifb_driver_init+0x17/0x19
[ 0.786192] do_one_initcall+0x52/0x19f
[ 0.786195] kernel_init_freeable+0x1af/0x251
[ 0.786197] ? rest_init+0xb0/0xb0
[ 0.786199] kernel_init+0xe/0x110
[ 0.786201] ret_from_fork+0x22/0x40
[ 0.786203] Code: fe ff ff 4c 89 c7 e8 dd e1 1a 00 e9 d3 fe ff ff 48 8d 55 c8 48 8d 75 b8 48 c7 c7 d7 5c cc 8e c6 05 8b ad 59 01 01 e8 cd 6f 01 00 <0f> 0b 45 31 ed e9 dd fd ff ff 0f b7 05 4e 46 3c 01 48 09 45 a8
[ 0.786222] ---[ end trace a5f176b1242af8ce ]---
[ 0.786223] efifb: abort, cannot ioremap video memory 0x1300000 @ 0xe0000000
[ 0.786226] efi-framebuffer: probe of efi-framebuffer.0 failed with error -5

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: user1 2748 F.... pulseaudio
 /dev/snd/controlC0: user1 2748 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Aug 15 19:09:25 2018
HibernationDevice: RESUME=/dev/mapper/vg-swap
InstallationDate: Installed on 2017-04-29 (472 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg-slash ro
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago)
dmi.bios.date: 04/17/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.70
dmi.board.name: X370 Taichi
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd04/17/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Tom Reynolds (tomreyn) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Bionic):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Bionic):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Naeil EZZOUEIDI (naeilzoueidi) wrote :

I have tried to reproduce the same behavior that you got but with no luck.

BTW, I am testing with v4.18 linux kernel.

Revision history for this message
Tom Reynolds (tomreyn) wrote :

This issue started happening on 16.04.5 with HWE kernel:

Aug 15 05:51:09 hostname kernel: [ 0.000000] Linux version 4.15.0-32-generic (buildd@lgw01-amd64-038) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #35~16.04.1-Ubuntu SMP Fri Aug 10 21:54:34 UTC 2018 (Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18)

This may not have been the first occurrence but all earlier boots have already rotated out of syslog, thanks to UFW log spam.

I only noticed this oops once I upgraded to 18.04.1 later on this 2018-08-15. It occurs on every boot since.

I will test mainline and report back.

Revision history for this message
Tom Reynolds (tomreyn) wrote :
Download full text (3.5 KiB)

Still present on 4.18:

$ dmesg | grep -FB3 -A50 ' cut here '
[ 0.776810] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 0.776847] efifb: probing for efifb
[ 0.776849] efifb: cannot reserve video memory at 0xe0000000
[ 0.776851] ------------[ cut here ]------------
[ 0.776853] ioremap on RAM at 0x00000000e0000000 - 0x00000000e12fffff
[ 0.776859] WARNING: CPU: 4 PID: 1 at arch/x86/mm/ioremap.c:166 __ioremap_caller+0x2bc/0x2d0
[ 0.776861] Modules linked in:
[ 0.776863] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 4.18.0-041800-generic #201808122131
[ 0.776865] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P4.70 04/17/2018
[ 0.776868] RIP: 0010:__ioremap_caller+0x2bc/0x2d0
[ 0.776870] Code: 0f b7 05 a9 51 3c 01 49 09 c7 e9 f1 fe ff ff 48 8d 55 c8 48 8d 75 b8 48 c7 c7 7d 2c ae ac c6 05 d2 c6 5b 01 01 e8 26 78 01 00 <0f> 0b 31 db e9 64 ff ff ff e8 76 75 01 00 66 0f 1f 44 00 00 0f 1f
[ 0.776886] RSP: 0018:ffffb3cbc005fbd8 EFLAGS: 00010286
[ 0.776887] RAX: 0000000000000000 RBX: 0000000000000001 RCX: fffffffface62608
[ 0.776889] RDX: 0000000000000001 RSI: 0000000000000092 RDI: 0000000000000246
[ 0.776891] RBP: ffffb3cbc005fc40 R08: 0000000000000000 R09: 000000000000029c
[ 0.776893] R10: ffff9a77ce949f00 R11: 0766073207310765 R12: 00000000e0000000
[ 0.776894] R13: 0000000001300000 R14: 0000000001300000 R15: 0000000001300000
[ 0.776896] FS: 0000000000000000(0000) GS:ffff9a77ced00000(0000) knlGS:0000000000000000
[ 0.776898] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.776900] CR2: 0000000000000000 CR3: 00000001a6c0a000 CR4: 00000000003406e0
[ 0.776901] Call Trace:
[ 0.776906] ? _cond_resched+0x19/0x30
[ 0.776909] ? efifb_probe.cold.5+0x2db/0x55f
[ 0.776912] ioremap_wc+0x17/0x20
[ 0.776914] efifb_probe.cold.5+0x2db/0x55f
[ 0.776917] platform_drv_probe+0x3d/0x90
[ 0.776919] driver_probe_device+0x2e3/0x460
[ 0.776921] __driver_attach+0xe4/0x110
[ 0.776923] ? driver_probe_device+0x460/0x460
[ 0.776925] bus_for_each_dev+0x74/0xb0
[ 0.776929] ? kmem_cache_alloc_trace+0x1c4/0x1d0
[ 0.776931] driver_attach+0x1e/0x20
[ 0.776932] bus_add_driver+0x159/0x230
[ 0.776936] ? vesafb_driver_init+0x19/0x19
[ 0.776939] ? do_early_param+0x95/0x95
[ 0.776941] driver_register+0x70/0xc0
[ 0.776943] ? vesafb_driver_init+0x19/0x19
[ 0.776945] __platform_driver_register+0x36/0x40
[ 0.776947] efifb_driver_init+0x17/0x19
[ 0.776950] do_one_initcall+0x4a/0x1c4
[ 0.776952] ? do_early_param+0x95/0x95
[ 0.776954] kernel_init_freeable+0x1b7/0x261
[ 0.776957] ? rest_init+0xb0/0xb0
[ 0.776958] kernel_init+0xe/0x104
[ 0.776960] ret_from_fork+0x22/0x40
[ 0.776963] ---[ end trace 1748f2102269e213 ]---
[ 0.776965] efifb: abort, cannot ioremap video memory 0x1300000 @ 0xe0000000
[ 0.776969] efi-framebuffer: probe of efi-framebuffer.0 failed with error -5
[ 0.777053] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[ 0.777061] ACPI: Power Button [PWRB]
[ 0.777085] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
...

Read more...

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Please ignore the MWAIT comment, this is present ever since I set BIOS option
  Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control
to the necessary (for system stability on any Ryzen CPU) non-standard value of 'Typical current' (#1690085).

Tom Reynolds (tomreyn)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Bionic):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Tom Reynolds (tomreyn) wrote :

Could "[PATCH V2 2/2] efi/fb: Convert PCI bus address to resource if translated by the bridge" https://lkml.org/lkml/2018/5/18/729 be related?

Revision history for this message
Tom Reynolds (tomreyn) wrote :

This may have been a BIOS bug, does not occur after BIOS upgrade (BIOS P4.70 04/17/2018 -> BIOS L4.81 08/16/2018):

# dmesg -t | grep ^DMI:
DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS L4.81 08/16/2018

# dmesg | grep -A5 'efifb: probing for efifb'
[ 0.813333] efifb: probing for efifb
[ 0.813342] efifb: framebuffer at 0xe0000000, using 19456k, total 19456k
[ 0.813344] efifb: mode is 3440x1440x32, linelength=13824, pages=1
[ 0.813345] efifb: scrolling: redraw
[ 0.813347] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.820746] Console: switching to colour frame buffer device 430x90

Revision history for this message
Tom Reynolds (tomreyn) wrote :

# cat /proc/version
Linux version 4.15.0-34-generic (buildd@lgw01-amd64-047) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018

# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/vg-slash ro

Before the BIOS upgrade, the same kernel version and cmdline still produced the above error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.