https://bugs.freedesktop.org/show_bug.cgi?id=105883
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #13 from Joshua Lee ---
To be clear, the Furmark was being run in his host system, not within a VM.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #12 from Joshua Lee ---
Someone on the /r/VFIO discord with a Ryzen APU (he usually boots his VM from
the console, rather than having a graphical host) confirmed the crashiness by
running Furmark, which crashed
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #11 from taij...@posteo.de ---
(In reply to Joshua Lee from comment #3)
> How do I find an prior boot's dmesg?
Try "journalctl -b -1" (for the boot attempt directly prior to this one, -2 for
the one before that, etc...).
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #10 from taij...@posteo.de ---
And yes, Arch has had CONFIG_DRM_AMD_DC_DCN1_0=y since 4.15.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=105883
taij...@posteo.de changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #9 from taij...@posteo.de ---
This is possibly the same bug described in bug #105760.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #8 from Michel Dänzer ---
Is CONFIG_DRM_AMD_DC_DCN1_0 enabled in the kernel build configuration in both
cases?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #7 from Joshua Lee ---
I'm not sure where the kernel log is on arch. When I add that option to my
kernel command line that you recommended, both my drm-next-staging kernel and
4.16 mainline kernels fail. I have
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #6 from Harry Wentland ---
On Ubuntu the kernel log keeps appending to /var/log/kern.log, but that might
look different on different distros.
If you have a luxury of a second system you might be able to ssh
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #5 from Joshua Lee ---
(In reply to Edward Kigwana from comment #4)
> Try
>
> options amdgpu dpm=0 dc=1 and seee if it still locks up.
That's in /etc/modconf.d or the like, right?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #4 from Edward Kigwana ---
Try
options amdgpu dpm=0 dc=1 and seee if it still locks up.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #3 from Joshua Lee ---
How do I find an prior boot's dmesg?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #2 from Joshua Lee ---
Where is my kernel log located? I successfully use a 4.16 mainline kernel...
it's dri-next-staging that's causing problems. I am using mesa from git also...
though I don't know if it ever
https://bugs.freedesktop.org/show_bug.cgi?id=105883
--- Comment #1 from Alex Deucher ---
Can you attach your kernel log or dmesg output from the boot? Do other kernels
work?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105883
Bug ID: 105883
Summary: booting with kernel using amd-staging-drm-next on
2400G hangs
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux
16 matches
Mail list logo