Description of problem: On some systems, 3.14-based kernels appear to lock up immediately after boot. Using "earlyprintk=efi" (assuming an EFI system) shows that the kernel is panicing in acpi_tb_parse_root_table. Version-Release number of selected component (if applicable): kernel-3.14.1-200.fc20.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot 3.14.1 on affected system 2. 3. Actual results: Kernel panics immediately on boot Expected results: System boots Additional info: According to the kernel bugzilla (linked) a patch is available to fix this problem though I have not tested it yet. It appears that systems with an AMI BIOS (as with mine) are affected. The patch is supposed to get queued for stable but has not been merged yet. This likely needs to be applied, as otherwise this will cause a major regression on a significant number of systems if the 3.14 update hits stable.
Using the "acpi=rsdt" boot option works around the issue.
Thanks for the pointer to the upstream bug. I've grabbed the kernel patch mentioned there and included in in the scratch build below. Could you try that when it completes and let me know if it resolves your issue? http://koji.fedoraproject.org/koji/taskinfo?taskID=6773761
Yes, this build boots normally on my system.
Thanks. I added the patch to our tree. It will be in the next build.
kernel-3.14.2-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.14.2-200.fc20
Package kernel-3.14.2-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.14.2-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5808/kernel-3.14.2-200.fc20 then log in and leave karma (feedback).
kernel-3.14.2-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.