Re: [Intel-gfx] Regression in i915
On 4/7/20 12:35 PM, Chris Wilson wrote: 2 possible causes for 2 very different symptoms are in flight. But neither would strictly be a hang; the most blatant one would be the display server triggering an EFAULT. The patches are currently sitting in the drm-intel-next-fixes queue; a quick test of drm-tip would confirm how worried one needs to be. The machine was still running, but I could not get access to any terminal to check the problem. When I booted to single-useer mode and then tried to start X, it failed but logged no useful errors. I do not know which patch fixed the problem, but a pull of drm-intel-next-queued handled the problem. My system is now booting fine. I think we only need to worry about the coronavirus, I did have one trivial merge conflict to fix. Thanks for your help. Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Regression in i915
Chris, With a recent pull of kernel head, my Toshiba laptop with an i915 graphics card fails to boot. It hangs at the point where it should switch to a graphics screen. I bisected the problem to commit 7dc8f1143778a35b190f9413f228b3cf28f67f8d Author: Chris Wilson Date: Wed Mar 11 16:03:10 2020 + drm/i915/gem: Drop relocation slowpath The lspci command reports my card as 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Has this problem been reported, and is there a fix? Thanks, Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Warning for driver i915 for 4.17.0-rcX
On 05/02/2018 01:12 AM, Jani Nikula wrote: On Mon, 30 Apr 2018, Larry Finger wrote: With kernel 4.17.0-rc3, I noted the following warning from driver i915. kernel: [ cut here ] kernel: Could not determine valid watermarks for inherited state kernel: WARNING: CPU: 3 PID: 224 at drivers/gpu/drm/i915/intel_display.c:14584 intel_modeset_init+0x3be/0x1060 [i915] Please try [1], see also the related bug [2]. BR, Jani. [1] http://patchwork.freedesktop.org/patch/msgid/20180426163015.14232-1-ville.syrj...@linux.intel.com [2] https://bugs.freedesktop.org/show_bug.cgi?id=105992 Thanks for your reply. Patch [1] above does fix my warning. Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Warning for driver i915 for 4.17.0-rcX
With kernel 4.17.0-rc3, I noted the following warning from driver i915. kernel: [ cut here ] kernel: Could not determine valid watermarks for inherited state kernel: WARNING: CPU: 3 PID: 224 at drivers/gpu/drm/i915/intel_display.c:14584 intel_modeset_init+0x3be/0x1060 [i915] kernel: Modules linked in: i915(+) xhci_pci i2c_algo_bit ehci_pci xhci_hcd serio_raw drm_kms_helper ehci_hcd syscopyarea sysfillrect sysimgblt kernel: CPU: 3 PID: 224 Comm: systemd-udevd Not tainted 4.17.0-rc0-08000-g2f39cfca0161-dirty #188 kernel: Hardware name: TOSHIBA TECRA A50-A/TECRA A50-A, BIOS Version 4.50 09/29/2014 kernel: RIP: 0010:intel_modeset_init+0x3be/0x1060 [i915] kernel: RSP: 0018:c9000112fab8 EFLAGS: 00010296 kernel: RAX: 0038 RBX: 88021dc1 RCX: 0006 kernel: RDX: 0007 RSI: 0082 RDI: 88022f2d5bd0 kernel: RBP: 88021c8b3000 R08: 0289 R09: 0004 kernel: R10: c9000112f948 R11: 0001 R12: 88021ef3d800 kernel: R13: ffea R14: R15: 88021dc10358 kernel: FS: 7f830913c940() GS:88022f2c() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 7ffc91722f58 CR3: 00021e940003 CR4: 001606e0 kernel: Call Trace: kernel: i915_driver_load+0xa87/0xed0 [i915] kernel: local_pci_probe+0x42/0xa0 kernel: pci_device_probe+0x125/0x190 kernel: driver_probe_device+0x30b/0x480 kernel: __driver_attach+0xb8/0xe0 kernel: ? driver_probe_device+0x40/0x480 kernel: ? driver_probe_device+0x480/0x480 kernel: bus_for_each_dev+0x65/0x90 kernel: bus_add_driver+0x161/0x260 kernel: ? 0xa0149000 kernel: driver_register+0x57/0xc0 kernel: ? 0xa0149000 kernel: do_one_initcall+0x4e/0x18d kernel: ? kmem_cache_alloc_trace+0xfe/0x210 kernel: ? do_init_module+0x22/0x20a kernel: do_init_module+0x5b/0x20a kernel: load_module+0x18a1/0x1e20 kernel: ? SYSC_finit_module+0xb7/0xd0 kernel: SYSC_finit_module+0xb7/0xd0 kernel: do_syscall_64+0x6e/0x120 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 kernel: RIP: 0033:0x7f8307f67529 kernel: RSP: 002b:7ffc91737ab8 EFLAGS: 0246 ORIG_RAX: 0139 kernel: RAX: ffda RBX: 559b3cf6f350 RCX: 7f8307f67529 kernel: RDX: RSI: 7f83088cd83d RDI: 0014 kernel: RBP: 7f83088cd83d R08: R09: 559b3cf44f50 kernel: R10: 0014 R11: 0246 R12: 0002 kernel: R13: 559b3cf634a0 R14: R15: 03938700 kernel: Code: 00 f7 c6 00 00 18 00 0f 84 d7 0a 00 00 85 c9 0f 94 c1 41 88 8c 24 8d 02 00 00 e9 f6 08 00 00 48 c7 c7 b0 2f 41 a0 e8 f2 9b cd e0 kernel: ---[ end trace c0feea6402f4c999 ]--- This warning was bisected to commit a2936e3d9a9cb2ce192455cdec3a8cfccc26b486 (refs/bisect/bad) Author: Ville Syrjälä Date: Thu Nov 23 21:04:49 2017 +0200 drm/i915: Use drm_mode_get_hv_timing() to populate plane clip rectangle Cc: Laurent Pinchart Signed-off-by: Ville Syrjälä Reviewed-by: Daniel Vetter Reviewed-by: Thierry Reding The output of 'lspci -nn -vvv' for the gracpics device is as follows: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0002] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Interrupt: pin A routed to IRQ 28 Region 0: Memory at e000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 This warning does not seem to cause any problems. Thanks, Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression in i915 for 4.11-rc1 - bisected to commit 69df05e11ab8
On 03/23/2017 03:44 PM, Chris Wilson wrote:
On Thu, Mar 23, 2017 at 01:19:43PM -0500, Larry Finger wrote:
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered
intermittent hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in
plasmashell [1283], reason: Hang on render ring, action: reset
linux-4v1g.suse kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
linux-4v1g.suse kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
linux-4v1g.suse kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
linux-4v1g.suse kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
linux-4v1g.suse kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
linux-4v1g.suse kernel: drm/i915: Resetting chip after gpu hang
This problem was added to
https://bugs.freedesktop.org/show_bug.cgi?id=99380, but it probably
is a different bug, as the OP in that report has problems with
kernel 4.10.x, whereas my problem did not appear until 4.11.
Close. Actually that patch touches code you are not using (oa-perf and
gvt), the real culprit was e8a9c58fcd9a ("drm/i915: Unify active context
tracking between legacy/execlists/guc").
The fix
commit 5d4bac5503fcc67dd7999571e243cee49371aef7
Author: Chris Wilson
Date: Wed Mar 22 20:59:30 2017 +
drm/i915: Restore marking context objects as dirty on pinning
Commit e8a9c58fcd9a ("drm/i915: Unify active context tracking between
legacy/execlists/guc") converted the legacy intel_ringbuffer submission
to the same context pinning mechanism as execlists - that is to pin the
context until the subsequent request is retired. Previously it used the
vma retirement of the context object to keep itself pinned until the
next request (after i915_vma_move_to_active()). In the conversion, I
missed that the vma retirement was also responsible for marking the
object as dirty. Mark the context object as dirty when pinning
(equivalent to execlists) which ensures that if the context is swapped
out due to mempressure or suspend/hibernation, when it is loaded back in
it does so with the previous state (and not all zero).
Fixes: e8a9c58fcd9a ("drm/i915: Unify active context tracking between
legacy/execlists/guc")
Reported-by: Dennis Gilmore
Reported-by: Mathieu Marquer
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=3
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100181
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: # v4.11-rc1
Link:
http://patchwork.freedesktop.org/patch/msgid/20170322205930.12762-1-ch...@chris-wilson.co.uk
Reviewed-by: Tvrtko Ursulin
went in this morning and so will be upstreamed ~next week.
-Chris
Thanks. With a bug that is difficult to trigger, bisection is difficult. I am
surprised that the only step I got wrong was the last one. BTW, my reversion
failed after 20 hours. I was ready to write again when I got your fix. Good timing.
If your patch does not fix my problem, I will let you know.
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Regression in i915 for 4.11-rc1 - bisected to commit 69df05e11ab8
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered intermittent
hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in plasmashell
[1283], reason: Hang on render ring, action: reset
linux-4v1g.suse kernel: [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
linux-4v1g.suse kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
linux-4v1g.suse kernel: [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
linux-4v1g.suse kernel: [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
linux-4v1g.suse kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
linux-4v1g.suse kernel: drm/i915: Resetting chip after gpu hang
This problem was added to https://bugs.freedesktop.org/show_bug.cgi?id=99380,
but it probably is a different bug, as the OP in that report has problems with
kernel 4.10.x, whereas my problem did not appear until 4.11.
The problem was bisected to commit 69df05e11ab8 ("drm/i915: Simplify releasing
context reference"). The accuracy of the bisection was tested by reverting that
patch in kernel 4.11-rc3. With that change, my kernel has now run for over 17
hours with no problem. Before the reversion, the longest any affected kernel
would run was ~3 hours until a gpu hang was detected.
I admit that I do not understand this driver, but my guess is that this commit
introduced a race condition in the context put.
Thanks,
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Critical regression in 4.7-rcX
On 07/15/2016 11:36 AM, Bish, Jim wrote:
On Fri, 2016-07-15 at 10:34 -0500, Larry Finger wrote:
On 07/15/2016 09:43 AM, Ville Syrjälä wrote:
On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote:
On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds
wrote:
On Thu, 14 Jul 2016, Larry Finger wrote:
To anyone keeping track of regressions in kernel 4.7, I call
your attention to
https://bugs.freedesktop.org/show_bug.cgi?id=96675.
This bug causes driver i915 to fail to connect to the
display, and results in
a blank screen as soon as the kernel is loaded. The only way
to operate with
kernel 4.7 is to add "nomodeset" to the command line. The
problem was bisected
to commit f21a21983ef13a ("drm/i915: Splitting
intel_dp_detect").
Daniel? Jani? Time to revert?
Yup. Means that I'll get to revert a pile of patches (plus even
more
in -next), but that's what we get for not handling regressions
timely.
Dave poked me about the same bug already too. But will take a few
days
until the pull is in your inbox I guess.
I attached a oneliner to the bug today, that I *think* should fix
the
problem.
After I checked out the problem commit and built that kernel with the
one-line
patch, the display works; however, mainline still fails. I am
currently
bisecting to find what other commit fails. At a minimum, we should be
able to
reduce the number of commits that need reverting.
Larry
I was seeing the same issue Linus reported but very sporadically.
Assumed it was due to my wierd configuration - eDP + usb type c -> MST
hub -> DVI KVM -> dual head HDMI. Checked out the one liner - works
for me but I guess there are still other failures.
I'm not sure what I did wrong before, but when I retested mainline with the one
liner, it now works. Once that is pushed to mainline, the bug should be fixed.
Sorry for any confusion.
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Critical regression in 4.7-rcX
On 07/15/2016 09:43 AM, Ville Syrjälä wrote:
On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote:
On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds
wrote:
On Thu, 14 Jul 2016, Larry Finger wrote:
To anyone keeping track of regressions in kernel 4.7, I call your attention to
https://bugs.freedesktop.org/show_bug.cgi?id=96675.
This bug causes driver i915 to fail to connect to the display, and results in
a blank screen as soon as the kernel is loaded. The only way to operate with
kernel 4.7 is to add "nomodeset" to the command line. The problem was bisected
to commit f21a21983ef13a ("drm/i915: Splitting intel_dp_detect").
Daniel? Jani? Time to revert?
Yup. Means that I'll get to revert a pile of patches (plus even more
in -next), but that's what we get for not handling regressions timely.
Dave poked me about the same bug already too. But will take a few days
until the pull is in your inbox I guess.
I attached a oneliner to the bug today, that I *think* should fix the
problem.
After I checked out the problem commit and built that kernel with the one-line
patch, the display works; however, mainline still fails. I am currently
bisecting to find what other commit fails. At a minimum, we should be able to
reduce the number of commits that need reverting.
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Critical regression in 4.7-rcX
On 07/15/2016 09:43 AM, Ville Syrjälä wrote:
On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote:
On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds
wrote:
On Thu, 14 Jul 2016, Larry Finger wrote:
To anyone keeping track of regressions in kernel 4.7, I call your attention to
https://bugs.freedesktop.org/show_bug.cgi?id=96675.
This bug causes driver i915 to fail to connect to the display, and results in
a blank screen as soon as the kernel is loaded. The only way to operate with
kernel 4.7 is to add "nomodeset" to the command line. The problem was bisected
to commit f21a21983ef13a ("drm/i915: Splitting intel_dp_detect").
Daniel? Jani? Time to revert?
Yup. Means that I'll get to revert a pile of patches (plus even more
in -next), but that's what we get for not handling regressions timely.
Dave poked me about the same bug already too. But will take a few days
until the pull is in your inbox I guess.
I attached a oneliner to the bug today, that I *think* should fix the
problem.
Unfortunately, that patch did not help. If you have any other patches, or a repo
I can pull from for testing, please let me know.
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Regression in i915 in kernel 4.6.0-git - bisected to f21a21983ef13a031
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The adapter in question is the
integrated graphics controller on a Toshiba Tecra A50 laptop. The output of
"lspci -nnv" for that controller is as follows:
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Toshiba America Info Systems Device [1179:0002]
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at e000 (64-bit, non-prefetchable) [size=4M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915
New information: I have used SSH to connect to the laptop to see the logs. In
the dmesg output, I see "i915 :00:02.0: No connectors reported connected
with modes". I will try to determine why that is happening.
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Regression in i915 in kernel 4.6.0-git - bisected to f21a21983ef13a031
The latest mainline kernel (commit 3f59de0) shows a regression. The symptom is
that as soon as the kernel is started, the display is blanked, and it is never
turned on again. This problem was bisected to commit
f21a21983ef13a031250c4c3f6018e29a549d0f1
("drm/i915: Splitting intel_dp_detect"). The adapter in question is the
integrated graphics controller on a Toshiba Tecra A50 laptop. The output of
"lspci -nnv" for that controller is as follows:
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Toshiba America Info Systems Device [1179:0002]
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at e000 (64-bit, non-prefetchable) [size=4M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915
If the kernel is booted with "nomodeset", the display is normal.
I will be happy to test any patches, or to answer any further questions.
Thanks,
Larry
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] Logged messages from i915 using kernel 3.19-rc4
Hi, I just discovered almost 100 of the following entries in my log: [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt Those were accumulated in about 12 hours of operation. I also have one that says i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment The above output was in the middle of the other type. The "lspci -nnv" stanza for the i915 is: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0002] Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at e000 (64-bit, non-prefetchable) [size=4M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 Please let me know of any further info that you need, or any diagnostics that I can add. Thanks, Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
[Intel-gfx] WARNING in 3.17-rc1 for i915
My Toshiba A50 with graphics adapter described by 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) gets the following warning on 3.17-rc1: [ 1271.563533] [ cut here ] [ 1271.563568] WARNING: CPU: 1 PID: 1050 at drivers/gpu/drm/i915/intel_display.c:1234 assert_cursor.constprop.79+0x99/0xa0 [i915]() [ 1271.563571] cursor on pipe A assertion failure (expected off, current on) [ 1271.563573] Modules linked in: ctr ccm fuse nfs bnep bluetooth af_packet fscache arc4 x86_pkg_temp_thermal kvm_intel iwlmvm kvm mac80211 crct10dif_pclmul crc32_pclmul crc32c_intel snd_hda_codec_generic i915 snd_hda_intel ghash_clmulni_intel aesni_intel aes_x86_64 snd_hda_controller lrw gf128mul snd_hda_codec glue_helper iwlwifi ablk_helper rtsx_pci_sdmmc cryptd snd_hwdep snd_pcm rtsx_pci_ms memstick mmc_core snd_seq acpi_cpufreq cfg80211 drm_kms_helper processor drm microcode pcspkr serio_raw thermal video thermal_sys sr_mod cdrom lpc_ich snd_seq_device snd_timer rfkill rtsx_pci mfd_core snd soundcore e1000e i2c_algo_bit hwmon ptp pps_core wmi xhci_hcd ac battery button sg dm_mod autofs4 [ 1271.563659] CPU: 1 PID: 1050 Comm: Xorg Not tainted 3.17.0-rc1+ #9 [ 1271.563661] Hardware name: TOSHIBA TECRA A50-A/TECRA A50-A, BIOS Version 4.20 04/17/2014 [ 1271.563664] 0009 8800c72f7aa8 816a009b 8800c72f7af0 [ 1271.563670] 8800c72f7ae0 8105bdfd [ 1271.563675] 0003 8800c6741000 8800c6741000 8800c72f7b40 [ 1271.563681] Call Trace: [ 1271.563688] [] dump_stack+0x4d/0x6f [ 1271.563695] [] warn_slowpath_common+0x7d/0xa0 [ 1271.563699] [] warn_slowpath_fmt+0x4c/0x50 [ 1271.563720] [] assert_cursor.constprop.79+0x99/0xa0 [i915] [ 1271.563737] [] intel_enable_pipe+0x49/0x1f0 [i915] [ 1271.563757] [] haswell_crtc_enable+0x486/0xa80 [i915] [ 1271.563774] [] __intel_set_mode+0x822/0xac0 [i915] [ 1271.563793] [] intel_set_mode+0x16/0x30 [i915] [ 1271.563811] [] intel_crtc_set_config+0x92c/0xe70 [i915] [ 1271.563828] [] drm_mode_set_config_internal+0x67/0xf0 [drm] [ 1271.563843] [] drm_mode_setcrtc+0xdc/0x590 [drm] [ 1271.563855] [] drm_ioctl+0x1a6/0x640 [drm] [ 1271.563862] [] ? __fget+0x5/0xe0 [ 1271.563867] [] do_vfs_ioctl+0x300/0x520 [ 1271.563871] [] ? __fget+0xad/0xe0 [ 1271.563876] [] ? __fget+0x5/0xe0 [ 1271.563880] [] SyS_ioctl+0x81/0xa0 [ 1271.563887] [] system_call_fastpath+0x16/0x1b [ 1271.563889] ---[ end trace 2327ac1a479ad52b ]--- Larry ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
