Description of problem: Kernel panic, trace is in attached picture. After partitioning with LVM and encrypt, I set my password and begin install, after presing Root psw button i see the kernel panic. Laptop is new Lenovo T540p exact ID in attached image with the error trace.
Created attachment 876867 [details] kernel panic trace img from my camera
Unfortunately there isn't anything we can do about F20 release media at this point. Does the problem still happen on a Rawhide nightly?
After turning off uefi seems that Fedora 20 network install is working.
I tried to install fedora rawhide, latest x86_64 from Red Hat network, build from 17.3. and I hit again kernel panic, see in attachment. (my cell camera photo)
Created attachment 876924 [details] kernel panic fedora rawhide
I tried RHEL-6.5 and RHEL-7.0 workstation and both ended with kernel panic or deep freeze of the system where I cant get any info. The problem is probably caused by HDD which is SAS 500GB drive. Seems that there are no drivers and during partition creating installation ended with panic.
The backtraces are after the initial problem has already occurred. The D taint is set in the backtrace we see, which means there's another one that probably scrolled off the screen. You might try using pause_on_oops=30 to see if you can get the initial backtrace to display.
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. 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 experience different issues, please open a new bug report for those.
Similar issue happening on a custom spinf of fedora 20 with kernel 3.14.4-200 installing in a Intel NUC. Attaching the pic with the oops but is clearly efi related. For information, previous build, with previous kernel and previous updates, worked well. I'm doing constant builds ( almost daily based )
Created attachment 899322 [details] Similar oops on install in Intel NUC
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 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.