All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 212137] New: kernel NULL pointer dereference, black screen when using two graphics cards
Date: Mon, 08 Mar 2021 17:39:41 +0000	[thread overview]
Message-ID: <bug-212137-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 212137
           Summary: kernel NULL pointer dereference, black screen when
                    using two graphics cards
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: mail@dennisfoster.us
        Regression: No

Created attachment 295741
  --> https://bugzilla.kernel.org/attachment.cgi?id=295741&action=edit
lspci -vvv

On linux v5.11 and above (up to 5.11.4) I cannot longer boot the system
(GNOME/Wayland) using two graphics cards. It gets stuck with black screen with
no response to keyboard/mouse.

In systemd journal there are some messages about kernel bug:

Mar 08 11:54:05 homeserver kernel: BUG: kernel NULL pointer dereference,
address: 0000000000000008
Mar 08 11:54:05 homeserver kernel: #PF: supervisor read access in kernel mode
Mar 08 11:54:05 homeserver kernel: #PF: error_code(0x0000) - not-present page
Mar 08 11:54:05 homeserver kernel: PGD 0 P4D 0
Mar 08 11:54:05 homeserver kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Mar 08 11:54:05 homeserver kernel: CPU: 6 PID: 608 Comm: gnome-shell Tainted: G
OE 5.11.4-arch1-1 #1
Mar 08 11:54:05 homeserver kernel: Hardware name: Gigabyte Technology Co., Ltd.
A320M-S2H/A320M-S2H-CF, BIOS F2 11/03/2020
Mar 08 11:54:05 homeserver kernel: RIP:
0010:drm_gem_handle_create_tail+0xcb/0x190 [drm]
Mar 08 11:54:05 homeserver kernel: Code: 00 48 89 df e8 c6 20 59 f4 45 85 e4 78
77 48 8d 5d 18 4c 89 ee 48 89 df e8 42 fe 00 00 89 c2 85 c0 75 3e 48 8b 85 40
01 00 00 <48> 8b 40 08 48 85 c0 74 0f 4c 89 ee 48 89 ef e8 81 8b 91 f4 85 c0
Mar 08 11:54:05 homeserver kernel: RSP: 0018:ffffb7a7c16bfd30 EFLAGS: 00010246
Mar 08 11:54:05 homeserver kernel: RAX: 0000000000000000 RBX: ffffa0eabe065090
RCX: 0000000000000001


Everything works perfectly fine using current LTS v5.10.21.
I am using Radeon RX 470 as a primary card, and the older ATI FirePro 2270 as a
secondary one in order to provide two extra monitor outputs.

I've attached my lspci output as well as full systemd log.

-- 
You may reply to this email to add a comment.

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:[~2021-03-08 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 17:39 bugzilla-daemon [this message]
2021-03-08 17:40 ` [Bug 212137] kernel NULL pointer dereference, black screen when using two graphics cards bugzilla-daemon
2021-03-08 18:03 ` bugzilla-daemon
2021-03-08 19:18 ` bugzilla-daemon
2021-03-18 14:32 ` 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-212137-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.