panic in i915

[Mike Brookes]

Linux myhost 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC 2016 i686 i686 i686 GNU/Linux

syslog:
Nov 5 21:15:45 myhost kernel: [ 53.532149] ------------[ cut here ]------------
Nov 5 21:15:45 myhost kernel: [ 53.532252] WARNING: CPU: 0 PID: 369 at /build/linux-LfgES4/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12744 intel_modeset_check_state+0x556/0x910 [i915]()
Nov 5 21:15:45 myhost kernel: [ 53.532257] encoder's enabled state mismatch (expected 0, found 1)
Nov 5 21:15:45 myhost kernel: [ 53.532261] Modules linked in: xt_tcpudp xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel ppdev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi ax88179_178a lpc_ich serio_raw snd_seq usbnet snd_seq_device snd_timer snd shpchp soundcore parport_pc 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 ahci psmouse r8169 libahci i2c_algo_bit drm_kms_helper pata_acpi syscopyarea sysfillrect sysimgblt fb_sys_fops drm mii fjes video
Nov 5 21:15:45 myhost kernel: [ 53.532402] CPU: 0 PID: 369 Comm: kworker/0:2 Tainted: G W 4.4.0-45-generic #66-Ubuntu
Nov 5 21:15:45 myhost kernel: [ 53.532406] Hardware name: /D945GSEJT , BIOS JT94510H.86A.0025.2009.0306.1639 03/06/2009
Nov 5 21:15:45 myhost kernel: [ 53.532432] Workqueue: events output_poll_execute [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.532438] c1acf967 c1e2b340 00000286 f15d1d20 c13a745f f15d1d60 f89d68b8 f15d1d50
Nov 5 21:15:45 myhost kernel: [ 53.532451] c1070307 f89d89c8 f15d1d80 00000171 f89d68b8 000031c8 f896b696 f896b696
Nov 5 21:15:45 myhost kernel: [ 53.532463] f58bc5d8 f5b6ea80 f58bc5e4 f15d1d6c c107037e 00000009 f15d1d60 f89d89c8
Nov 5 21:15:45 myhost kernel: [ 53.532475] Call Trace:
Nov 5 21:15:45 myhost kernel: [ 53.532488] [<c13a745f>] dump_stack+0x58/0x79
Nov 5 21:15:45 myhost kernel: [ 53.532498] [<c1070307>] warn_slowpath_common+0x87/0xc0
Nov 5 21:15:45 myhost kernel: [ 53.532585] [<f896b696>] ? intel_modeset_check_state+0x556/0x910 [i915]
Nov 5 21:15:45 myhost kernel: [ 53.532667] [<f896b696>] ? intel_modeset_check_state+0x556/0x910 [i915]
Nov 5 21:15:45 myhost kernel: [ 53.532674] [<c107037e>] warn_slowpath_fmt+0x3e/0x60
Nov 5 21:15:45 myhost kernel: [ 53.532757] [<f896b696>] intel_modeset_check_state+0x556/0x910 [i915]
Nov 5 21:15:45 myhost kernel: [ 53.532841] [<f897711d>] intel_atomic_commit+0x4cd/0x6a0 [i915]
Nov 5 21:15:45 myhost kernel: [ 53.532894] [<f875148e>] ? drm_atomic_check_only+0x1ae/0x600 [drm]
Nov 5 21:15:45 myhost kernel: [ 53.532943] [<f8750129>] ? drm_modeset_lock+0x49/0xd0 [drm]
Nov 5 21:15:45 myhost kernel: [ 53.532994] [<f8751912>] drm_atomic_commit+0x32/0x60 [drm]
Nov 5 21:15:45 myhost kernel: [ 53.533020] [<f85e3653>] restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533070] [<f8750244>] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
Nov 5 21:15:45 myhost kernel: [ 53.533096] [<f85e56a7>] drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533121] [<f85e571d>] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533146] [<f85e562c>] drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533229] [<f898c9ba>] intel_fbdev_output_poll_changed+0x1a/0x20 [i915]
Nov 5 21:15:45 myhost kernel: [ 53.533252] [<f85d86b1>] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533276] [<f85d88a8>] output_poll_execute+0x188/0x1c0 [drm_kms_helper]
Nov 5 21:15:45 myhost kernel: [ 53.533285] [<c1087751>] process_one_work+0x121/0x3f0
Nov 5 21:15:45 myhost kernel: [ 53.533292] [<c1087c2a>] worker_thread+0x20a/0x490
Nov 5 21:15:45 myhost kernel: [ 53.533300] [<c1087a20>] ? process_one_work+0x3f0/0x3f0
Nov 5 21:15:45 myhost kernel: [ 53.533306] [<c108cf06>] kthread+0xa6/0xc0
Nov 5 21:15:45 myhost kernel: [ 53.533315] [<c17b3349>] ret_from_kernel_thread+0x21/0x38
Nov 5 21:15:45 myhost kernel: [ 53.533321] [<c108ce60>] ? kthread_create_on_node+0x170/0x170
Nov 5 21:15:45 myhost kernel: [ 53.533327] ---[ end trace 361aeae89ccf24ea ]---

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1639506/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1639506

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc4

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]