All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210739] New: Regression in 5.10, Oops at amdgpu_connector_dp_detect()
Date: Thu, 17 Dec 2020 00:21:20 +0000	[thread overview]
Message-ID: <bug-210739-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=210739

            Bug ID: 210739
           Summary: Regression in 5.10, Oops at
                    amdgpu_connector_dp_detect()
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.10
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: bugs-a17@moonlit-rail.com
        Regression: Yes

Created attachment 294169
  --> https://bugzilla.kernel.org/attachment.cgi?id=294169&action=edit
dmesg from where X11 initializes

Booting into mainline 5.10.1 oopses in the amdgpu module in the routine
amdgpu_connector_dp_detect().  Kernels 5.9.15 and below are not affected.

Full dmesg attached.  Brief snippet of oops:
    BUG: kernel NULL pointer dereference, address: 0000000000000060
    Call Trace:
     amdgpu_connector_dp_detect+0x159/0x320 [amdgpu]
     drm_helper_probe_detect+0x93/0xd0
     drm_helper_probe_single_connector_modes+0x60c/0x7e0
     drm_client_modeset_probe+0x25c/0x13c0
[etc]

The GPU is inbuilt within the AMD A10-7870K (Radeon R7).
At system start:
    modprobe amdgpu clk_support=1
    modprobe radeon clk_support=0
Console output seems to be OK during system initialization.  But as soon as
Xorg starts, the oops occurs, and video output ceases.  System is still
responsive via the network.

The oops locks the video hardware spectacularly.  Neither the BIOS nor pressing
the motherboard <reset> button has any effect.  Only a power-cycle will get
things back to normal.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-12-17  0:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  0:21 bugzilla-daemon [this message]
2020-12-17  3:17 ` [Bug 210739] Regression in 5.10, Oops at amdgpu_connector_dp_detect() bugzilla-daemon
2020-12-17  3:18 ` bugzilla-daemon
2020-12-17  3:19 ` bugzilla-daemon
2020-12-17  9:18 ` bugzilla-daemon
2020-12-17 17:24 ` bugzilla-daemon
2020-12-17 21:45 ` bugzilla-daemon
2020-12-18  0:18 ` bugzilla-daemon
2020-12-26 22:08 ` 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-210739-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.