Created attachment 85211 [details] dmesg after reboot I am using the drm-next with git libdrm, mesa, xf86-video* ... Mainly I wanted airlied's nouveau optimus runtime PM patches. I just installed Nexuiz and ran nexuiz-glx with the Intel card (forgot to do DRI_PRIME=1) - it showed some brownish horizontal artifacts/lines and presumably crashed, creating an unkillable process. Here's the lines from dmesg: [ 6619.136216] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags(DRM_MODE_FLAG_PHSYNC) (expected 0, found 1) [ 6619.136236] ------------[ cut here ]------------ [ 6619.136297] WARNING: CPU: 0 PID: 1769 at drivers/gpu/drm/i915/intel_display.c:8746 check_crtc_state+0x5ff/0xac0 [i915]() [ 6619.136300] pipe state doesn't match! [ 6619.136302] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek uvcvideo brcmsmac videobuf2_vmalloc coretemp nouveau videobuf2_memops videobuf2_core kvm_intel cordic brcmutil videodev kvm atl1c bcma ttm usbhid dell_wmi mxm_wmi microcode snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc i915 snd_timer snd wmi drm_kms_helper lpc_ich mfd_core [ 6619.136371] CPU: 0 PID: 1769 Comm: X Not tainted 3.11.0-rc7+ #1 [ 6619.136375] Hardware name: Alienware M11x R2/M11x R2, BIOS A04 11/23/2010 [ 6619.136378] 0000000000000009 ffff88016f59d7c8 ffffffff815bcf24 0000000000000007 [ 6619.136396] ffff88016f59d818 ffff88016f59d808 ffffffff81043cd7 ffff88016f59d810 [ 6619.136402] ffff8801729d7000 ffff8801729d76d0 ffff880172a67418 ffff880172a67000 [ 6619.136408] Call Trace: [ 6619.136431] [<ffffffff815bcf24>] dump_stack+0x4f/0x84 [ 6619.136441] [<ffffffff81043cd7>] warn_slowpath_common+0x87/0xb0 [ 6619.136460] [<ffffffff81043da1>] warn_slowpath_fmt+0x41/0x50 [ 6619.136492] [<ffffffffa006bb1f>] check_crtc_state+0x5ff/0xac0 [i915] [ 6619.136528] [<ffffffffa007883d>] intel_modeset_check_state+0x2ad/0x770 [i915] [ 6619.136559] [<ffffffffa0078d20>] intel_set_mode+0x20/0x30 [i915] [ 6619.136590] [<ffffffffa0079553>] intel_crtc_set_config+0x823/0xa10 [i915] [ 6619.136600] [<ffffffff81333a2d>] drm_mode_set_config_internal+0x5d/0xe0 [ 6619.136607] [<ffffffff81335f93>] drm_mode_setcrtc+0xf3/0x630 [ 6619.136638] [<ffffffffa006e377>] ? intel_crtc_load_lut+0xd7/0x180 [i915] [ 6619.136658] [<ffffffff81326d59>] drm_ioctl+0x539/0x660 [ 6619.136664] [<ffffffff81335ea0>] ? drm_mode_setplane+0x3b0/0x3b0 [ 6619.136672] [<ffffffff8107773a>] ? __dequeue_entity+0x2a/0x50 [ 6619.136693] [<ffffffff8100b4e8>] ? __switch_to_xtra+0x118/0x140 [ 6619.136702] [<ffffffff8114fd57>] do_vfs_ioctl+0x87/0x520 [ 6619.136722] [<ffffffff815c4122>] ? _raw_spin_unlock_irq+0x12/0x40 [ 6619.136730] [<ffffffff8106f679>] ? finish_task_switch+0x49/0xe0 [ 6619.136736] [<ffffffff815c2aa9>] ? __schedule+0x409/0x820 [ 6619.136754] [<ffffffff815c4122>] ? _raw_spin_unlock_irq+0x12/0x40 [ 6619.136761] [<ffffffff81150281>] SyS_ioctl+0x91/0xb0 [ 6619.136769] [<ffffffff815cb692>] system_call_fastpath+0x16/0x1b [ 6619.136786] ---[ end trace 57ca81ad7543212d ]--- [ 6630.833559] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 6636.279723] ACPI Warning: \_SB_.PCI0.P0P2.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 6636.281180] ACPI Warning: \_SB_.PCI0.P0P2.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95) [ 6640.648259] nouveau 0000:01:00.0: power state changed by ACPI to D3cold [ 6727.429277] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags(DRM_MODE_FLAG_PHSYNC) (expected 0, found 1) [ 6727.429282] ------------[ cut here ]------------ [ 6727.429337] WARNING: CPU: 2 PID: 1769 at drivers/gpu/drm/i915/intel_display.c:8746 check_crtc_state+0x5ff/0xac0 [i915]() [ 6727.429339] pipe state doesn't match! [ 6727.429341] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek uvcvideo brcmsmac videobuf2_vmalloc coretemp nouveau videobuf2_memops videobuf2_core kvm_intel cordic brcmutil videodev kvm atl1c bcma ttm usbhid dell_wmi mxm_wmi microcode snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc i915 snd_timer snd wmi drm_kms_helper lpc_ich mfd_core [ 6727.429385] CPU: 2 PID: 1769 Comm: X Tainted: G W 3.11.0-rc7+ #1 [ 6727.429399] Hardware name: Alienware M11x R2/M11x R2, BIOS A04 11/23/2010 [ 6727.429401] 0000000000000009 ffff88016f59d7c8 ffffffff815bcf24 0000000000000007 [ 6727.429405] ffff88016f59d818 ffff88016f59d808 ffffffff81043cd7 ffff88016f59d810 [ 6727.429409] ffff8801729d7000 ffff8801729d76d0 ffff880172a67418 ffff880172a67000 [ 6727.429413] Call Trace: [ 6727.429434] [<ffffffff815bcf24>] dump_stack+0x4f/0x84 [ 6727.429441] [<ffffffff81043cd7>] warn_slowpath_common+0x87/0xb0 [ 6727.429446] [<ffffffff81043da1>] warn_slowpath_fmt+0x41/0x50 [ 6727.429471] [<ffffffffa006bb1f>] check_crtc_state+0x5ff/0xac0 [i915] [ 6727.429500] [<ffffffffa007883d>] intel_modeset_check_state+0x2ad/0x770 [i915] [ 6727.429513] [<ffffffffa0078d20>] intel_set_mode+0x20/0x30 [i915] [ 6727.429537] [<ffffffffa0079553>] intel_crtc_set_config+0x823/0xa10 [i915] [ 6727.429545] [<ffffffff81333a2d>] drm_mode_set_config_internal+0x5d/0xe0 [ 6727.429562] [<ffffffff81335f93>] drm_mode_setcrtc+0xf3/0x630 [ 6727.429575] [<ffffffffa006e377>] ? intel_crtc_load_lut+0xd7/0x180 [i915] [ 6727.429592] [<ffffffff81326d59>] drm_ioctl+0x539/0x660 [ 6727.429599] [<ffffffff8114d9c7>] ? path_openat+0x107/0x630 [ 6727.429602] [<ffffffff81335ea0>] ? drm_mode_setplane+0x3b0/0x3b0 [ 6727.429608] [<ffffffff8114fd57>] do_vfs_ioctl+0x87/0x520 [ 6727.429626] [<ffffffff811408b0>] ? __sb_end_write+0x30/0x70 [ 6727.429631] [<ffffffff8113ec36>] ? vfs_write+0x186/0x200 [ 6727.429635] [<ffffffff81150281>] SyS_ioctl+0x91/0xb0 [ 6727.429639] [<ffffffff8113f07d>] ? SyS_write+0x4d/0xa0 [ 6727.429644] [<ffffffff81005192>] ? SyS_iopl+0x72/0xa0 [ 6727.429662] [<ffffffff815cb692>] system_call_fastpath+0x16/0x1b [ 6727.429665] ---[ end trace 57ca81ad7543212e ]--- [ 6727.947371] nouveau 0000:01:00.0: power state changed by ACPI to D0 I have attached my regular dmesg after reboot as well, since at some point I had run dmesg --clear due to brcmsmac spamming my logs. I have also noticed that since the commit enabling nouveau MSI my laptop has micro freezes when the GPU transitions power states and DMAR now spews PWRITE errors.
Created attachment 85212 [details] trying again with DRI_PRIME=1 results in kernel panic when rebooting I tried DRI_PRIME=1 nexuiz-glx with the same result, except this time when I tried rebooting I got a kernel panic. Sorry about the horrdendous quality of the picture.
I can reproduce this bug by booting the machine with HDMI connected to my TV (artifacts show up on the laptop but not the TV). Also, to clarify: these issues do not exist with stable 3.11.0, and both cards can run Nexuiz without issue there.
Created attachment 85294 [details] PTE Write errors PTE Write errors, but as the dmesg shows, VirtualBox works fine
The DMAR errors are for the nvidia chip, the render errors are from mesa/i965 and will require a separate bug report so that it doesn't get spuriously rerouted again. And the kernel panic is also nouveau. Since you have an Arrandale, I would suggest disabling DMAR. Which leaves: *ERROR* mismatch in adjusted_mode.flags(DRM_MODE_FLAG_PHSYNC) (expected 0, found 1)
Yes, sorry, I will not confuse the issue or use DMAR. ;) I noticed today that both cards can run the game fine if I pass -windowed to either the glx or sdl client.
Please retest with latest drm-intel-fixes git from http://cgit.freedesktop.org/~danvet/drm-intel/ - we've just recently fixed a few bugs for mismatches in the mode flags. If that kernel still exhibits the pipe mismatch backtrace then please boot with drm.debug=0xe added to your kernel cmdline, reproduce the backtrace and then attach the complete log.
Created attachment 85507 [details] drm.debug=0xe tested with both cards, works fine
Indeed, one of those commits fixes fullscreen in both Nexuiz and OpenArena.
(In reply to comment #8) > Indeed, one of those commits fixes fullscreen in both Nexuiz and OpenArena. Yup, that was another bug around the panel fitter handling. Thanks for reporting back the test results.
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.