I've got an Athlon64 system that is stable when running FC3 (i386) with the original kernel, 2.6.9-1.667, but crashes with anything newer. I loaded FC4 (x86_64) on it and it crashes there as well. It crashes under various things that cause a load: rsyncing Fedora mirrors, playing bzflag, transcoding video, etc. I've also had some crashes while web browsing. Under the FC3 2.6.11-1.35_FC3 kernel, I get: kernel BUG at mm/rmap.c:482! invalid operand: 0000 [#1] every time it crashes. I set up a serial console so I can capture messages while in X. However, the crashes in FC4/x86_64 didn't even give me an oops. One odd thing about an FC4 crash playing bzflag (against some "bot" tanks): it froze after I fired a shot (all the tanks and other video stopped moving), but I still heard the sounds die away. I didn't get an oops, and even magic-SysRq (or serial break) didn't respond. It doesn't appear to be a RAM problem; it ran clean with memtest86+ for 24 hours. Another odd thing with FC4/x86_64: if I enable "Cool & Quiet" in the BIOS, I get random segfaults during boot. If I turn it off, powernow-k8 complains during boot, but the system runs (for a little bit anyway). I opened a bugzilla about this a while back. I closed it when I though it was working, but it was still crashing (I just hadn't done much for a few days I guess). I re-opened it and attached some more crash messages; it is: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159364 At this point, I'd be happy to find out it is bad hardware so I could replace it and move on. However, I can't afford to throw it all away without knowing which part is bad. Suggestions? -- Chris Adams <cmadams@xxxxxxxxxx> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
