From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214859] New: drm-amdgpu-init-iommu~fd-device-init.patch introduce bug
Date: Thu, 28 Oct 2021 18:23:07 +0000 [thread overview]
Message-ID: <bug-214859-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214859
Bug ID: 214859
Summary: drm-amdgpu-init-iommu~fd-device-init.patch introduce
bug
Product: Drivers
Version: 2.5
Kernel Version: 5.14.15
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: towo@siduction.org
Regression: No
After commit d60096b3b2c2..cd8cc7d31b49 100644
drm-amdgpu-init-iommu~fd-device-init.patch
Kernel 5.14.15 on most Ryzen Notebooks X cant't start really.
There is a long time, before x is starting, dmesg is spammed with failure
messages like
Okt 28 10:28:08 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 28b4 wait reg 28c6
Okt 28 10:28:21 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 1a6f4 wait reg 1a706
Okt 28 10:28:34 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 28b4 wait reg 28c6
Okt 28 10:28:47 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 1a6f4 wait reg 1a706
Okt 28 10:29:01 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 28b4 wait reg 28c6
Okt 28 10:29:14 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 1a6f4 wait reg 1a706
Okt 28 10:29:27 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 28b4 wait reg 28c6
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write
reg 1a6f4 wait reg 1a706
and/or
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: [gfxhub0]
no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process pid 0
thread pid 0)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: in page
starting at address 0x0000000000872000 from IH client 0x1b (UTCL2)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00040D00
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: Faulty
UTCL2 client ID: CPG (0x6)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
MORE_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
WALKER_ERROR: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
PERMISSION_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
MAPPING_ERROR: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: RW: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: [gfxhub0]
no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process pid 0
thread pid 0)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: in page
starting at address 0x0000000000872000 from IH client 0x1b (UTCL2)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
VM_L2_PROTECTION_FAULT_STATUS:0x00040D00
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: Faulty
UTCL2 client ID: CPG (0x6)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
MORE_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
WALKER_ERROR: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
PERMISSION_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:
MAPPING_ERROR: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: RW: 0x1
Reverting that commit and the kernel is back working normal.
Here the related reports from our users (ignore the nvidia posts).
https://forum.siduction.org/index.php?topic=8439.0
--
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:[~2021-10-28 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 18:23 bugzilla-daemon [this message]
2021-10-31 9:46 ` [Bug 214859] drm-amdgpu-init-iommu~fd-device-init.patch introduce bug bugzilla-daemon
2021-11-01 19:42 ` bugzilla-daemon
2021-11-01 19:44 ` bugzilla-daemon
2021-11-01 20:05 ` bugzilla-daemon
2021-11-02 20:30 ` bugzilla-daemon
2021-11-03 1:46 ` bugzilla-daemon
2021-11-03 14:29 ` bugzilla-daemon
2021-11-04 16:55 ` bugzilla-daemon
2021-11-17 16:38 ` 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-214859-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