Bug 1332056 - no plymouth, si_restrict_performance_levels_before_switch failed
Summary: no plymouth, si_restrict_performance_levels_before_switch failed
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-01 22:52 UTC by Ralph Giles
Modified: 2016-10-27 22:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 22:26:36 UTC
Type: Bug


Attachments (Terms of Use)

Description Ralph Giles 2016-05-01 22:52:18 UTC
Description of problem:

After installing upgrades on my fedora 24 test system on Friday, I tried booting it today. The machine came up through the normal boot logo. Then instead of a login screen, I got a text-mode message:

[drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed

ctrl-shift-F2 switches to a text-mode login screen, and the machine is up and listening on ssh. Just no...workstation part.

Version-Release number of selected component (if applicable):

Fedora (4.5.2-301.fc24.x86_64) 24 (Workstation Edition)

How reproducible:

Still occurs with the previous kernel 100% so far.

Steps to Reproduce:
1. dnf system-upgrade to 24 on a crufty system
2. dnf upgrade daily for a week.
3. restart

Actual results:

No graphical login.

Expected results:

Normal login screen.

Additional info:

Switching back to tty shows a more complete boot log. All steps are green (OK) except for:

Starting Cleanup udevd DB...
Starting Plymouth switch root service...
Starting Switch Root...

Let me know if you need anything else. I'm familiar with the command line, but not with X or systemd debugging.

Comment 1 Ralph Giles 2016-05-01 23:16:39 UTC
Still occurs after installing today's updates, and with kernel 4.5.2-302.

Comment 2 Ralph Giles 2016-05-02 17:26:47 UTC
Seems to be resolved after today's updates. Maybe selinux-policy.noarch 3.13.1-184.fc24? Feel free to close.


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