On Wed, 2006-10-18 at 07:02 -0400, Peter Møller Neergaard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Over the weekend, we installed a new server based on two Xeon 5130 > processors. We installed Fedora Core 5 and updated to the latest > versions on the package. > > Since installing the server, we've two times experienced that the > server completely hang: all processes became unresponsive and there > was no longer generated any log information. In both cases we had to > hard reboot the machine. The first time after 3 hours, the second > time after 30 minutes. > > 1. Are there any known issues that could cause this? > > 2. Any suggestions for BIOS settings that might cause this > > 3. Any suggestions on how to determine whether this is the hardware > or the operating system. > > The best suggestion, I've found so far is turning off unused services. > > I've included the full output of "uname -a" and "/proc/cpuinfo" below > in case it matters. > > Thank you in advance. > > /Peter > > I'd suggest you do the following (step by step): A. run memtest86 [1] on the machine for ~24 hours. Are there any memory errors? B. Start the machine in text-only runlevel 3 [2], does the machine still lock? C. Get a serial NULL cable and use to monitor the machine from a remote machine [3]. Can you see any kernel error logs? - Gilboa [1] http://www.memtest86.com/ [2] When grub starts, type E (edit) and add "3" to the command line and then 'B' (boot) [3] I. http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/configure-kernel-grub.html II. Install agetty. III. http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/getty-agetty.html IIII. Use minicom (Linux) or HyperTerminal (Windows) to open a terminal on the machine. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
