On Tue, Oct 8, 2013 at 6:08 PM, Roland Dreier wrote:
> On Mon, Oct 7, 2013 at 11:10 PM, Daniel Vetter wrote:
>> Can you please boot with drm.debug=0xe, reproduce the issue and then
>> attach the dmesg. The additional debug spam should shed some light on how
>> we managed to get into this peculiar
On Mon, Oct 7, 2013 at 11:10 PM, Daniel Vetter wrote:
> Can you please boot with drm.debug=0xe, reproduce the issue and then
> attach the dmesg. The additional debug spam should shed some light on how
> we managed to get into this peculiar situation ...
Sure, here it is.
Thanks,
Roland
---
Hi,
I have a Lenovo T410s (Ironlake/Arrandale graphics) that I use docked
and connected to an external DP monitor (laptop is closed so the only
active display is the DP monitor). With 3.12-rc4 I reproducably hit a
deadlock when I undock the laptop -- it seems to be a deadlock on
dev->mode_confix.
On Mon, Oct 07, 2013 at 03:41:05PM -0700, Roland Dreier wrote:
> Hi,
>
> I have a Lenovo T410s (Ironlake/Arrandale graphics) that I use docked
> and connected to an external DP monitor (laptop is closed so the only
> active display is the DP monitor). With 3.12-rc4 I reproducably hit a
> deadlock
