From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200667] New: [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg
Date: Fri, 27 Jul 2018 11:54:34 +0000 [thread overview]
Message-ID: <bug-200667-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200667
Bug ID: 200667
Summary: [AMDGPU] stacktrace in dmesg, starting at
drm_dp_i2c_do_msg
Product: Drivers
Version: 2.5
Kernel Version: 4.17.10
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: CWidmer@umbrox.de
Regression: No
Created attachment 277569
--> https://bugzilla.kernel.org/attachment.cgi?id=277569&action=edit
Full dmesg output from kernel 4.18-r6
When I changed my kernel from 4.17.9 to 4.17.10 (both patched with the Gentoo
patchset), a stacktrace started to appear in the kernel messages. To check
whether this is still an issue in mainline and not related to the distribution
kernel, I tried 4.18-r6 which also shows the issue.
--
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:[~2018-07-27 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 11:54 bugzilla-daemon [this message]
2018-07-27 11:55 ` [Bug 200667] [AMDGPU] stacktrace in dmesg, starting at drm_dp_i2c_do_msg bugzilla-daemon
2018-07-27 11:56 ` bugzilla-daemon
2018-07-27 12:03 ` bugzilla-daemon
2018-07-27 14:41 ` bugzilla-daemon
2018-07-27 17:47 ` bugzilla-daemon
2018-07-27 17:55 ` bugzilla-daemon
2018-07-27 18:39 ` bugzilla-daemon
2018-10-22 21:14 ` 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-200667-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox