https://bugzilla.kernel.org/show_bug.cgi?id=96361
Bug ID: 96361 Summary: [Bisected, radeon]Non-infinite boot loop since v3.13 Product: Drivers Version: 2.5 Kernel Version: 3.19 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: servuswiegehtz@yahoo.de Regression: No
For a while now my desktop pc experiences boot issues. I try to boot and after grub the screen just goes in standby mode and sometimes it reboots and sometimes just nothing happens. After a few tries it usually succeeds in booting.
So I bisected the kernel and this is the first bad commit: 6c7bccea390853bdec5b76fe31fc50f3b36f75d5
Steps to reproduce: not sure, seems to be a rare bug. install a linux kernel newer than 3.13 and boot
Hardware: AMD Phenom X4 955 AMD 5770 (Evergreen, Juniper)
I tried to get a log from systemd (journalctl --boot=-1) but there is none for the failed boot attempt.
https://bugzilla.kernel.org/show_bug.cgi?id=96361
Alex Deucher alexdeucher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com
--- Comment #1 from Alex Deucher alexdeucher@gmail.com --- Please attach your dmesg output with radeon.dpm=1 on the kernel command line in grub.
https://bugzilla.kernel.org/show_bug.cgi?id=96361
--- Comment #2 from servuswiegehtz@yahoo.de --- Created attachment 173691 --> https://bugzilla.kernel.org/attachment.cgi?id=173691&action=edit dmesg output
dmesg output with radeon.dpm=1 (in this case the pc managed to boot to linux, as mentioned there is no log when it fails, or is journalctl --boot=-1 the wrong way to get the previous log? (systemd))
https://bugzilla.kernel.org/show_bug.cgi?id=96361
--- Comment #3 from servuswiegehtz@yahoo.de --- bug is only present with radeon.dpm=1 (default?), with radeon.dpm=0 there are no issues
https://bugzilla.kernel.org/show_bug.cgi?id=96361
--- Comment #4 from Alex Deucher alexdeucher@gmail.com --- forcing dpm=1 enables additional debugging output not present when the parameter is not explicitly set.
https://bugzilla.kernel.org/show_bug.cgi?id=96361
--- Comment #5 from servuswiegehtz@yahoo.de --- is there anything else I can provide? logs, try some modified kernels etc?
https://bugzilla.kernel.org/show_bug.cgi?id=96361
servuswiegehtz@yahoo.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE
--- Comment #6 from servuswiegehtz@yahoo.de --- seems to be fixed in newer kernels
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org