|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel crash in the logs when exiting / shutting down the system | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Stakanov Schufter <stakanov> |
| Component: | Kernel | Assignee: | openSUSE Kernel Bugs <kernel-bugs> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jslaby, os, patrik.jakobsson, stakanov, tiwai, tzimmermann |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stakanov Schufter
2021-12-06 08:30:15 UTC
Is it a regression since the recent kernel update? Or did you get it in the earlier kernels? And, please upload the full dmesg output. In anyway, it's a DRM problem, Ccing relevant people. I went back to the very fist log (130 boots) as far as September 23. It may be the reason why I have two bugs for mesa open? Anyway: Sep 23 23:55:42 localhost kernel: show_signal: 49 callbacks suppressed Sep 23 23:55:42 localhost kernel: traps: gajim[2244] trap int3 ip:7fb62475fadf sp:7ffc8d659990 error:0 in libglib-2.0.so.0.6800.4[7fb624720000+8b000] Sep 23 23:55:53 localhost kernel: ------------[ cut here ]------------ Sep 23 23:55:53 localhost kernel: WARNING: CPU: 2 PID: 1709 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x2da/0x300 [ttm] Sep 23 23:55:53 localhost kernel: Modules linked in: rfcomm nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib> Sep 23 23:55:53 localhost kernel: snd_intel_dspcfg snd_intel_sdw_acpi i2c_mux efi_pstore k10temp fam15h_power videobuf2_dma_sg raid1 snd_hda_codec videobuf2_memops> Sep 23 23:55:53 localhost kernel: CPU: 2 PID: 1709 Comm: Xorg.bin Not tainted 5.14.0-1-default #1 openSUSE Tumbleweed 050795c50c64a4b2532121eca878f6869ea43f27 Sep 23 23:55:53 localhost kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./970A-UD3P, BIOS F2g 10/07/2014 Sep 23 23:55:53 localhost kernel: RIP: 0010:ttm_bo_release+0x2da/0x300 [ttm] Sep 23 23:55:53 localhost kernel: Code: 8d b5 b8 fe ff ff e8 05 90 e8 ff 48 8b 75 08 4c 89 e7 e8 c9 23 00 00 48 8b 7d 98 e9 64 fd ff ff e8 9b 3b ad cf e9 95 fd ff f> Sep 23 23:55:53 localhost kernel: RSP: 0018:ffffb66c01737d20 EFLAGS: 00010202 Sep 23 23:55:53 localhost kernel: RAX: 0000000000000001 RBX: ffffb66c01737d60 RCX: 0000000000000000 Sep 23 23:55:53 localhost kernel: RDX: 0000000000000002 RSI: ffff8f7d1438cab8 RDI: ffff8f7d2e2115d8 Sep 23 23:55:53 localhost kernel: RBP: ffff8f7d2e2115d8 R08: ffff8f7d2e2115d8 R09: 0000000000000064 Sep 23 23:55:53 localhost kernel: R10: 0000000000000010 R11: ffff8f7d33cf9d10 R12: ffff8f7c4277c6f0 Sep 23 23:55:53 localhost kernel: R13: ffff8f7d2e211478 R14: ffff8f7d422679c0 R15: ffff8f7cc4330c78 Sep 23 23:55:53 localhost kernel: FS: 00007f15c5c03940(0000) GS:ffff8f835ed00000(0000) knlGS:0000000000000000 Sep 23 23:55:53 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 23 23:55:53 localhost kernel: CR2: 00007f15b5b7240c CR3: 00000004d5610000 CR4: 00000000000406e0 Sep 23 23:55:53 localhost kernel: Call Trace: Sep 23 23:55:53 localhost kernel: radeon_bo_unref+0x1a/0x30 [radeon 319ae925f08af35efa8a83676e342b2b1b9dca25] Sep 23 23:55:53 localhost kernel: radeon_gem_object_free+0x30/0x50 [radeon 319ae925f08af35efa8a83676e342b2b1b9dca25] Sep 23 23:55:53 localhost kernel: drm_gem_dmabuf_release+0x36/0x50 [drm 74f50b2b4b79fb70a1f137dc23e4ae01c9ac78dd] Sep 23 23:55:53 localhost kernel: dma_buf_release+0x3a/0x80 Sep 23 23:55:53 localhost kernel: __dentry_kill+0xfa/0x170 Sep 23 23:55:53 localhost kernel: __fput+0xe3/0x240 Sep 23 23:55:53 localhost kernel: task_work_run+0x65/0xa0 Sep 23 23:55:53 localhost kernel: do_exit+0x34d/0xa10 Sep 23 23:55:53 localhost kernel: do_group_exit+0x33/0xa0 Sep 23 23:55:53 localhost kernel: __x64_sys_exit_group+0x14/0x20 Sep 23 23:55:53 localhost kernel: do_syscall_64+0x5c/0x80 Sep 23 23:55:53 localhost kernel: ? handle_mm_fault+0xcf/0x2a0 Sep 23 23:55:53 localhost kernel: ? do_user_addr_fault+0x1d5/0x670 Sep 23 23:55:53 localhost kernel: ? asm_exc_page_fault+0x8/0x30 Sep 23 23:55:53 localhost kernel: ? exit_to_user_mode_prepare+0x19b/0x230 Sep 23 23:55:53 localhost kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 23 23:55:53 localhost kernel: RIP: 0033:0x7f15c546d031 Sep 23 23:55:53 localhost kernel: Code: Unable to access opcode bytes at RIP 0x7f15c546d007. Sep 23 23:55:53 localhost kernel: RSP: 002b:00007fff75514828 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 Sep 23 23:55:53 localhost kernel: RAX: ffffffffffffffda RBX: 00007f15c5565470 RCX: 00007f15c546d031 Sep 23 23:55:53 localhost kernel: RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 Sep 23 23:55:53 localhost kernel: RBP: 0000000000000000 R08: fffffffffffffd80 R09: 0000000000000000 Sep 23 23:55:53 localhost kernel: R10: 00007f15c4cc0730 R11: 0000000000000246 R12: 00007f15c5565470 Sep 23 23:55:53 localhost kernel: R13: 000000000000082d R14: 00007f15c5565948 R15: 0000000000000000 Sep 23 23:55:53 localhost kernel: ---[ end trace 6910ddd5b4d2c0cd ]--- So goes back at least to September 23. If there is a way to open archived journals I may well remount even further. You may educate me. Thanks. I guess the best would be to report it to the upstream gitlab.freedesktop.org Issues. Although AMD people tend to see any radeon driver issue in a lower priority, it's still worth to try. Maybe baffling ignorance of my part, but: what do I need to do this, is there a registering process and then I report or how does it work? Would spare me a lot of time to know how to reach the right place in the right way. If you have any knowledge about it, I would be uttermost pleased if you could share it. I have zero experience with git Thank you for your patience. (In reply to Stakanov Schufter from comment #4) > Maybe baffling ignorance of my part, but: what do I need to do this, is > there a registering process and then I report or how does it work? I guess you'd need to register yourself in gitlab.freedesktop.org, yes. The URL to report is: https://gitlab.freedesktop.org/drm/amd/-/issues > Would spare me a lot of time to know how to reach the right place in the > right way. If you have any knowledge about it, I would be uttermost pleased > if you could share it. > I have zero experience with git It's basically independent from git, rather a bug tracker hosted on gitlab. The UI is somewhat similar as github issue reporting, and should be easy to navigate. You can mention the openSUSE Bugzilla entry as a reference, of course. I'm afraid there is a little we can do about this, provided this is an upstream bug and noone in upstream cared to fix this quite yet. |