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
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #1 from Richard Bradfield bradfirj@fstab.me --- Created attachment 116080 --> https://bugs.freedesktop.org/attachment.cgi?id=116080&action=edit lspci -nn
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #2 from Richard Bradfield bradfirj@fstab.me --- Created attachment 116081 --> https://bugs.freedesktop.org/attachment.cgi?id=116081&action=edit Oops stack trace only
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #3 from Richard Bradfield bradfirj@fstab.me --- Created attachment 116082 --> https://bugs.freedesktop.org/attachment.cgi?id=116082&action=edit Bisection log
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #4 from Richard Bradfield bradfirj@fstab.me --- Created attachment 116083 --> https://bugs.freedesktop.org/attachment.cgi?id=116083&action=edit Culprit commit according to bisect
Sorry for the bug-spam, I wasn't sure how to add many attachments at once.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #5 from Alex Deucher alexdeucher@gmail.com --- Created attachment 116085 --> https://bugs.freedesktop.org/attachment.cgi?id=116085&action=edit possible fix
Does the attached patch fix the issue?
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #6 from Alex Deucher alexdeucher@gmail.com --- Actually reverting the commit is probably the proper fix.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #7 from Richard Bradfield bradfirj@fstab.me --- Patch fixes the issue, I can try a revert as well.
With the patch applied, there's still a problem with gnome-shell crashing, but there's no Oops in the VT any more.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #8 from Richard Bradfield bradfirj@fstab.me --- (In reply to Alex Deucher from comment #6)
Actually reverting the commit is probably the proper fix.
Reverting the commit doesn't fix the issue, there is still a kernel Oops upon hotplugging the monitor. I'll dig into the trace.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #9 from Alex Deucher alexdeucher@gmail.com --- How about the revert and the patch?
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #10 from Richard Bradfield bradfirj@fstab.me --- (In reply to Alex Deucher from comment #9)
How about the revert and the patch?
Revert and patch is working for me.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #11 from Andreas Tunek andreas.tunek@gmail.com --- Is this fixed? I am asking because 91253 is probably due to the same committ.
https://bugs.freedesktop.org/show_bug.cgi?id=90681
Alex Deucher alexdeucher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #12 from Alex Deucher alexdeucher@gmail.com --- problematic commit reverted: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2d...
Fix committed: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fb...
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #13 from Andreas Tunek andreas.tunek@gmail.com --- Will this be in 4.2 rc3?
https://bugs.freedesktop.org/show_bug.cgi?id=90681
--- Comment #14 from Alex Deucher alexdeucher@gmail.com --- (In reply to Andreas Tunek from comment #13)
Will this be in 4.2 rc3?
Yes, they are in 4.1 as well.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org