Created attachment 845807 [details] Trace on screen (first) Description of problem: Get traces starting http://kojipkgs.fedoraproject.org//work/tasks/1706/6361706/Fedora-Live-Jam-KDE-x86_64-rawhide-20140105.iso Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Boot http://kojipkgs.fedoraproject.org//work/tasks/1706/6361706/Fedora-Live-Jam-KDE-x86_64-rawhide-20140105.iso from CD drive 2. Select Debug (2nd line Actual results: Messages about perf counts, then alternating call traces Expected results: Normal boot. Additional info: Worked for a while, but hung after I tried to get a network connection. I don't think the network connection works, because I can't add a new wireless network.
Created attachment 845808 [details] Trace on screen (second)
kernel-debug-3.13.0-0.rc6.git0.1.fc21.x86_64 (maybe not debug)
Does this happen only on one machine, or all the machines you tried? Can you get the dmesg saved to a USB key or something similar and attach it?
It happens on more that one machine. This morning, I tried Fedora-Live-Jam-KDE-x86_64-rawhide-20140111.iso on a Toshiba NB550D. First, following http://fedoraproject.org/wiki/Netconsole, I prepared a debugger machine by setting it to accept a fixed ethernet port at 10.0.0.1, connecting the two machines with an ethernet cable, enabling the firewall to accept port 6666, and issuing nc -vlu 6666. Then I booted the NB55D, holding F12 to get a boot menu. The debugger now showed an active internet connection, and I was able to get its MAC address using Connection Information. On the NB550, I selected booting from the CD. When the opening menu appeared, I selected Troubleshooting, and edited the Test Media and Boot item to remove rhgb and quiet, and added netconsole=4444.0.2/p4p1@6666.0.1/<my-mac-address>. When I hit return, the NB555D started the media check, but when it got about 1.5% through, it crashed with a trace that I can photograph if this happened too early for the netconsole trace. To check my connection, I restarted the NB555D's working system and added the same netconsole command as above. Nothing appeared on the debugger machine. After the system booted, I configured an ethernet connection with a fixed address of 10.0.0.2. When I issued "ncat -vu 10.0.0.1 6666", I could then type on its keyboard and see the text appearing on the debugger machine. So, I know I have a good ethernet connection. I suspect there is something wrong with my netconsole parameter, since it produces no output in a working system.
Tried Fedora-Live-Jam-KDE-x86_64-rawhide-20140112.iso on two machines, a Toshiba NB555D and a HP61. I followed the same procedure on both: Boot the DVD Move down to Troubleshooting, hit enter Move to Test Media and Start Hit Tab, remove rhgb and quiet, add nomodeset=2 Hit Enter CD boots, media check starts, then I get a traceback and the bug. If I can't get a dmesg, I can provide screen photos.
According to bug 1052843, I can boot Fedora-Live-Security-x86_64-rawhide-20140113.iso without the crashes. I don't know if that's relevant or not.
What kernel is included in the Security spin and what kernel is included in the KDE spin(s) you're having trouble with?
Created attachment 850798 [details] dmesg output I have found the traces appear when the "threadirqs" keyword is present in the command line. As mentioned in bug 467594, removing that keyword made it possible for me to get the attached dmesg and typescript files. In future tests, I'll make sure the MicroSD adapter is removed.
Created attachment 850799 [details] /var/log/messages from boot
(In reply to Peter H. Jones from comment #8) > Created attachment 850798 [details] > dmesg output > > I have found the traces appear when the "threadirqs" keyword is present in > the command line. As mentioned in bug 467594, removing that keyword made it > possible for me to get the attached dmesg and typescript files. So all of the kernel traces you've been seeing have come from having threadirqs on the command line?
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