[Bug 103913] DRM/Radeon driver not resilient to poor monitor connections

[Bug 103913] DRM/Radeon driver not resilient to poor monitor connections

[bugzilla-daemon]

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

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

            Bug ID: 103913
           Summary: DRM/Radeon driver not resilient to poor monitor
                    connections
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: roger@beardandsandals.co.uk

Disconnecting and reconnecting HDMI/DVI connectors, or a loose connection, can
cause the driver to stall in a loop with the following messages being logged
approximately every 500ms in syslog.

Nov 25 16:13:30 dragon kernel: [363196.855813] radeon 0000:02:00.0: ring 0
stalled for more than 1710608msec
Nov 25 16:13:30 dragon kernel: [363196.855818] radeon 0000:02:00.0: GPU lockup
(current fence id 0x0000000000284cb5 last fence id 0x0000000000284cb6 on ring
0)

This causes the screen to blank. A reboot is required to clear this.

It would seem more sensible to reset the driver if it has been locked on the
same fence for a long time.

=====================================================================

(II) Module radeon: vendor="X.Org Foundation"        [    82.693]    compiled
for 1.19.3, module version = 7.10.0      [    82.693]    Module class: X.Org
Video Driver                  [    82.693]    ABI class: X.Org Video Driver,
version 23.0       [    82.693] (II) 

roger@dragon:/var/log$ sudo lshw -c video                                      
                            *-display
       description: VGA compatible controller
       product: RV770 [Radeon HD 4850]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:02:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=radeon latency=0
       resources: irq:26 memory:d0000000-dfffffff memory:fbae0000-fbaeffff
ioport:b000(size=256) memory:c0000-dffff


Roger

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

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

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

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

[Bug 103913] DRM/Radeon GPU hang

[bugzilla-daemon]

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

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

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|DRM/Radeon driver not       |DRM/Radeon GPU hang
                   |resilient to poor monitor   |
                   |connections                 |

--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
The monitor connections have nothing to do with GPU hangs.  Can you narrow down
what application causes the GPU hang?

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

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

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

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

[Bug 103913] DRM/Radeon GPU hang

[bugzilla-daemon]

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

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

--- Comment #2 from roger@beardandsandals.co.uk ---
No applications are running other than gnome desktop itself. I doubt this
actually a real GPU hang, that is just what it says in the syslog messages. Are
fences used by the driver for anything other than communicating with the GPU?

I can trigger this by pulling out the HDMI cable and sticking it back in again.

I will do some more tests over the next couple of days.

Roger

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

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

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

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

[Bug 103913] DRM/Radeon GPU hang

[bugzilla-daemon]

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

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

--- Comment #3 from roger@beardandsandals.co.uk ---
Just found out that my gnome desktop is rendering through Wayland. I wonder if
that is relevant.

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

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

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

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

[Bug 103913] DRM/Radeon GPU hang

[bugzilla-daemon]

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

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

roger@beardandsandals.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from roger@beardandsandals.co.uk ---
I moved to a simpler is single head setup and found that this loop occurs
randomly without any changes to the monitor connection. It fact it usually
occurs after the system has been idle for some time with just the gnome desktop
running. I am marking this bug as resolved. I will switch over to using xserver
instead of Wayland and see if that resolves the issue. If it does I will raise
another bug with more appropriate information.

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

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

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

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