Bug 1335330

Summary: [abrt] WARNING: CPU: 1 PID: 1 at drivers/video/fbdev/core/fb_draw.h:45 cfb_fillrect+0x25f/0x350()
Product: [Fedora] Fedora Reporter: Ricardo Ramos <delacosta610>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/39e4feb835d52d45d39e168c8013320a1171b68e
Whiteboard: abrt_hash:4a2babfcd738d1d6c45183a32d31a62cb0a3db88;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-03 22:22:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Ricardo Ramos 2016-05-12 00:10:14 UTC 
Description of problem:
It always happens at boot, just when the system completes loading up the live image.

Additional info:
reporter:       libreport-2.7.0
WARNING: CPU: 1 PID: 1 at drivers/video/fbdev/core/fb_draw.h:45 cfb_fillrect+0x25f/0x350()
pixel_to_pat(): unsupported pixelformat 15
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.5.2-302.fc24.x86_64 #1
Hardware name: Hewlett-Packard G1-2112la/2ABA, BIOS ANP_712 07/15/2011
 0000000000000286 0000000061b64cd6 ffff8800640af7b0 ffffffff813d43bf
 ffff8800640af7f8 ffffffff81ad6018 ffff8800640af7e8 ffffffff810a5e22
 ffff880064164000 0000000000000320 0000000000000000 000000000000000f
Call Trace:
 [<ffffffff813d43bf>] dump_stack+0x63/0x84
 [<ffffffff810a5e22>] warn_slowpath_common+0x82/0xc0
 [<ffffffff810a5ebc>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffff8145456f>] cfb_fillrect+0x25f/0x350
 [<ffffffff81451375>] ? fb_copy_cmap+0x95/0xf0
 [<ffffffff81448304>] bit_clear_margins+0x94/0xf0
 [<ffffffff814417e6>] fbcon_clear_margins+0x66/0x90
 [<ffffffff81445498>] fbcon_switch+0x3b8/0x630
 [<ffffffff814ce32a>] redraw_screen+0x17a/0x250
 [<ffffffff814cf0cb>] do_bind_con_driver+0x2eb/0x3d0
 [<ffffffff814cf509>] do_take_over_console+0x159/0x1c0
 [<ffffffff8144344c>] do_fbcon_takeover+0x5c/0xb0
 [<ffffffff814480e5>] fbcon_event_notify+0x685/0x790
 [<ffffffff810c5829>] notifier_call_chain+0x49/0x70
 [<ffffffff810c5b67>] __blocking_notifier_call_chain+0x47/0x60
 [<ffffffff810c5b96>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff8144df5b>] fb_notifier_call_chain+0x1b/0x20
 [<ffffffff814500f6>] register_framebuffer+0x216/0x360
 [<ffffffff81459721>] efifb_probe+0x6c1/0x740
 [<ffffffff81516d9b>] platform_drv_probe+0x3b/0xa0
 [<ffffffff81510c40>] ? devices_kset_move_last+0x50/0x90
 [<ffffffff81514c2c>] driver_probe_device+0x22c/0x440
 [<ffffffff81514ec4>] __driver_attach+0x84/0x90
 [<ffffffff81514e40>] ? driver_probe_device+0x440/0x440
 [<ffffffff8151253c>] bus_for_each_dev+0x6c/0xc0
 [<ffffffff8151431e>] driver_attach+0x1e/0x20
 [<ffffffff81513d63>] bus_add_driver+0x1c3/0x280
 [<ffffffff81db086d>] ? vesafb_driver_init+0x14/0x14
 [<ffffffff81515790>] driver_register+0x60/0xe0
 [<ffffffff81516d16>] __platform_driver_register+0x36/0x40
 [<ffffffff81db087f>] efifb_driver_init+0x12/0x14
 [<ffffffff81002123>] do_one_initcall+0xb3/0x1f0
 [<ffffffff81d688ed>] ? initcall_blacklist+0xbe/0xbe
 [<ffffffff81d691f2>] kernel_init_freeable+0x18f/0x22b
 [<ffffffff817c3680>] ? rest_init+0x80/0x80
 [<ffffffff817c368e>] kernel_init+0xe/0xe0
 [<ffffffff817d0abf>] ret_from_fork+0x3f/0x70
 [<ffffffff817c3680>] ? rest_init+0x80/0x80

Potential duplicate: bug 1265817
Comment 1 Ricardo Ramos 2016-05-12 00:10:25 UTC 
Created attachment 1156341 [details]
File: dmesg
Comment 2 Ricardo Ramos 2016-07-03 19:54:45 UTC 
I thought this issue was fixed after I updated the BIOS firmware but now I see is back again...
Comment 3 Ricardo Ramos 2016-07-30 15:51:49 UTC 
I found out it happens when the live image boots in UEFI mode whether on CD/DVD or USB, on legacy mode it boots with no error messages.
Comment 4 Ricardo Ramos 2016-09-03 22:22:29 UTC 
I will report this bug on every fedora alpha release until it gets fixed.

*** This bug has been marked as a duplicate of bug 1371606 ***