Hide Forgot
Description of problem: I've been having a terrible time with my system throwing kernel panics all over the place, frequently leading to complete system lockup. (Caps lock and Scroll lock blinking in unison.) I was having this problem with FC13. These lockups can occur after anywhere from 6 minutes to 72+ hours after boot. I recently upgraded to FC14 (6 Mar 2011) to see if this solved my problems. It did not. I thought to compile the kernel on my machine to see if a local build would help. And now I'm here. Version-Release number of selected component (if applicable): kernel-2.6.35.fc14 How reproducible: From my compile messages: In file included from include/linux/proc_fs.h:5:0, from include/linux/netfilter.h:329, from include/net/netns/x_tables.h:5, from include/net/net_namespace.h:18, from include/linux/netdevice.h:49, from drivers/net/usb/pegasus.c:35: include/linux/fs.h:666:2: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I'm not certain that I should even be submitting this report, being an unreproducible bug, but, well, the error message said to anyway. If someone tells me how to find said "preprocessed source", I'll be happy to attach it. I'll come back and add "Steps to Reproduce" later, after seeing if running the build process again actually duplicates it, but I want to submit this before my system dies again...
How unreproducible is it? So unreproducible that simply hitting the up arrow in that window and running the exact same command (rpmbuild -bb --target=`uname -m` kernel.spec) on the exact same code without changing one single thing, other than the total entropy in the universe, did not reproduce it. It compiled. So... yeah. I dunno what else to say. Throw this one away? Y'all's call, I'll try and find more info for you if I can (and you want), or we can drop it.
You've almost certainly got some bad memory. Try running memtest.
Ran memtest, two full cycles, no errors. That said, I pulled one of my 4GB sticks and got a 7 day uptime, which beats anything I've ever gotten before, and ... then it crashed on a different bug. (nVidia NVRM Xid message in /var/log messages, no blinking lights on the keyboard,so, uh, yeah, something else.) I've got the other stick (the one I pulled out at first) in the machine now, and the one I had the 7 day uptime on in the bag, and I'm going to see how it fares on this one. I don't really know how to reconcile this behaviour with the memtest results, though. On that note, this probably isn't y'all's problem here. So, thanks for listening, I'm just going to close this one. If you want some more information, open it and drop a line, I'll come back. :)