[Bug 111182] Fade-to-white after KMS is set on RV635

* [Bug 111182] Fade-to-white after KMS is set on RV635
@ 2019-07-22  9:38 bugzilla-daemon
  2019-07-22 10:33 ` bugzilla-daemon
  2019-11-19  9:35 ` bugzilla-daemon
  0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2019-07-22  9:38 UTC (permalink / raw)
  To: dri-devel

[-- Attachment #1.1: Type: text/plain, Size: 2061 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111182

            Bug ID: 111182
           Summary: Fade-to-white after KMS is set on RV635
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: thumperward@hotmail.com

Created attachment 144837
  --> https://bugs.freedesktop.org/attachment.cgi?id=144837&action=edit
dmesg output after blacklisting radeon, then enabling it after boot

I have a laptop with a Radeon Mobility 3670. With KMS disabled I can boot
normally; however, otherwise it typically locks hard as soon as modesetting
happens, with an odd effect where the screen gradually fades to being nearly
completely white. (I can provide video if for some reason this would help).

However, on occasion (rarely) it will flicker for a second, successfully switch
modes, spit out "Timeout setting UVD clocks", and then carry on correctly.

Given that this happens very early in the boot, and hard locks the system, I've
taken to blacklisting radeon in my boot parameters, then doing a "sudo modprobe
radeon" after logging in and crossing my fingers. Attached is dmesg output from
such a case - note the delay between lines 918 and 919 as boot finished, I
logged in, and then ran modprobe. Lines 950-955 show the errors that get echoed
as the system then successfully switches modes.

(blacklisting until after boot isn't the only way to get it working - it just
happens to give me more of a sense of control than repeatedly power-cycling and
hoping the system boots normally.)

The closest example I could find on search was 16389 - however none of the
workarounds there help, and when the screen fades the machine is subsequently
completely unreponsive.

Debian 10 buster, 1:19.0.1-1

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

[-- Attachment #1.2: Type: text/html, Size: 3594 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread