FS#45877 - [linux] Unable to boot from Linux kernel 4.1.3

Attached to Project: Arch Linux
Opened by Daniel J Dominguez (danield21) - Sunday, 02 August 2015, 23:15 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 26 June 2016, 14:46 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After updating from linux 4.1.2 to 4.1.3 and rebooting, the systemd boot would start up as normal, then when it gets to starting the user manager, it would go into a infinite loop of starting and stopping it, and eventually finally stop the loop by removing the slice and just hang. I decided to restart and it went through the same process of looping, so I downgraded the kernel and that seemed to fix it.

Additional info:
* linux 4.1.3
* logs have been attached.


Steps to reproduce:
pacman -S linux
reboot
   boot.log (1.5 MiB)
   Xorg.0.log (33.4 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 26 June 2016, 14:46 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Monday, 03 August 2015, 03:37 GMT
Is everything else on your system up-to-date?
Comment by Daniel J Dominguez (danield21) - Tuesday, 04 August 2015, 01:30 GMT
Yes, in fact I just did a pacman Syu and let the kernel update as well, same thing happened. So far, I have to downgrade to the previous version to get it to run. Also, it appears I meant 4.1.2 to 4.1.3.
Comment by Aidan E. (aereaux) - Tuesday, 04 August 2015, 04:01 GMT
Oops, wrong bug.
Comment by Timothy Redaelli (tredaelli) - Wednesday, 05 August 2015, 17:09 GMT
"[ 34.888] (EE) [drm] KMS not enabled"
seems like KMS is not enabled, which is your cmdline?
Comment by Samantha McVey (samcv) - Friday, 10 June 2016, 08:17 GMT
Daniel,
This bug is now almost a year old. Can you please let me know if this is still a problem for you or if this was fixed in a more recent kernel version? Your response is appreciated.

Loading...