Comment # 39 on bug 954783 from Takashi Iwai

(In reply to Jozef Kovac from comment #38)
> I found nothing  relevant in log, actualy  nothing at all  in that time  and
> never happen again,  tested for couple days, probably another bug, not
> related to radeon or need special circumstances.
> 
> 
> But i  set up  netconsole(with my old mini 2133 Debian)  and try capture 
> old DRI_PRIME=1  bug.
>  
> 4.1.12-1  immediately after i use DRI_PRIME=1  show:
> 
> [  187.561982] [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create
> device file for dpm state
> [  187.562556] [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create
> device file for dpm state
> [  187.563102] [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create
> device file for power profile
> [  187.563643] [drm:radeon_pm_late_init [radeon]] *ERROR* failed to create
> device file for power method

These are the bugs that have been fixed in 4.1.13.

> [  187.678751] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP =
> 65535

This is usually non-fatal issue.  It's checked since recent kernels.

>  and nothing more until crash.
> 
> 4.1.13-5  show  every time when DRI_PRIME=1 is in use.
> 
> [  378.149829] snd_hda_intel 0000:03:00.1: CORB reset timeout#2, CORBRP =
> 65535 

This is same as above, thus no cause.  So, we didn't catch the cause yet...

> 3.16.7-29 
> 
> nothing show via netconsole when i use DRI_PRIME=1 and work absolutly stable.

The old kernel had no check in HD-audio driver.

> With 4.1.12  crash  everytime  after couple minutes (max 7min),  but
> 4.1.13-5  crash 32min/2min/11min  when DRI_PRIME=1  when used.(tested three
> times)

Does it with a high CPU load, or it happens in idle state, too?
I wonder whether it's a software failure, or it's triggered by hardware (by
some change in kernel, etc).

Also, if it's about graphics, you may boot with drm.debug=0x0e option.  Then
it'll show more verbose logs regarding graphics.