From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216840] New: AMDGPU trace message at boot
Date: Fri, 23 Dec 2022 22:02:35 +0000 [thread overview]
Message-ID: <bug-216840-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216840
Bug ID: 216840
Summary: AMDGPU trace message at boot
Product: Drivers
Version: 2.5
Kernel Version: 6.1.0
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: carlosalvatore@gmail.com
Regression: No
Hi,
I don't know whether this is important, but I'd like to know what is causing
this trace message: https://pastebin.pl/view/94557be6 when booting.
Hardware details:
- MB: ASUS M5A97 R2.0
- CPU: AMD FX-8350
- Kernel: 6.1.0
- GPU: Radeon HD 7970 (Tahiti) [Gigabyte GV-R797OC-3GD]
There are no critical problems when using the system. Other than HDMI port not
working anymore (I don't know if this is related. At some point HDMI stopped
working and I've got this message: "drm:detect_link_and_local_sink [amdgpu]]
*ERROR* No EDID read.", which I bypassed using a HDMI>DP adapter).
GRUB command line arguments are:
amdgpu.si_support=1 radeon.si_support=0 modprobe.blacklist=radeon
amdgpu.vm_update_mode=3 amdgpu.dpm=1 amdgpu.dc=1 amd_iommu=on iommu=pt
video=DisplayPort-0:edid/1204x800.bin
Regards.
--
CarloSalvatore
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-12-23 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 22:02 bugzilla-daemon [this message]
2022-12-24 18:47 ` [Bug 216840] AMDGPU trace message at boot bugzilla-daemon
2022-12-27 16:45 ` bugzilla-daemon
2022-12-30 0:28 ` bugzilla-daemon
2022-12-30 0:37 ` 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-216840-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.