https://bugs.freedesktop.org/show_bug.cgi?id=98987
Bug ID: 98987 Summary: [RS690] BUG: soft lockup when radeon modesetting Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: high Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: vaclav.ovsik@gmail.com
Created attachment 128323 --> https://bugs.freedesktop.org/attachment.cgi?id=128323&action=edit logged using netconsole - kernel 4.8.7 (Debian kernel)
Dear developers, I'm unable to boot into functional system with KMS radeon. When radeon.modeset=0 on kernel command-line system it starts and run OK. Without disabled modeset the kernel 4.7, 4.8, 4.9-rc7 with 90% probability locks or crash. I'm running Debian unstable and tried Debian kernels 4.7, 4.8 from Debian and compile 4.9rc7 vanilla kernel.
Attached logs through netconsole.
Any idea what I can test?
Thanks
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #1 from Václav Ovsík vaclav.ovsik@gmail.com --- Created attachment 128324 --> https://bugs.freedesktop.org/attachment.cgi?id=128324&action=edit logged using netconsole - 4.8.7 - soft lockup
https://bugs.freedesktop.org/show_bug.cgi?id=98987
Václav Ovsík vaclav.ovsik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #128323|logged using netconsole - |logged using netconsole - description|kernel 4.8.7 (Debian |4.8.7 - NULL pointer |kernel) |
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #2 from Václav Ovsík vaclav.ovsik@gmail.com --- Created attachment 128325 --> https://bugs.freedesktop.org/attachment.cgi?id=128325&action=edit logged using netconsole - 4.9.0-rc7 - NULL pointer
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #3 from Václav Ovsík vaclav.ovsik@gmail.com --- Created attachment 128326 --> https://bugs.freedesktop.org/attachment.cgi?id=128326&action=edit logged using netconsole - 4.9.0-rc7 - soft lockup
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #4 from Václav Ovsík vaclav.ovsik@gmail.com --- today I inserted into MB Asus M2A-VM HDMI PCI-E card HD7770. With HD7770 the modeset works OK without any crash/lockup. Xserver started OK too. Loaded was radeon driver. The bug in radeon driver is in a part specific to RS690 chip so.
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #5 from Vedran Miletić vedran@miletic.net --- Has KMS ever worked on that card for you? If yes, can you test older kernels?
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #6 from Christian König deathsimple@vodafone.de --- Setting radeon.modeset=0 is not longer supported since the removal of UMS support, so setting this options just blacklists the driver completely.
That looks like a bug in the HDMI audio handling code, we had similar issues on other hardware generations as well. Maybe the handling routine for RS690 is still not in the correct order.
Anyway please try radeon.audio=0 as well.
https://bugs.freedesktop.org/show_bug.cgi?id=98987
--- Comment #7 from Václav Ovsík vaclav.ovsik@gmail.com --- Bing - HDMI audio is probably a source of problem.
I tried to add radeon.audio=0. I tested this before already, but I tried this time again with 4.9-rc7. No bug in console appeared, but kernel lock down (<Alt>-<SysRq>-B don't worked). I tried I think 3-times - no OOPS on console, only hang. Then I get idea to look into BIOS if HDMI audio is enabled there and really, HDMI was disabled completely. I enable HDMI in the BIOS and disable HDMI audio only and system started normaly. I tried combinations:
BIOS BIOS radeon.audio=0 HDMI HDMI audio ---------------------------------------------------------------- 0 - no OOPS 0 - yes OOPS yes yes no OOPS yes yes yes OOPS yes no no OK
So to avoid problems with the radeon driver the HDMI audio must be disabled in BIOS and it is possible only if the HDMI connector is enabled, because otherwise the option (HDMI audio) is greyed. I can't remember if I had this setting in the past, maybe yes. Disabled HDMI may be the result of BIOS "Load system default", because other flaws on this mobo with networking some time ago (.
https://bugs.freedesktop.org/show_bug.cgi?id=98987
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #8 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/762.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org