On 06/14/2012 06:27 PM, Daniel Vetter wrote:
Well, can you revert this patch (or just replace the 5 with 3 in the
code) on top of latest 3.4.x and test whether this is indeed the cause
of your regression? Just to make sure that we have the right culprit.
Hi Daniel,
Yes, 3.4.2 with 092945e11c5b8
On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
In the mean while I will redo the bisect.
Hi guys,
I did a bisect on the actual problem (and not on the maybe-related
second error message). It results in
092945e11c5b84f66dd08f0b87fb729715d377bc:
Author: Adam Jackson 2011-07-26 20:39:45
Com
On 06/14/2012 06:27 PM, Daniel Vetter wrote:
> Well, can you revert this patch (or just replace the 5 with 3 in the
> code) on top of latest 3.4.x and test whether this is indeed the cause
> of your regression? Just to make sure that we have the right culprit.
Hi Daniel,
Yes, 3.4.2 with 092945e11c
On Thu, Jun 14, 2012 at 7:14 PM, Wouter M. Koolen
wrote:
> On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
>>
>> In the mean while I will redo the bisect.
>
> Hi guys,
>
> I did a bisect on the actual problem (and not on the maybe-related second
> error message). It results in 092945e11c5b84f66dd0
On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
> In the mean while I will redo the bisect.
Hi guys,
I did a bisect on the actual problem (and not on the maybe-related
second error message). It results in
092945e11c5b84f66dd08f0b87fb729715d377bc:
Author: Adam Jackson 2011-07-26 20:39:45
Comm
On Thu, Jun 14, 2012 at 4:00 PM, Dave Airlie wrote:
> On Thu, Jun 14, 2012 at 2:26 PM, Wouter M. Koolen
> wrote:
> cc'ing Daniel.
>
>> Hi Igor and Len,
>>
>> When I cold boot 3.4 on my laptop the second monitor attached to the
>> displayport stays blank. It works fine with 3.3.8 and earlier.
>>
>
On 06/14/2012 03:05 PM, Daniel Vetter wrote:
> Can you please boot with drm.debug=0xe added to your kernel
> cmdline and attach the full dmesg, so we know a bit what your display
> hw looks like?
Please find attached dmesg output with drm.debug=0xe.
3.3.8 is the baseline, on which the display port
On Thu, Jun 14, 2012 at 7:14 PM, Wouter M. Koolen
wrote:
> On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
>>
>> In the mean while I will redo the bisect.
>
> Hi guys,
>
> I did a bisect on the actual problem (and not on the maybe-related second
> error message). It results in 092945e11c5b84f66dd0
On Thu, Jun 14, 2012 at 4:00 PM, Dave Airlie wrote:
> On Thu, Jun 14, 2012 at 2:26 PM, Wouter M. Koolen
> wrote:
> cc'ing Daniel.
>
>> Hi Igor and Len,
>>
>> When I cold boot 3.4 on my laptop the second monitor attached to the
>> displayport stays blank. It works fine with 3.3.8 and earlier.
>>
>
