Bug 96361 - [Bisected, radeon]Non-infinite boot loop since v3.13
Summary: [Bisected, radeon]Non-infinite boot loop since v3.13
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-08 22:14 UTC by servuswiegehtz
Modified: 2015-11-24 13:17 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.19
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output (77.55 KB, text/plain)
2015-04-09 19:01 UTC, servuswiegehtz
Details

Description servuswiegehtz 2015-04-08 22:14:08 UTC
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.
Comment 1 Alex Deucher 2015-04-09 13:04:14 UTC
Please attach your dmesg output with radeon.dpm=1 on the kernel command line in grub.
Comment 2 servuswiegehtz 2015-04-09 19:01:52 UTC
Created attachment 173691 [details]
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))
Comment 3 servuswiegehtz 2015-04-09 19:13:04 UTC
bug is only present with radeon.dpm=1 (default?), with radeon.dpm=0 there are no issues
Comment 4 Alex Deucher 2015-04-09 20:21:54 UTC
forcing dpm=1 enables additional debugging output not present when the parameter is not explicitly set.
Comment 5 servuswiegehtz 2015-04-15 20:41:16 UTC
is there anything else I can provide? logs, try some modified kernels etc?
Comment 6 servuswiegehtz 2015-11-24 13:17:32 UTC
seems to be fixed in newer kernels

Note You need to log in before you can comment on or make changes to this bug.