From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211161] list_del corruption in ttm_pool_shrink
Date: Wed, 13 Jan 2021 02:11:52 +0000 [thread overview]
Message-ID: <bug-211161-2300-E2fwBmxZUG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211161-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211161
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Benji Wiebe from comment #0)
> Created attachment 294611 [details]
> kernel BUG dmesg 1
>
> I've been getting occasional graphics lockups, fixable only by reboot. I was
> hard rebooting until I realized I could ssh in to my desktop still, so here
> are two dmesg logs that I've captured. There's also a report of (I think)
> this same bug in the LKML: https://lkml.org/lkml/2020/12/31/47
If it's the same issue, it's fixed with these patches:
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=e0658f970a7f3d85431c6803b7d5169444fb11b0
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-fixes&id=a73858ef4d5e1d425e171f0f6a52864176a6a979
--
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
next prev parent reply other threads:[~2021-01-13 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 0:44 [Bug 211161] New: list_del corruption in ttm_pool_shrink bugzilla-daemon
2021-01-13 0:45 ` [Bug 211161] " bugzilla-daemon
2021-01-13 2:11 ` bugzilla-daemon [this message]
2021-01-13 2:24 ` bugzilla-daemon
2021-01-19 18:15 ` 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-211161-2300-E2fwBmxZUG@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox