Created attachment 858241 [details] dmidecode dump Description of problem: hardware platform in dmidecode dump I went for rawhide from f20 and kernels that remain there from f20 seem to boot & work fine, 3.12.8-300.fc20.x86_64 is fine, whereas vmlinuz-3.14.0-0.rc0.git17.1.fc21.x86_64 vmlinuz-3.14.0-0.rc0.git19.1.fc21.x86_64 both crash almost at boot time please feel free to instruct on how to gather more useful info in order to help investigate it Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We need to see the backtrace of the crash in order to make any progress. Can you remove 'rhgb' and 'quiet' from the command line and see if you can get a picture or some log of the crash?
I suspect this may well be the NUMA stuff we just discussed on IRC and patched. reporter, can you check with http://koji.fedoraproject.org/koji/buildinfo?buildID=496017 - kernel-3.14.0-0.rc1.git0.2.fc21 - and see if that helps? Thanks!
Created attachment 860083 [details] boot.log
Created attachment 860085 [details] dmesg
3.14.0-0.rc1.git0.2.fc21.x86_64 is no good, I've filmed boot up but doubt anything there, booting seems find and there is no freeze just instantaneous power cycle. boot and dmesg logs attached
Can we get the journalctl output from an affected boot? journalctl has a rather neat trick for this. "journalctl -b" gets you just the journal from the current boot. "journalctl -b-1" gets you the journal from the *previous* boot. "journalctl -b-2" gets you the journal from two boots ago, and so on. You should be able to use this to isolate the output from a failed boot. thanks!
I'll do it, but these boot & dmesg don't help? they are both from the affected kernel/boot.
Created attachment 860396 [details] journalctl dump
I have no idea why your machine would be rebooting, but this is well into userspace before it happens. It looks like the last thing that is done is that dracut builds an initramfs for the kdump service.
Created attachment 863574 [details] kernel-3.14.0-0.rc2.git3.1.fc21.x86_64
danger!!! the same problem in kernel-3.13.3-201.fc20.x86_64 with Fedora 20
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.