dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103913] DRM/Radeon driver not resilient to poor monitor connections
Date: Sun, 26 Nov 2017 11:15:42 +0000	[thread overview]
Message-ID: <bug-103913-502@http.bugs.freedesktop.org/> (raw)


[-- 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

             reply	other threads:[~2017-11-26 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 11:15 bugzilla-daemon [this message]
2017-11-26 20:49 ` [Bug 103913] DRM/Radeon GPU hang bugzilla-daemon
2017-11-27 18:47 ` bugzilla-daemon
2017-11-29 20:57 ` bugzilla-daemon
2017-12-06  9:01 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-103913-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).