Created attachment 128307 [details] Full dmesg of kernel with backtraces Kernel: kernel-PAE-core-4.8.10-300.fc25.i686 Machine: Acer Aspire One ZG5 Video outputs: one LCD display 1024x600, one VGA port with no monitor attached. 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 015b Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 58480000 (32-bit, non-prefetchable) [size=512K] I/O ports at 60c0 [size=8] Memory at 40000000 (32-bit, prefetchable) [size=256M] Memory at 58500000 (32-bit, non-prefetchable) [size=256K] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 Every single time the kernel boots, I get three WARN_ON messages in the dmesg log: [ 4.757645] ------------[ cut here ]------------ [ 4.757817] WARNING: CPU: 0 PID: 89 at drivers/gpu/drm/i915/intel_fbdev.c:416 intel_fb_initial_config+0x366/0x680 [i915] [ 4.757821] WARN_ON(!connector->state->crtc) [ 4.757824] Modules linked in: [ 4.757827] i915 ata_generic serio_raw i2c_algo_bit drm_kms_helper pata_acpi drm r8169 mii fjes video [ 4.757856] CPU: 0 PID: 89 Comm: kworker/u4:2 Not tainted 4.8.10-300.fc25.i686+PAE #1 [ 4.757859] Hardware name: Acer AOA150/ , BIOS v0.3301 05/09/2008 [ 4.757869] Workqueue: events_unbound async_run_entry_fn [ 4.757875] ce63a967 5cca08e8 00000286 f49b5d18 cdf5ccd0 f49b5d5c f864b748 f49b5d48 [ 4.757891] cdc6c0aa f8657bef f49b5d7c 00000059 f864b748 000001a0 f85f61d6 000001a0 [ 4.757905] 00000001 00000000 f4b3c800 f49b5d68 cdc6c116 00000009 00000000 f49b5d5c [ 4.757920] Call Trace: [ 4.757933] [<cdf5ccd0>] dump_stack+0x58/0x78 [ 4.757941] [<cdc6c0aa>] __warn+0xea/0x110 [ 4.758018] [<f85f61d6>] ? intel_fb_initial_config+0x366/0x680 [i915] [ 4.758018] [<cdc6c116>] warn_slowpath_fmt+0x46/0x60 [ 4.758018] [<f85f61d6>] intel_fb_initial_config+0x366/0x680 [i915] [ 4.758018] [<f85f5e70>] ? intelfb_create+0x540/0x540 [i915] [ 4.758018] [<f80c54d3>] drm_setup_crtcs+0x1c3/0xa40 [drm_kms_helper] [ 4.758018] [<cdc9302f>] ? ttwu_do_activate+0x5f/0x70 [ 4.758018] [<cdc939e4>] ? try_to_wake_up+0x44/0x340
I've got the same issue on a HP Mini 110 running kernel 4.9.0-2-686-pae (Debian Stretch). kernel: 4.9.0-2-686-pae #1 SMP Debian 4.9.13-1 (2017-02-27) i686 GNU/Linux ----------- 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fe980000 (32-bit, non-prefetchable) [size=512K] I/O ports at dc80 [size=8] Memory at d0000000 (32-bit, prefetchable) [size=256M] Memory at fe940000 (32-bit, non-prefetchable) [size=256K] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller Flags: bus master, fast devsel, latency 0 Memory at fe880000 (32-bit, non-prefetchable) [size=512K] Capabilities: <access denied> ----------- WARNING: CPU: 1 PID: 6 at /build/linux-GCI9oD/linux-4.9.13/drivers/gpu/drm/i915/i WARN_ON(!connector->state->crtc) Modules linked in: mac80211 snd_hda_codec_idt i915 snd_hda_codec_generic pcspkr snd_hda_intel joyde CPU: 1 PID: 6 Comm: kworker/u4:0 Not tainted 4.9.0-2-686-pae #1 Debian 4.9.13-1 Hardware name: Hewlett-Packard HP Mini 110-1000/308F, BIOS 308F0 Ver. F.19 01/12/ Workqueue: events_unbound async_run_entry_fn f7517d44 cf2f0f52 f7517d58 00000000 cf066b2a f8e76a6b f7517d78 00000006 f8e6a048 0000019e f8e1a3fc 0000019e 00000009 f8e1a3fc 00000001 f768f000 00000000 f7517d64 cf066b96 00000009 00000000 f7517d58 f8e76a6b f7517d78 Call Trace: [<cf2f0f52>] ? dump_stack+0x55/0x73 [<cf066b2a>] ? __warn+0xea/0x110 [<f8e1a3fc>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915] [<f8e1a3fc>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915] [<cf066b96>] ? warn_slowpath_fmt+0x46/0x60 [<f8e1a3fc>] ? intel_fb_initial_config+0x3fc/0x5f0 [i915] [<cf1bbe70>] ? __kmalloc+0xc0/0x4f0 [<f8dd7c10>] ? gen2_write16+0x120/0x120 [i915] [<f8e1a000>] ? intelfb_create+0x4d0/0x4d0 [i915] [<f8aa85b3>] ? drm_setup_crtcs+0x1a3/0x940 [drm_kms_helper] [<cf08f135>] ? try_to_wake_up+0x45/0x360 [<cf08f49e>] ? wake_up_q+0x2e/0x60 [<f8aa903c>] ? drm_fb_helper_initial_config+0xbc/0x410 [drm_kms_helper] [<cf0a2cf0>] ? pick_next_task_fair+0x490/0x520 [<f8e1abe6>] ? intel_fbdev_initial_config+0x16/0x30 [i915] [<cf086e85>] ? async_run_entry_fn+0x35/0x170 [<cf07eb31>] ? process_one_work+0x141/0x380 [<cf07edb1>] ? worker_thread+0x41/0x460 [<cf07ed70>] ? process_one_work+0x380/0x380 [<cf084057>] ? kthread+0xa7/0xc0 [<cf083fb0>] ? kthread_park+0x50/0x50 [<cf59ec43>] ? ret_from_fork+0x1b/0x28 ---[ end trace 9f2112909399e665 ]---
Hello Alex, Nemo, Sorry for the long delay, is this still valid on latest kernel https://www.kernel.org/? If so, Could you please attach dmesg with drm.debug=0xe parameter on grub please? Thank you.
Created attachment 133064 [details] dmesg under kernel 4.11.11-300.fc26.i686+PAE The backtrace is still present under Fedora 26 with distro kernel kernel-PAE-core-4.11.11-300.fc26.i686 , although the trace is a bit different. I am attaching the one I get with the distro kernel while I get the vanilla kernel to compile on this machine.
(In reply to Alex Villacís Lasso from comment #3) > Created attachment 133064 [details] > dmesg under kernel 4.11.11-300.fc26.i686+PAE > > The backtrace is still present under Fedora 26 with distro kernel > kernel-PAE-core-4.11.11-300.fc26.i686 , although the trace is a bit > different. I am attaching the one I get with the distro kernel while I get > the vanilla kernel to compile on this machine. Thank you Alex, Waiting for Vanilla dmesg for comparing then. On a side note, from dmesg attached it looks quite familiar to this other bug: https://bugs.freedesktop.org/show_bug.cgi?id=101937, though HW and SW are different.
Created attachment 133124 [details] dmesg under 4.12.3 A WARN_ON still appears under 4.12.3. Attached dmesg with drm.debug=0x3 .
Thank you for the update Alex, If more info is needed it will be asked below.
Under 4.13.4 and later the situation is worse. See https://bugs.freedesktop.org/show_bug.cgi?id=103223 .
commit b1e01595a66dc206a2c75401ec4c285740537f3f Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Fri Nov 17 21:19:09 2017 +0200 drm/i915: Redo plane sanitation during readout fixes this, and at least 4.14.20 has the backport now.
Closing, please re-open if still occurs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.