On 07/01/2015 10:45 AM, Chris Murphy wrote:
On Wed, Jul 1, 2015 at 8:45 AM, Craig Goodyear <cjhs22a@xxxxxxxxxxxx> wrote:
Where do I start in order to determine the cause of this problem?
The closest thing I find that are semi recent is
https://bbs.archlinux.org/viewtopic.php?id=184783
So it sounds like a hardware bug that the kernel previously worked
around and now it's not working around it (?) and thus is a kernel
bug. Try using a different kernel. kernel-4.0.7-300.fc22 is in
updates-testing repo so you could easily try that. If that doesn't
work then I'd go to koji and get kernel-4.1.0-1.fc23.
If that doesn't work, then I suggest you go backwards to the newest
Fedora 21 kernel available which presumably will work since it worked
for you before.
Thank you for the response. I have downloaded and tested kernels
4.0.7-300.fc22, 4.1.0-1.fc23 and 3.17.4-301.fc21. All resulted in
booting to emerengcy mode.
At this point, I will install Fedora 21 and test. If not successful, I
will assume that I have a motherboard failure.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
