Comment 24 for bug 1757218
Revision history for this message
| Leonardo Müller (leozinho29-eu) wrote | #24 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The bug is still the same. What happened was that the system froze at a different message in that particular try. Journalctl from a successful initialization showing the most common point of failure:
systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:
systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:
systemd[1]: Started Uncomplicated firewall.
systemd-udevd[400]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
systemd[1]: Starting Load/Save RF Kill Switch Status...
The messages after the one of intel backlight are the ones related with /dev/rfkill. This is why it freezes showing:
[ OK ]: Started Load/Save Screen Backlight Brightness of backlight:
Probably the RF Kill has a serious enough failure when this bug happens that the entire system freezes.