https://bugs.freedesktop.org/show_bug.cgi?id=106225
Michel Dänzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #37 from Francisco Pina Martins ---
Confirming that the issue seems to be solved with mainline linux-4.19-rc[1,2].
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #36 from Andrea Vettorello ---
With recent development kernels from https://cgit.freedesktop.org/~agd5f/
(drm-next-4.19-wip, I think commit ddf74e79a54070f277ae520722d3bab7f7a6c67a) I
can consistently complete cold/warm boot on my 24
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #35 from Andrea Vettorello ---
Sorry for the spam, I thought the two attachments would be inserted in the same
comment.
I think I'm afflicted by the same bug on different HW (Asrock AB350 ixt, Ryzen
5 2400G), Debian Stretch running
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #34 from Andrea Vettorello ---
Created attachment 140597
--> https://bugs.freedesktop.org/attachment.cgi?id=140597&action=edit
relevant kernel 4.17.5 source of the oops
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #33 from Andrea Vettorello ---
Created attachment 140596
--> https://bugs.freedesktop.org/attachment.cgi?id=140596&action=edit
relevant kernel 4.17.5 log of the oops
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #32 from Luca ---
Happens to me too (kernel 4.17 ubuntu 18.04), especially the first boot of the
day I always get black screen after modeset. I haven't tried with KASAN and
can't get any log but I suspect is the same issue.
Asrock a
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #31 from Francisco Pina Martins ---
I have used [this
PKGBUILD](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-amd-staging-drm-next-git)
to build the kernel.
Albeit considering the version number it looks more like linu
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #30 from Jerry Zuo ---
The commit on amd-staging-drm-next I checked out for verification is:
Author: Shaoyun Liu
AuthorDate: Tue May 22 11:45:41 2018 -0400
Commit: Alex Deucher
CommitDate: Thu May 24 10:28:35 2018 -0500
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #29 from Francisco Pina Martins ---
Created attachment 139779
--> https://bugs.freedesktop.org/attachment.cgi?id=139779&action=edit
journaltcl log file for linux-amd-staging-drm-next
I was able to compile the "amd-staging-drm-next
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #28 from Francisco Pina Martins ---
Currently "amd-staging-drm-next" fails to build for me, with the following
error:
```
../lib/str_error_r.c: In function ‘str_error_r’:
../lib/str_error_r.c:25:3: error: passing argument 1 to restr
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #27 from Jerry Zuo ---
The issue could get reproduced on 4.16.3, but not on 4.16-rc7.
I've verified the commit a0f282dcdb1775cbcc0a151570fc01c0aae5ca0f (current top)
on amd-staging-drm-next without seeing the issue on Raven by havi
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #26 from Michel Dänzer ---
(In reply to Francisco Pina Martins from comment #25)
> Is there anything else I can do here to help track the eventual problem with
> AMDGPU? Or do you think the AMDGPU memory problem is being caused by
>
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #25 from Francisco Pina Martins ---
I have submitted the bug to kernel bugzilla as you have suggested:
https://bugzilla.kernel.org/show_bug.cgi?id=199613
Is there anything else I can do here to help track the eventual problem with
A
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #24 from Michel Dänzer ---
(In reply to Francisco Pina Martins from comment #23)
> [...] should this issue be filed somewhere else then?
> If yes, where,
I'm not sure. :( Maybe start with memory management (https://www.linux-mm.org/
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #23 from Francisco Pina Martins ---
This is a bit out of my league... but should this issue be filed somewhere else
then?
If yes, where, and what information should I provide?
Also, is there a possibility that there are multiple issu
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #22 from Michel Dänzer ---
It still says the memory is freed from rcu_cpu_kthread. Weird. It's not clear
this actually is an amdgpu issue.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #21 from Francisco Pina Martins ---
Created attachment 139288
--> https://bugs.freedesktop.org/attachment.cgi?id=139288&action=edit
journalctl log with KASAN_OUTLINE and kasan_multi_shot using a kernel compiled
with debug info
Ok,
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #20 from Michel Dänzer ---
Now I notice there's another report for firmware_parser_create+0xa9b/0xd90.
What does faddr2line say for that?
Though it's weird that KASAN claims the memory written in
firmware_parser_create was freed fro
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #19 from Francisco Pina Martins ---
Created attachment 139239
--> https://bugs.freedesktop.org/attachment.cgi?id=139239&action=edit
journalctl log with KASAN_OUTLINE and kasan_multi_shot using amdgpu.ko compiled
with debug info
He
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #18 from Michel Dänzer ---
(In reply to Francisco Pina Martins from comment #17)
> Will it work if I just replace the amdgpu.ko file with the debug-enabled
> version?
Yeah, that could work. If it doesn't, then it's not a big deal, i
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #17 from Francisco Pina Martins ---
I don't think I'll be able to test that, since The kernel with debug enabled
weights in at 590Mb, which is larger than my 512Mb /boot partition.
Will it work if I just replace the amdgpu.ko file wi
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #16 from Michel Dänzer ---
That does look helpful, thanks! I'll leave it to the DC folks to take it from
here.
Francisco, just one more thing: Can you double-check that KASAN still reports
firmware_parser_create+0xa70/0xd90 with the
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #15 from Francisco Pina Martins ---
Here you go:
francisco@ZenBox [11:13:37] [/tmp/build/linux-kasan/src/linux-4.16]
-> $ scripts/faddr2line drivers/gpu/drm/amd/amdgpu/amdgpu.ko
firmware_parser_create+0xa70/0xd90
firmware_parser_cr
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #14 from Francisco Pina Martins ---
francisco@ZenBox [10:31:49] [~]
-> $ file
/usr/lib/modules/4.16.5-1-kasan/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
/usr/lib/modules/4.16.5-1-kasan/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko:
E
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #13 from Michel Dänzer ---
(In reply to Francisco Pina Martins from comment #12)
> francisco@ZenBox [18:12:53] [/usr/lib/modules/4.16.5-1-kasan/build]
> -> $ scripts/faddr2line ../kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
> firmwa
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #12 from Francisco Pina Martins ---
francisco@ZenBox [18:03:53] [/usr/lib/modules/4.16.5-1-kasan/build]
-> $ scripts/faddr2line drivers/gpu/drm/amd/amdgpu/amdgpu.ko
firmware_parser_create+0xa70/0xd90
ERROR: can't find objfile driver
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #11 from Michel Dänzer ---
Please provide the output of the following in your kernel build tree:
scripts/faddr2line drivers/gpu/drm/amd/amdgpu/amdgpu.ko
firmware_parser_create+0xa70/0xd90
--
You are receiving this mail because:
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Francisco Pina Martins changed:
What|Removed |Added
Attachment #139178|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #9 from Michel Dänzer ---
Getting closer, please try again with kasan_multi_shot on the kernel command
line, otherwise KASAN only reports the first thing it catches.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Francisco Pina Martins changed:
What|Removed |Added
Attachment #139154|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #7 from Francisco Pina Martins ---
I had previously made a mistake in loading the kernel's .config file.
I have now managed to compile the kernel with the options for KASAN set.
However, booting this kernel results in an instant rebo
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #6 from Michel Dänzer ---
Looks like KASAN isn't enabled yet — the lines in dmesg containing "PREEMPT SMP
NOPTI" should contain "KASAN" as well.
FWIW, I just enable CONFIG_KASAN and CONFIG_KASAN_INLINE in .config, I don't
have to do
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #5 from Francisco Pina Martins ---
Created attachment 139154
--> https://bugs.freedesktop.org/attachment.cgi?id=139154&action=edit
journaltcl log file with KASAN enabled in kernel
I have compiled a new kernel with KASAN module ena
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #4 from Michel Dänzer ---
Maybe you can try enabling KASAN and see if that catches anything earlier.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com
--- Comment #3 f
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Francisco Pina Martins changed:
What|Removed |Added
Attachment #139081|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #1 from Michel Dänzer ---
The journalctl log file shows oopses from the evdev driver, no obvious amdgpu
related issues.
Can you attach a picture of the output from the actual kernel panic?
--
You are receiving this mail because:
Y
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Bug ID: 106225
Summary: Kernel panic after modesetting (not on every boot) on
ryzen 5 2400g
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS:
39 matches
Mail list logo
