All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204181] NULL pointer dereference regression in amdgpu
Date: Mon, 19 Aug 2019 13:39:26 +0000	[thread overview]
Message-ID: <bug-204181-2300-YnHgGnm4wE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204181-2300@https.bugzilla.kernel.org/>

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

--- Comment #33 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
I(In reply to Sergey Kondakov from comment #26)
> Created attachment 284083 [details]
> dmesg_2019-08-02-amdgpu_fail_on_patched_5.2.5
> 
> (In reply to Nicholas Kazlauskas from comment #24)
> > This should be fixed with the series linked below:
> > 
> > https://patchwork.freedesktop.org/series/64505/
> > 
> > But it still needs review and backporting to older kernels.
> 
> Celebration might have been premature. Hours later I've got another freeze
> with different error in amdgpu. Only this time, mouse cursor was movable
> over frozen frame right until I tried switching VT. Here's trace:
> BUG: unable to handle page fault for address: 0000000800000184
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0 
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 2 PID: 21044 Comm: kworker/u16:0 Tainted: G        W IO     
> 5.2.5-1396.g79b6a9c-HSF #1 openSUSE Tumbleweed (unreleased)
> Hardware name: Gigabyte Technology Co., Ltd. GA-990XA-UD3/GA-990XA-UD3, BIOS
> F14e 09/09/2014
> Workqueue: events_unbound commit_work
> RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2e6/0xd60 [amdgpu]

Are you able to consistently reproduce this issue? Is it the same setup and
same conditions as before? I haven't been able to see it in my testing at
least.

-- 
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

  parent reply	other threads:[~2019-08-19 13:39 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 10:11 [Bug 204181] New: NULL pointer dereference regression in amdgpu bugzilla-daemon
2019-07-15 13:07 ` [Bug 204181] " bugzilla-daemon
2019-07-15 15:43 ` bugzilla-daemon
2019-07-15 15:43 ` bugzilla-daemon
2019-07-15 15:45 ` bugzilla-daemon
2019-07-15 15:48 ` bugzilla-daemon
2019-07-15 15:50 ` bugzilla-daemon
2019-07-15 15:50 ` bugzilla-daemon
2019-07-15 15:53 ` bugzilla-daemon
2019-07-15 15:56 ` bugzilla-daemon
2019-07-15 15:58 ` bugzilla-daemon
2019-07-15 15:59 ` bugzilla-daemon
2019-07-16 15:29 ` bugzilla-daemon
2019-07-16 16:36 ` bugzilla-daemon
2019-07-16 16:52 ` bugzilla-daemon
2019-07-16 16:55 ` bugzilla-daemon
2019-07-24 18:33 ` bugzilla-daemon
2019-07-25 10:52 ` bugzilla-daemon
2019-07-25 14:21 ` bugzilla-daemon
2019-07-25 15:42 ` bugzilla-daemon
2019-07-25 15:50 ` bugzilla-daemon
2019-07-26 12:23 ` bugzilla-daemon
2019-07-26 16:02 ` bugzilla-daemon
2019-07-30 21:41 ` bugzilla-daemon
2019-07-31 16:28 ` bugzilla-daemon
2019-08-01  6:13 ` bugzilla-daemon
2019-08-02  2:21 ` bugzilla-daemon
2019-08-04  5:17 ` bugzilla-daemon
2019-08-07 17:43 ` bugzilla-daemon
2019-08-14  6:43 ` bugzilla-daemon
2019-08-14 19:06 ` bugzilla-daemon
2019-08-15 22:05 ` bugzilla-daemon
2019-08-17  5:13 ` bugzilla-daemon
2019-08-19 13:39 ` bugzilla-daemon [this message]
2019-08-19 15:11 ` bugzilla-daemon
2019-08-21 13:38 ` bugzilla-daemon
2019-08-21 14:37 ` bugzilla-daemon
2019-08-21 15:27 ` bugzilla-daemon
2019-08-21 18:36 ` bugzilla-daemon
2019-08-21 19:28 ` bugzilla-daemon
2019-08-21 21:39 ` bugzilla-daemon
2019-08-21 21:51 ` bugzilla-daemon
2019-08-22 13:14 ` bugzilla-daemon
2019-08-23 21:02 ` bugzilla-daemon
2019-08-24  9:43 ` bugzilla-daemon
2019-08-26  5:32 ` bugzilla-daemon
2019-09-04  4:50 ` bugzilla-daemon
2019-09-06 10:37 ` bugzilla-daemon
2019-09-06 10:38 ` bugzilla-daemon
2019-09-20  1:58 ` bugzilla-daemon
2019-09-20 13:19 ` bugzilla-daemon
2019-09-20 14:04 ` bugzilla-daemon
2019-09-21  5:26 ` bugzilla-daemon
2019-09-27  3:50 ` bugzilla-daemon
2019-09-27 12:50 ` bugzilla-daemon
2019-09-27 13:19 ` bugzilla-daemon
2019-09-27 20:18 ` bugzilla-daemon
2019-09-28  0:07 ` bugzilla-daemon
2019-09-29 18:10 ` bugzilla-daemon
2019-09-29 21:54 ` bugzilla-daemon
2019-09-30  2:07 ` bugzilla-daemon
2019-09-30  2:09 ` bugzilla-daemon
2019-11-05 19:38 ` bugzilla-daemon
2019-12-12 19:04 ` bugzilla-daemon
2020-06-19  3:13 ` bugzilla-daemon
2020-06-19  3:14 ` bugzilla-daemon
2020-07-26 22:49 ` bugzilla-daemon
2020-07-26 22:50 ` bugzilla-daemon
2022-11-10  4:02 ` bugzilla-daemon
2022-12-23  9:17 ` 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-204181-2300-YnHgGnm4wE@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.