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 90681] Radeon Kernel Oops & Lockup when switching on DisplayPort attached monitor
Date: Wed, 27 May 2015 14:14:42 +0000	[thread overview]
Message-ID: <bug-90681-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 90681
           Summary: Radeon Kernel Oops & Lockup when switching on
                    DisplayPort attached monitor
           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: bradfirj@fstab.me

Created attachment 116079
  --> https://bugs.freedesktop.org/attachment.cgi?id=116079&action=edit
journalctl output for crash

Switching my DisplayPort attached monitor on (or off and then on again) while
booted to multiuser target (no Xorg or Wayland) causes a kernel Oops, followed
by soft-lockups which render the system unusable.

Doing the same while at the full Graphical target causes gnome-shell to crash,
but it is possible to recover the system by logging in again.

The kernel error and IP are:
>May 24 23:25:28 fedora-workstation.home kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000003b0
>May 24 23:25:28 fedora-workstation.home kernel: IP: [<ffffffffa0152055>] radeon_connector_edid+0x5/0x70 [radeon]

Full journal from a reproduction of the bug will be attached, as will lspci
-nn.

I have isolated this using git bisect to the following commit (the patch for
which is attached to this bug).
This is a commit currently part of the linux-stable tree and lies between 4.0.2
and 4.0.3

>016a255b7835ee7e49a3eba3c14ba0bc0221a4f8 is the first bad commit
>commit 016a255b7835ee7e49a3eba3c14ba0bc0221a4f8
>Author: Alex Deucher <alexander.deucher@amd.com>
>Date:   Tue Apr 7 09:52:42 2015 -0400
>
>    drm/radeon: only mark audio as connected if the monitor supports it (v3)
>    
>    commit 0f55db36d49d45b80eff0c0a2a498766016f458b upstream.
>    
>    Otherwise the driver may try and send audio which may confuse the
>    monitor.
>    
>    v2: set pin to NULL if no audio
>    v3: avoid crash with analog encoders
>    
>    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>>
>
>:040000 040000 de0366a6790f5c91d175bcb89cb34956bbe72b26 >bbdb5734961f824558152c7c34a840c78bc3a9a9 M	drivers

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

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

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

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

             reply	other threads:[~2015-05-27 14:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 14:14 bugzilla-daemon [this message]
2015-05-27 14:15 ` [Bug 90681] Radeon Kernel Oops & Lockup when switching on DisplayPort attached monitor bugzilla-daemon
2015-05-27 14:15 ` bugzilla-daemon
2015-05-27 14:16 ` bugzilla-daemon
2015-05-27 14:17 ` bugzilla-daemon
2015-05-27 15:37 ` bugzilla-daemon
2015-05-27 15:59 ` bugzilla-daemon
2015-05-27 16:05 ` bugzilla-daemon
2015-05-27 17:08 ` bugzilla-daemon
2015-05-27 17:14 ` bugzilla-daemon
2015-05-27 18:02 ` bugzilla-daemon
2015-07-20 17:58 ` bugzilla-daemon
2015-07-20 18:54 ` bugzilla-daemon
2015-07-21 19:37 ` bugzilla-daemon
2015-07-21 19:41 ` 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-90681-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).