On Mon, Aug 08, 2016 at 01:30:37PM -0400, Alex Deucher wrote:
> On Fri, Aug 5, 2016 at 8:30 PM, Lyude wrote:
> > While I was investigating an unrelated bug on the radeon driver, I noticed
> > that
> > it's become rather difficult to actually read through dmesg with drm.debug
> > turned on, on acc
On Fri, Aug 5, 2016 at 8:30 PM, Lyude wrote:
> While I was investigating an unrelated bug on the radeon driver, I noticed
> that
> it's become rather difficult to actually read through dmesg with drm.debug
> turned on, on account of the huge number of messages we end up printing from
> failed DP
Am 06.08.2016 um 02:30 schrieb Lyude:
> While I was investigating an unrelated bug on the radeon driver, I noticed
> that
> it's become rather difficult to actually read through dmesg with drm.debug
> turned on, on account of the huge number of messages we end up printing from
> failed DP aux tran
While I was investigating an unrelated bug on the radeon driver, I noticed that
it's become rather difficult to actually read through dmesg with drm.debug
turned on, on account of the huge number of messages we end up printing from
failed DP aux transactions that happen every time we reprobe each c
