From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109234] amdgpu random hangs with 4.21+
Date: Sun, 06 Jan 2019 20:50:19 +0000 [thread overview]
Message-ID: <bug-109234-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 6841 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109234
Bug ID: 109234
Summary: amdgpu random hangs with 4.21+
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: bmilreu@gmail.com
This bug happens for me like once a day, at seemingly random times with latest
kernel from torvalds tree. Last merge was yesterday
https://github.com/torvalds/linux/commit/0fe4e2d5cd931ad2ff99d61cfdd5c6dc0c3ec60b
but in the previous drm merge the bug was also present.
System: Host: mjb Kernel: 4.20.0-1-tkg-cfs x86_64 bits: 64 Desktop: KDE
Plasma 5.14.4 Distro: Manjaro Linux
Machine: Type: Desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x
serial: <root required>
UEFI: American Megatrends v: 0601 date: 10/29/2018
CPU: 6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 3885 MHz min/max:
1550/3900 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.3 driver: amdgpu resolution:
1920x1080~60Hz
OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0
4.21.0-torvaldsgit LLVM 8.0.0)
v: 4.5 Mesa 19.0.0-devel (git-8847370424)
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives: Local Storage: total: 1.59 TiB used: 283.09 GiB (17.3%)
Info: Processes: 262 Uptime: 6m Memory: 15.66 GiB used: 1.22 GiB (7.8%)
Shell: zsh inxi: 3.0.28
dmesg from previous boot always shows a trace like this:
jan 06 18:37:32 mjb kernel: general protection fault: 0000 [#1] PREEMPT SMP
NOPTI
jan 06 18:37:32 mjb kernel: CPU: 4 PID: 676 Comm: Xorg:cs0 Tainted: G
O 4.21.0-torvaldsgit #1
jan 06 18:37:32 mjb kernel: Hardware name: System manufacturer System Product
Name/TUF B450M-PLUS GAMING, BIOS 0601 10/29/2018
jan 06 18:37:32 mjb kernel: RIP: 0010:__memcpy+0x12/0x20
jan 06 18:37:32 mjb kernel: Code: 48 89 c8 e9 f9 fc ff ff 48 89 f0 e9 f1 fc ff
ff 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2
07 <f3> 48 a5 89 d1 f3 a4 c3 66>
jan 06 18:37:32 mjb kernel: RSP: 0018:ffffc9000327bc30 EFLAGS: 00010246
jan 06 18:37:32 mjb kernel: RAX: 0000a0050f003b80 RBX: ffff888105fdb0b0 RCX:
0000000000000200
jan 06 18:37:32 mjb kernel: RDX: 0000000000000000 RSI: ffff8880d3369000 RDI:
0000a0050f003b80
jan 06 18:37:32 mjb kernel: RBP: 0000000000000000 R08: 0000000000000000 R09:
00000000000001cc
jan 06 18:37:32 mjb kernel: R10: 0000000000000000 R11: ffff8883fa6a4828 R12:
0000000000001000
jan 06 18:37:32 mjb kernel: R13: 0000000000000000 R14: 00000000d3369000 R15:
ffff88840bf6fb28
jan 06 18:37:32 mjb kernel: FS: 00007fc0419a4700(0000)
GS:ffff88840eb00000(0000) knlGS:0000000000000000
jan 06 18:37:32 mjb kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 06 18:37:32 mjb kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 06 18:37:32 mjb kernel: CR2: 00007fa2d142d210 CR3: 0000000401080000 CR4:
00000000003406e0
jan 06 18:37:32 mjb kernel: Call Trace:
jan 06 18:37:32 mjb kernel: dma_direct_unmap_page+0x92/0xa0
jan 06 18:37:32 mjb kernel: ttm_unmap_and_unpopulate_pages+0x148/0x170 [ttm]
jan 06 18:37:32 mjb kernel: ttm_tt_destroy+0x81/0xd0 [ttm]
jan 06 18:37:32 mjb kernel: ttm_bo_put+0x25e/0x2f0 [ttm]
jan 06 18:37:32 mjb kernel: amdgpu_bo_unref+0x1a/0x30 [amdgpu]
jan 06 18:37:32 mjb kernel: amdgpu_gem_object_free+0x23/0x30 [amdgpu]
jan 06 18:37:32 mjb kernel: drm_gem_handle_delete+0x9b/0x130 [drm]
jan 06 18:37:32 mjb kernel: ? drm_gem_handle_create+0x40/0x40 [drm]
jan 06 18:37:32 mjb kernel: drm_ioctl_kernel+0x8b/0xd0 [drm]
jan 06 18:37:32 mjb kernel: drm_ioctl+0x1e5/0x390 [drm]
jan 06 18:37:32 mjb kernel: ? drm_gem_handle_create+0x40/0x40 [drm]
jan 06 18:37:32 mjb kernel: ? tlb_finish_mmu+0x1f/0x30
jan 06 18:37:32 mjb kernel: ? unmap_region+0xc9/0xf0
jan 06 18:37:32 mjb kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
jan 06 18:37:32 mjb kernel: do_vfs_ioctl+0x97/0x720
jan 06 18:37:32 mjb kernel: ? __do_munmap.constprop.9+0x263/0x3a0
jan 06 18:37:32 mjb kernel: __x64_sys_ioctl+0x62/0x90
jan 06 18:37:32 mjb kernel: do_syscall_64+0x55/0x100
jan 06 18:37:32 mjb kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
jan 06 18:37:32 mjb kernel: RIP: 0033:0x7fc04ba0580b
jan 06 18:37:32 mjb kernel: Code: 0f 1e fa 48 8b 05 55 b6 0c 00 64 c7 00 26 00
00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f
05 <48> 3d 01 f0 ff ff 73 01 c3>
jan 06 18:37:32 mjb kernel: RSP: 002b:00007fc0419a3968 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
jan 06 18:37:32 mjb kernel: RAX: ffffffffffffffda RBX: 0000562b657e9710 RCX:
00007fc04ba0580b
jan 06 18:37:32 mjb kernel: RDX: 00007fc0419a39a0 RSI: 0000000040086409 RDI:
000000000000000e
jan 06 18:37:32 mjb kernel: RBP: 00007fc0419a39a0 R08: 0000562b6333bc48 R09:
0000000000000007
jan 06 18:37:32 mjb kernel: R10: 0000000000000026 R11: 0000000000000246 R12:
0000000040086409
jan 06 18:37:32 mjb kernel: R13: 000000000000000e R14: 0000562b63390960 R15:
0000562b657e3fa0
jan 06 18:37:32 mjb kernel: Modules linked in: devlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter nf_tables nfnetlink edac_mce_amd
kvm_amd kvm irqbypass snd_hda_code>
jan 06 18:37:32 mjb kernel: ---[ end trace 28938eb196cb96ca ]---
jan 06 18:37:32 mjb kernel: RIP: 0010:__memcpy+0x12/0x20
jan 06 18:37:32 mjb kernel: Code: 48 89 c8 e9 f9 fc ff ff 48 89 f0 e9 f1 fc ff
ff 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2
07 <f3> 48 a5 89 d1 f3 a4 c3 66>
jan 06 18:37:32 mjb kernel: RSP: 0018:ffffc9000327bc30 EFLAGS: 00010246
jan 06 18:37:32 mjb kernel: RAX: 0000a0050f003b80 RBX: ffff888105fdb0b0 RCX:
0000000000000200
jan 06 18:37:32 mjb kernel: RDX: 0000000000000000 RSI: ffff8880d3369000 RDI:
0000a0050f003b80
jan 06 18:37:32 mjb kernel: RBP: 0000000000000000 R08: 0000000000000000 R09:
00000000000001cc
jan 06 18:37:32 mjb kernel: R10: 0000000000000000 R11: ffff8883fa6a4828 R12:
0000000000001000
jan 06 18:37:32 mjb kernel: R13: 0000000000000000 R14: 00000000d3369000 R15:
ffff88840bf6fb28
jan 06 18:37:32 mjb kernel: FS: 00007fc0419a4700(0000)
GS:ffff88840eb00000(0000) knlGS:0000000000000000
jan 06 18:37:32 mjb kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
jan 06 18:37:32 mjb kernel: CR2: 00007fa2d142d210 CR3: 0000000401080000 CR4:
00000000003406e0
lines 2853-2894/2894 (END)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 8251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-06 20:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 20:50 bugzilla-daemon [this message]
2019-01-07 3:33 ` [Bug 109234] amdgpu random hangs with 4.21+ bugzilla-daemon
2019-01-07 10:28 ` bugzilla-daemon
2019-01-07 17:56 ` bugzilla-daemon
2019-01-07 22:01 ` bugzilla-daemon
2019-01-07 23:32 ` bugzilla-daemon
2019-01-08 8:12 ` bugzilla-daemon
2019-01-08 15:15 ` bugzilla-daemon
2019-01-08 16:40 ` bugzilla-daemon
2019-01-08 17:01 ` bugzilla-daemon
2019-01-09 15:21 ` bugzilla-daemon
2019-01-09 15:22 ` bugzilla-daemon
2019-01-09 15:36 ` bugzilla-daemon
2019-01-10 17:51 ` [Bug 109234] amdgpu random hangs with 5.0-rc1/4.21+ bugzilla-daemon
2019-01-11 6:36 ` bugzilla-daemon
2019-01-11 6:38 ` bugzilla-daemon
2019-01-13 23:45 ` [Bug 109234] amdgpu random hangs with 5.0-rc2/4.21+ bugzilla-daemon
2019-01-14 3:38 ` bugzilla-daemon
2019-01-14 10:53 ` bugzilla-daemon
2019-01-14 19:33 ` bugzilla-daemon
2019-01-14 21:30 ` bugzilla-daemon
2019-01-15 8:15 ` bugzilla-daemon
2019-01-18 3:45 ` bugzilla-daemon
2019-01-18 3:47 ` bugzilla-daemon
2019-01-18 4:31 ` 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-109234-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.