Bug 60534 - i915 deadlock related to lock(&dev->struct_mutex);
Summary: i915 deadlock related to lock(&dev->struct_mutex);
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: Daniel Vetter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-08 15:17 UTC by Alexander E. Patrakov
Modified: 2015-10-07 09:55 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.10-rc7 plus patches
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmesg illustrating the problem (99.87 KB, text/plain)
2013-07-08 15:17 UTC, Alexander E. Patrakov
Details

Description Alexander E. Patrakov 2013-07-08 15:17:35 UTC
Created attachment 106845 [details]
Dmesg illustrating the problem

I have a 3.10-rc7 kernel plus radeon-related patches from branch 'drm-next-3.11-wip-4' of git://people.freedesktop.org/~agd5f/linux

My laptop has both an Intel graphics chip in itself and a Radeon chip in a hot-pluggable dock station. Both graphics cards have usable outputs. So I was playing with xrandr --setprovideroffloadsink and --setprovideroutputsource. By doing so, I was able to cause a deadlock in the i915 driver. I am going to attach a dmesg that illustrates it.
Comment 1 Daniel Vetter 2013-07-08 20:30:37 UTC
Known issue with the current prime code, we need w/w mutexes (now mergd into latest git) and a completely reworking locking in drm/i915 (not even started yet).

This will take a while to fix.
Comment 4 Jani Nikula 2014-08-14 11:29:03 UTC
Daniel, have we finally fixed this?
Comment 5 Daniel Vetter 2014-10-19 11:31:00 UTC
No, still need to rewrite half the driver ...

The nouveau/radeon side of this little project from Maarten is merged into 3.18 though.
Comment 6 Jani Nikula 2015-10-07 09:55:15 UTC
If the problem persists with latest kernels, please file a bug at the freedesktop.org bugzilla [1], referencing this bug. Thank you.

[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel

Note You need to log in before you can comment on or make changes to this bug.