All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111659] Kernel panic when waking up after screens go to dpms sleep
Date: Wed, 11 Sep 2019 11:39:00 +0000	[thread overview]
Message-ID: <bug-111659-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111659
           Summary: Kernel panic when waking up after screens go to dpms
                    sleep
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: not set
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: brad@fnarfbargle.com

Created attachment 145332
  --> https://bugs.freedesktop.org/attachment.cgi?id=145332&action=edit
Multiple instances of the Panic

iMac late 2011 with 2 Thunderbolt displays.

Kernel 5.2 finally got DP routing working to allow both TB displays to work,
however I'm now getting lockups which appear to be triggered in  
radeon_dp_needs_link_train.

I'm capturing these over netconsole as it leaves the machine paralysed.

Attachment faults.txt has 4 separate instances of the fault from 4 different
boots.

This machine stays on 24/7 and this seems to occur when the displays wake up
after a dpms sleep. Having said that I've also seen the fault when doing
something innocuous like changing the audio volume.

Generally at least 2 of the screens wakeup, so I have displays with a
lockscreen asking for a password and a mouse, but the machine is dead. 

The last example in faults.txt left the machine in a state where I could ssh in
and reboot it. All the others required a hard power cycle.

I'm currently using 5.2.11. Previously I was using 4.17, but I can't roll back
prior to 5.2 without losing the second TB display, and it can take hours or
days to hit so bisection would be difficult.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Blackcomb [Radeon HD 6970M/6990M] (prog-if 00 [VGA controller])
        Subsystem: Apple Inc. Radeon HD 6970M
        Flags: bus master, fast devsel, latency 0, IRQ 79
        Memory at 90000000 (64-bit, prefetchable) [size=256M]
        Memory at a8800000 (64-bit, non-prefetchable) [size=128K]
        I/O ports at 2000 [size=256]
        Expansion ROM at a8820000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
        Capabilities: [150] Advanced Error Reporting
        Kernel driver in use: radeon
        Kernel modules: radeon

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

[-- Attachment #1.2: Type: text/html, Size: 4131 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

             reply	other threads:[~2019-09-11 11:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 11:39 bugzilla-daemon [this message]
2019-09-11 11:39 ` [Bug 111659] Kernel panic when waking up after screens go to dpms sleep bugzilla-daemon
2019-09-11 11:39 ` bugzilla-daemon
2019-09-11 14:26 ` bugzilla-daemon
2019-09-26  3:51 ` bugzilla-daemon
2019-09-26  4:43 ` bugzilla-daemon
2019-10-28  8:14 ` bugzilla-daemon
2019-10-28 11:57 ` bugzilla-daemon
2019-10-31  7:42 ` bugzilla-daemon
2019-11-19  0:30 ` bugzilla-daemon
2019-11-19  8:02 ` bugzilla-daemon
2019-11-19  9:35 ` 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-111659-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.