Bug 89187 - MST backport to 3.16 crashes
Summary: MST backport to 3.16 crashes
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Dave Airlie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-17 14:52 UTC by Dariusz Gadomski
Modified: 2017-07-24 22:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Kernel config used (166.48 KB, text/plain)
2015-02-17 14:52 UTC, Dariusz Gadomski
no flags Details
full dmesg output (254.65 KB, text/plain)
2015-02-17 14:53 UTC, Dariusz Gadomski
no flags Details
dmesg output with drm.debug=1 (254.65 KB, text/plain)
2015-02-17 14:53 UTC, Dariusz Gadomski
no flags Details

Description Dariusz Gadomski 2015-02-17 14:52:52 UTC
Created attachment 113571 [details]
Kernel config used

I have built kernel from sources [1] containing David Airlie's MST i915 backport for the 3.16 kernel. I have used Ubuntu config (attached).

After connecting daisy-chained monitors (Dell U2414H) I get the following stack trace:

[   38.186428] CPU: 1 PID: 2395 Comm: Xorg Tainted: G        W  OE 3.16.0+ #1
[   38.186429] Hardware name: Dell Inc. XPS 15 9530/XPS 15 9530, BIOS A07 10/15/2014
[   38.186430]  0000000000000009 ffff8803f83378c8 ffffffff82759c3f ffff8803f8337910
[   38.186433]  ffff8803f8337900 ffffffff8206d97d ffff880412735058 ffff8804127356f8
[   38.186435]  ffff880414866800 ffff880412735000 ffff880414866b40 ffff8803f8337960
[   38.186437] Call Trace:
[   38.186440]  [<ffffffff82759c3f>] dump_stack+0x45/0x56
[   38.186443]  [<ffffffff8206d97d>] warn_slowpath_common+0x7d/0xa0
[   38.186445]  [<ffffffff8206d9ec>] warn_slowpath_fmt+0x4c/0x50
[   38.186456]  [<ffffffffc064cd63>] check_crtc_state+0x703/0xd70 [i915]
[   38.186469]  [<ffffffffc065b24f>] intel_modeset_check_state+0x28f/0x7a0 [i915]
[   38.186479]  [<ffffffffc065b7f5>] intel_set_mode+0x25/0x30 [i915]
[   38.186490]  [<ffffffffc065c73c>] intel_crtc_set_config+0x92c/0xe00 [i915]
[   38.186499]  [<ffffffffc042e421>] drm_mode_set_config_internal+0x61/0xe0 [drm]
[   38.186508]  [<ffffffffc0431f99>] drm_mode_setcrtc+0xd9/0x590 [drm]
[   38.186515]  [<ffffffffc04229cc>] drm_ioctl+0x1ec/0x660 [drm]
[   38.186519]  [<ffffffff821e4e10>] do_vfs_ioctl+0x2e0/0x4c0
[   38.186521]  [<ffffffff820a4c84>] ? vtime_account_user+0x54/0x60
[   38.186524]  [<ffffffff821e5071>] SyS_ioctl+0x81/0xa0
[   38.186526]  [<ffffffff827627bf>] tracesys+0xe1/0xe6
[   38.186528] ---[ end trace 8b3dd31c3c6e8ccc ]---


Attaching full dmesg and another dmesg with drm.debug=1 passed on the kernel command line.

I am using intel drivers built from git available here [2] (version 147e190d1e18d3ac6dc23aa4e493eec28aa75d1d).

[1] http://cgit.freedesktop.org/~airlied/linux/log/?h=drm-i915-mst-v3.16
[2] https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa
Comment 1 Dariusz Gadomski 2015-02-17 14:53:24 UTC
Created attachment 113572 [details]
full dmesg output
Comment 2 Dariusz Gadomski 2015-02-17 14:53:44 UTC
Created attachment 113573 [details]
dmesg output with drm.debug=1
Comment 3 Jani Nikula 2015-02-17 16:23:33 UTC
(In reply to Dariusz Gadomski from comment #0)
> I have built kernel from sources [1] containing David Airlie's MST i915
> backport for the 3.16 kernel. I have used Ubuntu config (attached).

Dave, all yours.
Comment 4 Chris Wilson 2015-02-17 20:42:40 UTC
I don't think we expect the backport to fix all the state checking hilarity, and whilst it is just the state checker WONTFIX for 3.16?
Comment 5 Jani Nikula 2015-02-18 15:23:28 UTC
(In reply to Chris Wilson from comment #4)
> I don't think we expect the backport to fix all the state checking hilarity,
> and whilst it is just the state checker WONTFIX for 3.16?

Well, *we* are definitely not doing it, but since Dave has done the backport to begin with, I figured it's up to him to respond.

OTOH this being upstream bugzilla, we might just as well resolve invalid.
Comment 6 Ander Conselvan de Oliveira 2015-06-03 16:37:34 UTC
(In reply to Jani Nikula from comment #5)
> (In reply to Chris Wilson from comment #4)
> > I don't think we expect the backport to fix all the state checking hilarity,
> > and whilst it is just the state checker WONTFIX for 3.16?
> 
> Well, *we* are definitely not doing it, but since Dave has done the backport
> to begin with, I figured it's up to him to respond.
> 
> OTOH this being upstream bugzilla, we might just as well resolve invalid.

Dave hasn't responded by now, so let's close invalid.


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.