dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216549] New: AMDGPU crash with kernel NULL pointer dereference,  RIP: 0010:amdgpu_bo_get_memory
Date: Sun, 02 Oct 2022 16:17:48 +0000	[thread overview]
Message-ID: <bug-216549-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216549
           Summary: AMDGPU crash with kernel NULL pointer dereference,
                    RIP: 0010:amdgpu_bo_get_memory
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.19.12
          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: bxkx@duck.com
        Regression: No

Created attachment 302142
  --> https://bugzilla.kernel.org/attachment.cgi?id=302142&action=edit
Journal log of the error

I experienced this GPU crash. I couldn't find any info about the first call
trace on the internet, though.



The monitor output froze, system still running, I tried to switch TTY and it
changed the output but froze/couldn't do anything. System looks like it kept
running until I hit the reset button, logged until the end.

I'm using a RX 6600

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

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-10-02 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02 16:17 bugzilla-daemon [this message]
2022-10-02 22:03 ` [Bug 216549] AMDGPU crash with kernel NULL pointer dereference, RIP: 0010:amdgpu_bo_get_memory 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-216549-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox