Bug 59151 - Device 'efifb.0' does not have a release() function, it is broken and must be fixed.
Summary: Device 'efifb.0' does not have a release() function, it is broken and must be...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers (show other bugs)
Hardware: All Linux
: P1 low
Assignee: James Simmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-31 15:31 UTC by Erich Luckerbauer
Modified: 2024-10-15 08:56 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.9.4-1
Subsystem:
Regression: No
Bisected commit-id:

Attachments
lspci -vvnn ++ dmidecode (33.36 KB, application/octet-stream)
2013-05-31 15:31 UTC, Erich Luckerbauer 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Erich Luckerbauer 2013-05-31 15:31:48 UTC 
Created attachment 103121 [details]
lspci -vvnn ++ dmidecode

This error message appears on every boot, without causing noticeable problems. I found out that it has to do with having USB optimization enabled/disabled in the BIOS. When it's enabled, that is, USB is not being made available during POST, I get this error message, otherwise not.

Board: Intel DP55KG

Mai 31 16:53:04 mitlDing kernel: efifb: invalid framebuffer address
Mai 31 16:53:04 mitlDing kernel: ------------[ cut here ]------------
Mai 31 16:53:04 mitlDing kernel: WARNING: at drivers/base/core.c:228 device_release+0x92/0xa0()
Mai 31 16:53:04 mitlDing kernel: Hardware name:         
Mai 31 16:53:04 mitlDing kernel: Device 'efifb.0' does not have a release() function, it is broken and must be fixed.
Mai 31 16:53:04 mitlDing kernel: Modules linked in:
Mai 31 16:53:04 mitlDing kernel: Pid: 1, comm: swapper/0 Not tainted 3.9.4-1-ARCH #1
Mai 31 16:53:04 mitlDing kernel: Call Trace:
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81352d62>] ? device_release+0x92/0xa0
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff810580b0>] warn_slowpath_common+0x70/0xa0
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff8105812c>] warn_slowpath_fmt+0x4c/0x50
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81352d62>] device_release+0x92/0xa0
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81271c7e>] kobject_release+0x7e/0x1b0
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81904f43>] ? efifb_probe+0x4a8/0x4a8
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81271dd8>] kobject_put+0x28/0x60
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff813530a7>] put_device+0x17/0x20
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81359740>] platform_device_unregister+0x20/0x30
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff819051c4>] efifb_init+0x281/0x28a
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff81904f43>] ? efifb_probe+0x4a8/0x4a8
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff8100210a>] do_one_initcall+0x10a/0x160
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff818d5037>] kernel_init_freeable+0x15b/0x1dc
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff818d4881>] ? do_early_param+0x88/0x88
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff814b43b0>] ? rest_init+0x90/0x90
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff814b43be>] kernel_init+0xe/0x190
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff814d9dec>] ret_from_fork+0x7c/0xb0
Mai 31 16:53:04 mitlDing kernel:  [<ffffffff814b43b0>] ? rest_init+0x90/0x90
Mai 31 16:53:04 mitlDing kernel: ---[ end trace 88282399491fd3ea ]---

With USB optimization disabled it looks like this:

efifb: probing for efifb
 efifb: framebuffer at 0xe0000000, mapped to 0xffffc90000780000, using 1876k, total 1875k
 efifb: mode is 800x600x32, linelength=3200, pages=1
 efifb: scrolling: redraw
 efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0

Telling on kernel commandline to use another framebuffer or simply vga doesn't help.

uname -r
3.9.4-1-ARCH

Outputs of lspci -vvnn and dmidecode are added.
Note You need to log in before you can comment on or make changes to this bug.