[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=51381

--- Comment #24 from Teofilis Martisius <Teofilis.Martisius@gmail.com> ---
Hi,

Thank you once again for quick response.

Ok, a while ago I added radeon.no_wb=1 as without it I was getting display
corruption. That problem seems to be gone now, so there's no reason to keep
that option any more- I've taken it off.

I think you nailed the problem. On 3.12, it fails to turn ON the dGPU after it
has been turned OFF. I have tried this by booting 3.12 with following boot
parameters:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.12-1-amd64
root=UUID=6b66e960-0da6-4a99-abfe-f23614b50db9 ro quiet radeon.audio=0 modeset=

Then I did:

echo OFF >/sys/kernel/debug/vgaswitcheroo/switch
echo ON >/sys/kernel/debug/vgaswitcheroo/switch

After "echo ON" I got similar "atombios stuck in loop" errors in dmesg, and
errors that dGPU failed to come back on. 

"DRI_PRIME=1 glxgears" of course fails to work after that as well.

I've attached the dmesg from 3.12. Ok, what next?

P.S. Sorry for slow responses. I only have time to do this in the evenings, and
I'm in London- I guess you are in a different timezone.

Sincerely,
Teofilis Martisius

-- 
You are receiving this mail because:
You are watching the assignee of the bug.