On 03/28/2016 02:39 PM, Joseph Salisbury wrote:
> On 03/02/2016 04:58 PM, Joseph Salisbury wrote:
>> On 02/29/2016 04:33 AM, Jani Nikula wrote:
>>> On Wed, 24 Feb 2016, Joseph Salisbury
>>> wrote:
Hi Sonika,
A kernel bug report was opened against
On 03/02/2016 04:58 PM, Joseph Salisbury wrote:
> On 02/29/2016 04:33 AM, Jani Nikula wrote:
>> On Wed, 24 Feb 2016, Joseph Salisbury wrote:
>>> Hi Sonika,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that
On 02/29/2016 04:33 AM, Jani Nikula wrote:
> On Wed, 24 Feb 2016, Joseph Salisbury wrote:
>> Hi Sonika,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>>
On Wed, 24 Feb 2016, Joseph Salisbury wrote:
> Hi Sonika,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit 237ed86c693d8a8e4db476976aeb30df4deac74b
>
On 2/26/2016 12:11 AM, Joseph Salisbury wrote:
On 02/24/2016 10:53 PM, Jindal, Sonika wrote:
Hi Joe,
Yes, first thing to try is to increase the tries.
We testing with 300 retries, but the second monitor still did not show
up. However, it did show up in lspci.
Can you please point me to
Hi Joe,
Yes, first thing to try is to increase the tries.
Can you please point me to the bug and provide more details like platform,
monitor, cable.
Are you referring to the same issue as Oleksandr reported where a single link
dvi/hdmi cable didn’t work and dual link worked?
Regards,
Sonika
Hi Sonika,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 237ed86c693d8a8e4db476976aeb30df4deac74b
Author: Sonika Jindal
Date: Tue Sep 15 09:44:20 2015 +0530