Bug 1371606

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 WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: delacosta610, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4fd02e913adfb2df6eedbd4381e3c2ed2b660d98
Whiteboard: abrt_hash:7bf16a0cae23e6c3213bcee45e7c4a0b687b0411;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-06 03:13:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Ricardo Ramos 2016-08-30 15:38:54 UTC 
Description of problem:
It happens always on this computer when booting a Fedora live image in UEFI mode.

Additional info:
reporter:       libreport-2.7.2
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.8.0-0.rc2.git3.1.fc25.x86_64 #1
Hardware name: Hewlett-Packard G1-2112la/2ABA, BIOS ANP_712 07/15/2011
 0000000000000286 0000000009745a4b ffff9fbfe40b7760 ffffffff8b467eb3
 ffff9fbfe40b77b0 0000000000000000 ffff9fbfe40b77a0 ffffffff8b0ae6db
 0000002de40b7838 ffff9fbfbd3bf800 0000000000000320 0000000000000000
Call Trace:
 [<ffffffff8b467eb3>] dump_stack+0x86/0xc3
 [<ffffffff8b0ae6db>] __warn+0xcb/0xf0
 [<ffffffff8b0ae75f>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffff8b4f7baf>] cfb_fillrect+0x25f/0x350
 [<ffffffff8b4f4795>] ? fb_copy_cmap+0x95/0xf0
 [<ffffffff8b4eb35d>] bit_clear_margins+0x9d/0xf0
 [<ffffffff8b4e47d3>] fbcon_clear_margins+0x63/0x80
 [<ffffffff8b4e81d3>] fbcon_switch+0x3c3/0x640
 [<ffffffff8b58a8ef>] redraw_screen+0x16f/0x250
 [<ffffffff8b58b6bd>] do_bind_con_driver+0x2ed/0x3d0
 [<ffffffff8b58bad6>] do_take_over_console+0x116/0x180
 [<ffffffff8b4e611c>] do_fbcon_takeover+0x5c/0xb0
 [<ffffffff8b4eb141>] fbcon_event_notify+0x6b1/0x7b0
 [<ffffffff8b12df4d>] ? debug_lockdep_rcu_enabled+0x1d/0x20
 [<ffffffff8b0d7859>] notifier_call_chain+0x39/0xa0
 [<ffffffff8b0d7a4d>] __blocking_notifier_call_chain+0x4d/0x70
 [<ffffffff8b0d7a86>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff8b4f10eb>] fb_notifier_call_chain+0x1b/0x20
 [<ffffffff8b4f24d8>] register_framebuffer+0x278/0x360
 [<ffffffff8b4fcdda>] efifb_probe+0x61a/0x670
 [<ffffffff8b5db0cb>] platform_drv_probe+0x3b/0xa0
 [<ffffffff8b5d4acc>] ? devices_kset_move_last+0x5c/0x90
 [<ffffffff8b5d8b93>] driver_probe_device+0x223/0x430
 [<ffffffff8b5d8e83>] __driver_attach+0xe3/0xf0
 [<ffffffff8b5d8da0>] ? driver_probe_device+0x430/0x430
 [<ffffffff8b5d6423>] bus_for_each_dev+0x73/0xc0
 [<ffffffff8b5d826e>] driver_attach+0x1e/0x20
 [<ffffffff8b5d7c73>] bus_add_driver+0x173/0x270
 [<ffffffff8c215709>] ? vesafb_driver_init+0x14/0x14
 [<ffffffff8c1c78cd>] ? set_debug_rodata+0x12/0x12
 [<ffffffff8b5d9ae0>] driver_register+0x60/0xe0
 [<ffffffff8c215709>] ? vesafb_driver_init+0x14/0x14
 [<ffffffff8b5db046>] __platform_driver_register+0x36/0x40
 [<ffffffff8c21571b>] efifb_driver_init+0x12/0x14
 [<ffffffff8b002190>] do_one_initcall+0x50/0x180
 [<ffffffff8c1c78cd>] ? set_debug_rodata+0x12/0x12
 [<ffffffff8c1c823b>] kernel_init_freeable+0x200/0x29c
 [<ffffffff8b8e8eae>] kernel_init+0xe/0x100
 [<ffffffff8b8f9e6f>] ret_from_fork+0x1f/0x40
 [<ffffffff8b8e8ea0>] ? rest_init+0x140/0x140
Comment 1 Ricardo Ramos 2016-08-30 15:39:08 UTC 
Created attachment 1195981 [details]
File: dmesg
Comment 2 Ricardo Ramos 2016-09-03 22:22:29 UTC 
*** Bug 1335330 has been marked as a duplicate of this bug. ***
Comment 3 Laura Abbott 2017-01-17 01:20:37 UTC 
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.
Comment 4 Ricardo Ramos 2017-01-17 16:19:17 UTC 
(In reply to Laura Abbott from comment #3)
> *********** MASS BUG UPDATE **************
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 25 kernel bugs.
>  
> Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
>  
> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.
>  
> If you experience different issues, please open a new bug report for those.

Hello, I'm unable to test the issue with the kernel you mention because the computer where I reported this bug is running windows and it's not possible to install fedora right now so instead I used the latest re-spin that comes with kernel 4.8.16.-300.fc25, so I run the live ISO with an USB and the issue still persist, I suppose it will be the same with the latest kernel, this bug has been around for a few years now and I've been reporting this with every new fedora release.
Comment 5 Ricardo Ramos 2017-01-26 04:26:00 UTC 
(In reply to Laura Abbott from comment #3)
> *********** MASS BUG UPDATE **************
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 25 kernel bugs.
>  
> Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
>  
> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.
>  
> If you experience different issues, please open a new bug report for those.

I tested the kernel 4.9.4-201.fc25 and the bug is still present.
Comment 6 Justin M. Forbes 2017-04-11 14:51:09 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 7 Ricardo Ramos 2017-04-13 17:52:53 UTC 
(In reply to Justin M. Forbes from comment #6)
> *********** MASS BUG UPDATE **************
> Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.

It's still present.

> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.

I haven't moved to Fedora 26 but I tested the new alpha release and was unable to check if the bug is still present because problem report (gnome-abrt) didn't ship with it so I'm going to wait for the beta release.
Comment 8 Ricardo Ramos 2017-06-13 17:22:22 UTC 
(In reply to Justin M. Forbes from comment #6)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 25 kernel bugs.
> 
> Fedora 25 has now been rebased to 4.10.9-200.fc25.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
> 
> If you have moved on to Fedora 26, and are still experiencing this issue,
> please change the version to Fedora 26.
> 
> If you experience different issues, please open a new bug report for those.

This bug is still present in Fedora 26 Beta, switching...
Comment 9 Ricardo Ramos 2017-10-04 00:11:18 UTC 
This bug is still present on Fedora 27 Beta, switching...
Comment 10 Laura Abbott 2018-02-20 19:54:33 UTC 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.
Comment 11 Ricardo Ramos 2018-03-06 03:13:15 UTC 
I can't test this anymore, the computer where this bug was present has been sold.

Thank you.