From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208997] New: WARNING: CPU: 3 PID: 1633 at drivers/gpu/drm/drm_modeset_lock.c
Date: Sat, 22 Aug 2020 16:04:24 +0000 [thread overview]
Message-ID: <bug-208997-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208997
Bug ID: 208997
Summary: WARNING: CPU: 3 PID: 1633 at
drivers/gpu/drm/drm_modeset_lock.c
Product: Drivers
Version: 2.5
Kernel Version: 5.8.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: martin.tk@gmx.com
Regression: No
Created attachment 292059
--> https://bugzilla.kernel.org/attachment.cgi?id=292059&action=edit
stack trace that's showing up in syslog
Since upgrading to 5.8.0 version I noticed a stack trace popping up in my
syslog. Actually, I haven't noticed it up until today.
I haven't noticed anything in my hardware behaviour. All seems to be working as
it used to.
The stack trace keeps appearing on up until 5.8.3.
I'm running Slackware current. I compiled the kernel myself, took it straight
from kernel.org.
Hardware:
CPU: Phenom2 x4 965
motherboard is included in the log: Gigabyte Technology Co., Ltd.
GA-MA770T-UD3/GA-MA770T-UD3
gpu: Radon RX550 (using kernel provided module).
Attached are a few examples of the stack trace. Going by the date, the first
few are on 5.8.0, the last are on 5.8.3.
Cheers.
Martin
ps. I'm not sure about the component.
--
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 reply other threads:[~2020-08-22 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 16:04 bugzilla-daemon [this message]
2020-08-24 13:04 ` [Bug 208997] WARNING: CPU: 3 PID: 1633 at drivers/gpu/drm/drm_modeset_lock.c bugzilla-daemon
2020-09-07 16:58 ` 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-208997-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.