A few weeks of bisecting: commit eddfcbcdc27fbecb33bff098967bbdd7ca75bfa6 Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Date: Mon Jun 15 12:33:53 2015 +0200 drm/i915: Update less state during modeset. No need to repeatedly call update_watermarks, or update_fbc. Down to a single call to update_watermarks in .crtc_enable Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by: Matt Roper <matthew.d.roper@intel.com> Tested-by(IVB): Matt Roper <matthew.d.roper@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
I presume it is an oops, but it locks the machine up hard.
Got it at last with the usual trick of killing fbcon/fbdev: [ 548.535895] [drm] Initialized i915 1.6.0 20150619 for 0000:00:02.0 on minor 0 [ 548.604106] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2 [ 548.996278] ------------[ cut here ]------------ [ 548.996289] kernel BUG at drivers/gpu/drm/i915/intel_display.c:1947! [ 548.996295] invalid opcode: 0000 [#1] SMP [ 548.996301] Modules linked in: i915(E) ctr ccm input_polldev bnep rfcomm arc4 ath9k ath9k_common ath9k_hw uvcvideo ath videobuf2_vmalloc mac80211 videobuf2_memops videobuf2_core snd_hda_codec_conexant v4l2_common snd_hda_codec_generic videodev dell_wmi snd_hda_intel gpio_ich sparse_keymap snd_hda_controller snd_hda_codec hid_multitouch snd_hda_core dell_laptop snd_hwdep dcdbas btusb snd_pcm i8k btbcm btintel snd_seq_midi bluetooth snd_seq_midi_event coretemp snd_rawmidi cfg80211 snd_seq snd_seq_device microcode joydev snd_timer serio_raw snd wmi drm_kms_helper soundcore shpchp lpc_ich usbhid hid psmouse ahci libahci [ 548.996382] CPU: 1 PID: 1134 Comm: Xorg Tainted: G W E 4.1.0-rc6+ #217 [ 548.996386] Hardware name: Dell Inc. Inspiron 1090/Inspiron 1090, BIOS A06 08/23/2011 [ 548.996392] task: f0fcd2e0 ti: efe26000 task.ti: efe26000 [ 548.996398] EIP: 0060:[<f8bd15ef>] EFLAGS: 00213297 CPU: 1 [ 548.996462] EIP is at __intel_set_mode+0x71f/0x750 [i915] [ 548.996467] EAX: f5998000 EBX: f5aee000 ECX: f5998000 EDX: 00203296 [ 548.996472] ESI: eff53000 EDI: 00000001 EBP: efe27da0 ESP: efe27d4c [ 548.996477] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 548.996482] CR0: 80050033 CR2: bf8e8d10 CR3: 30e1a020 CR4: 000007f0 [ 548.996486] Stack: [ 548.996489] e6b51580 e6b51580 00000000 efe27d84 c1413071 efe27d78 efe27d84 c1413eed [ 548.996502] f5aee000 f5998000 f0192800 f0192800 f5998000 f5413c00 eff53000 f8bc25e9 [ 548.996513] f5aee000 f0192800 f0192800 eff53000 efe27e24 efe27de0 f8bd7bb4 00000000 [ 548.996525] Call Trace: [ 548.996539] [<c1413071>] ? drm_atomic_set_crtc_for_plane+0x41/0x100 [ 548.996547] [<c1413eed>] ? drm_atomic_set_fb_for_plane+0x1d/0x90 [ 548.996604] [<f8bc25e9>] ? intel_modeset_setup_plane_state+0x59/0xc0 [i915] [ 548.996663] [<f8bd7bb4>] intel_crtc_set_config+0x294/0x550 [i915] [ 548.996673] [<c1619b30>] ? mutex_lock+0x10/0x28 [ 548.996681] [<c140472e>] drm_mode_set_config_internal+0x4e/0xc0 [ 548.996688] [<c14085e2>] drm_mode_setcrtc+0x3f2/0x540 [ 548.996697] [<c12c2edd>] ? apparmor_capable+0x1d/0x50 [ 548.996704] [<c14081f0>] ? drm_mode_setplane+0x1b0/0x1b0 [ 548.996711] [<c13fa372>] drm_ioctl+0x2e2/0x530 [ 548.996719] [<c1120117>] ? __generic_file_write_iter+0x177/0x1b0 [ 548.996725] [<c14081f0>] ? drm_mode_setplane+0x1b0/0x1b0 [ 548.996735] [<c11ab292>] ? fsnotify+0x272/0x360 [ 548.996742] [<c13fa090>] ? drm_getmap+0xb0/0xb0 [ 548.996750] [<c11856ea>] do_vfs_ioctl+0x30a/0x530 [ 548.996758] [<c1176531>] ? __sb_end_write+0x31/0x70 [ 548.996765] [<c1174b38>] ? vfs_write+0x158/0x1a0 [ 548.996772] [<c118dc52>] ? __fget_light+0x22/0x60 [ 548.996779] [<c1185970>] SyS_ioctl+0x60/0x90 [ 548.996786] [<c161be08>] sysenter_do_call+0x12/0x12 [ 548.996790] Code: 08 4b 56 c3 f8 c7 44 24 04 ac 07 00 00 c7 04 24 80 84 c2 f8 e8 a3 9f 47 c8 e9 4c fa ff ff 8b 45 dc 80 78 1a 04 0f 87 41 f9 ff ff <0f> 0b c7 44 24 08 d8 b3 c2 f8 c7 44 24 04 72 30 00 00 c7 04 24 [ 548.996861] EIP: [<f8bd15ef>] __intel_set_mode+0x71f/0x750 [i915] SS:ESP 0068:efe27d4c [ 548.996924] ---[ end trace 95c346afe1be8257 ]---
Does this still occur in v4.3? Seems the offending function should be gone..
Or well depends, I think the regressions from this bug are fixed at least.
Let's presume it died with the function removal.
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.