From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209129] HW related error message under Gnome important tab
Date: Thu, 03 Sep 2020 09:49:07 +0000 [thread overview]
Message-ID: <bug-209129-2300-KTq1UWEvce@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209129-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209129
Borislav Petkov (bp@alien8.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|x86-64 |Video(DRI - non Intel)
Assignee|platform_x86_64@kernel-bugs |drivers_video-dri@kernel-bu
|.osdl.org |gs.osdl.org
Product|Platform Specific/Hardware |Drivers
--- Comment #11 from Borislav Petkov (bp@alien8.de) ---
Hmm, so it looks like that GpuWatchdog thing is chrome thread. And the error in
your dmesg before it:
[ 266.208179] [TTM] Buffer eviction failed
[ 266.346883] GpuWatchdog[2984]: segfault at 0 ip
says that a buffer eviction in the TTM fails which probably causes the watchdog
to segfault. In any case, this is a DRM issue, not a platform one.
Reassigning...
What you could do for starters is try the latest kernel 5.8 to check whether
this has been fixed in the meantime.
HTH.
--
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 parent reply other threads:[~2020-09-03 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209129-2300@https.bugzilla.kernel.org/>
2020-09-03 9:49 ` bugzilla-daemon [this message]
2020-09-03 10:27 ` [Bug 209129] HW related error message under Gnome important tab bugzilla-daemon
2020-09-03 10:59 ` bugzilla-daemon
2020-09-03 11:28 ` bugzilla-daemon
2020-11-01 15:46 ` bugzilla-daemon
2023-12-08 8:00 ` 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-209129-2300-KTq1UWEvce@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.