Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34691 - [linux] 3.8.x - 3.11.x Device 'efifb.0' does not have a release() function

Attached to Project: Arch Linux
Opened by Erich Luckerbauer (moleculecolony) - Monday, 08 April 2013, 23:27 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 07 October 2013, 10:52 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Error message on every boot.

Additional info:
* package version(s)
linux 3.8.6-1, but was there in earlier versions, too
* config and/or log files etc.
efifb: invalid framebuffer address
------------[ cut here ]------------
WARNING: at drivers/base/core.c:228 device_release+0x92/0xa0()
Hardware name:
Device 'efifb.0' does not have a release() function, it is broken and must be fixed.
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.8.6-1-ARCH #1
Call Trace:
[<ffffffff81347e02>] ? device_release+0x92/0xa0
[<ffffffff81057190>] warn_slowpath_common+0x70/0xa0
[<ffffffff8105720c>] warn_slowpath_fmt+0x4c/0x50
[<ffffffff81347e02>] device_release+0x92/0xa0
[<ffffffff8126b37e>] kobject_release+0x7e/0x1b0
[<ffffffff818ffa7a>] ? efifb_probe+0x4a8/0x4a8
[<ffffffff8126b4d8>] kobject_put+0x28/0x60
[<ffffffff81348147>] put_device+0x17/0x20
[<ffffffff8134e7f0>] platform_device_unregister+0x20/0x30
[<ffffffff818ffcfb>] efifb_init+0x281/0x28a
[<ffffffff818ffa7a>] ? efifb_probe+0x4a8/0x4a8
[<ffffffff8100210a>] do_one_initcall+0x10a/0x160
[<ffffffff818d0d9f>] kernel_init_freeable+0x15b/0x1d7
[<ffffffff818d060a>] ? do_early_param+0x88/0x88
[<ffffffff814a2e50>] ? rest_init+0x90/0x90
[<ffffffff814a2e5e>] kernel_init+0xe/0x190
[<ffffffff814c72ac>] ret_from_fork+0x7c/0xb0
[<ffffffff814a2e50>] ? rest_init+0x90/0x90
---[ end trace b8b439fa7c92f6b9 ]---


Steps to reproduce:
Check for red lines in journalctl -b

Not much found when googling the error message, only this one was interesting:

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840621

They said we should report it to you guys here, which I did.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 07 October 2013, 10:52 GMT
Reason for closing:  Upstream
Comment by Tobias Powalowski (tpowa) - Tuesday, 09 April 2013, 09:48 GMT
http://www.mjmwired.net/kernel/Documentation/fb/efifb.txt
You need to tell on kernel commandline which pc you own.
Comment by Tobias Powalowski (tpowa) - Tuesday, 09 April 2013, 09:51 GMT
Also please report this on upstream kernel tracker I cannot do anything for you.
Comment by Erich Luckerbauer (moleculecolony) - Tuesday, 09 April 2013, 11:41 GMT
I'm not on a Mac.

I guess something is wrong either in the installation process or with the default kernel parameters. (My installation was with the version of March last year.)

Setting the kernel parameter vga=normal solved it. The message changed to this one:

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

More info can be found in /usr/src/linux-3.8.6-1-ARCH/Documentation/fb/modedb.txt (the file you linked to is there also).

Comment by Erich Luckerbauer (moleculecolony) - Thursday, 11 April 2013, 08:07 GMT
Found out that the problem was something else. It depends on the keyboard being available at boot. When I enable USB optimization in the BIOS, meaning that USB is not available until loaded by the kernel, I get this error message.

So yes, maybe should be reported to the kernel guys.
Comment by Tobias Powalowski (tpowa) - Thursday, 23 May 2013, 20:03 GMT
Status on 3.9?
Comment by Erich Luckerbauer (moleculecolony) - Thursday, 23 May 2013, 20:35 GMT
The same with 3.9.3-1. Didn't find the time to report it on kernel tracker so far...
Comment by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:03 GMT
Status on 3.10.x?
Comment by Erich Luckerbauer (moleculecolony) - Wednesday, 31 July 2013, 07:26 GMT
Still unchanged.
Comment by Tobias Powalowski (tpowa) - Tuesday, 17 September 2013, 09:59 GMT
Status on 3.11.1?
Comment by Erich Luckerbauer (moleculecolony) - Wednesday, 18 September 2013, 09:39 GMT
unchanged, error message is slightly different:

Sep 18 11:08:10 mitlDing kernel: efifb: invalid framebuffer address
Sep 18 11:08:10 mitlDing kernel: ------------[ cut here ]------------
Sep 18 11:08:10 mitlDing kernel: WARNING: CPU: 0 PID: 1 at drivers/base/core.c:228 device_release+0x92/0xa0()
Sep 18 11:08:10 mitlDing kernel: Device 'efifb.0' does not have a release() function, it is broken and must be fixed.
Sep 18 11:08:10 mitlDing kernel: Modules linked in:
Sep 18 11:08:10 mitlDing kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.1-1-ARCH #1
Sep 18 11:08:10 mitlDing kernel: Hardware name: /DP55KG, BIOS KGIBX10J.86A.5936.2011.0630.2250 06/30/2011
Sep 18 11:08:10 mitlDing kernel: 0000000000000009 ffff880119aa3d30 ffffffff814da65d ffff880119aa3d78
Sep 18 11:08:10 mitlDing kernel: ffff880119aa3d68 ffffffff8106189d ffffffff8187d600 ffffffff8187d5f0
Sep 18 11:08:10 mitlDing kernel: ffff880118ae1840 ffffffff8187d600 0000000000000000 ffff880119aa3dc8
Sep 18 11:08:10 mitlDing kernel: Call Trace:
Sep 18 11:08:10 mitlDing kernel: [<ffffffff814da65d>] dump_stack+0x54/0x8d
Sep 18 11:08:10 mitlDing kernel: [<ffffffff8106189d>] warn_slowpath_common+0x7d/0xa0
Sep 18 11:08:10 mitlDing kernel: [<ffffffff8106190c>] warn_slowpath_fmt+0x4c/0x50
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81211fa8>] ? release_sysfs_dirent+0x78/0x120
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81372e92>] device_release+0x92/0xa0
Sep 18 11:08:10 mitlDing kernel: [<ffffffff8128770e>] kobject_release+0x7e/0x1b0
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81918286>] ? efifb_probe+0x498/0x498
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81287868>] kobject_put+0x28/0x60
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81373237>] put_device+0x17/0x20
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81379da0>] platform_device_unregister+0x20/0x30
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81918507>] efifb_init+0x281/0x28a
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81918286>] ? efifb_probe+0x498/0x498
Sep 18 11:08:10 mitlDing kernel: [<ffffffff810020fa>] do_one_initcall+0xfa/0x1b0
Sep 18 11:08:10 mitlDing kernel: [<ffffffff81081995>] ? parse_args+0x225/0x400
Sep 18 11:08:10 mitlDing kernel: [<ffffffff818df067>] kernel_init_freeable+0x15a/0x1db
Sep 18 11:08:10 mitlDing kernel: [<ffffffff818de89a>] ? do_early_param+0x88/0x88
Sep 18 11:08:10 mitlDing kernel: [<ffffffff814ccf40>] ? rest_init+0x90/0x90
Sep 18 11:08:10 mitlDing kernel: [<ffffffff814ccf4e>] kernel_init+0xe/0x190
Sep 18 11:08:10 mitlDing kernel: [<ffffffff814e912c>] ret_from_fork+0x7c/0xb0
Sep 18 11:08:10 mitlDing kernel: [<ffffffff814ccf40>] ? rest_init+0x90/0x90
Sep 18 11:08:10 mitlDing kernel: ---[ end trace 16e8dd66dd8c1b36 ]---

Loading...