I don't think it is the same bug. I have a card with HDMI and DVI
connectors (XFX RX 460). The HDMI connector is connected to the monitor,
the DVI connector is unplugged.
// David
On 2018-04-30 17:40, Harry Wentland wrote:
> Replied on the ticket.
>
> If this is about non-functioning LVDS or VGA I'm aware of it and trying
> to find time to find a good solution.
>
> Harry
>
> On 2018-04-30 11:14 AM, Joseph Salisbury wrote:
>> Hi Harry,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found the following commit introduced the bug:
>>
>>
>> commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c
>> Author: Harry Wentland <email address hidden>
>> Date: Tue Sep 12 15:58:20 2017 -0400
>>
>> drm/amd/dc: Add dc display driver (v2)
>>
>>
>> The regression was introduced as of v4.15-rc1 and still exists in
>> current mainline. The commit does not need to be reverted to resolve
>> the bug. Disabling the CONFIG_DRM_AMD_DC_PRE_VEGA option makes the bug
>> go away.
>>
>> I was hoping to get your feedback, since you are the patch author. Do
>> you think gathering any additional data will help diagnose this issue?
>>
>>
>> Thanks,
>>
>> Joe
>>
>>
>> [0] http://pad.lv/1761751
>>
I don't think it is the same bug. I have a card with HDMI and DVI
connectors (XFX RX 460). The HDMI connector is connected to the monitor,
the DVI connector is unplugged.
// David
On 2018-04-30 17:40, Harry Wentland wrote: aeb6ee93b2d8a84 9a4c4e1c7c DRM_AMD_ DC_PRE_ VEGA option makes the bug pad.lv/ 1761751
> Replied on the ticket.
>
> If this is about non-functioning LVDS or VGA I'm aware of it and trying
> to find time to find a good solution.
>
> Harry
>
> On 2018-04-30 11:14 AM, Joseph Salisbury wrote:
>> Hi Harry,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found the following commit introduced the bug:
>>
>>
>> commit 4562236b3bc0a28
>> Author: Harry Wentland <email address hidden>
>> Date: Tue Sep 12 15:58:20 2017 -0400
>>
>> drm/amd/dc: Add dc display driver (v2)
>>
>>
>> The regression was introduced as of v4.15-rc1 and still exists in
>> current mainline. The commit does not need to be reverted to resolve
>> the bug. Disabling the CONFIG_
>> go away.
>>
>> I was hoping to get your feedback, since you are the patch author. Do
>> you think gathering any additional data will help diagnose this issue?
>>
>>
>> Thanks,
>>
>> Joe
>>
>>
>> [0] http://
>>