PDA

View Full Version : FC4 freezes / hangs



mongenix
24th March 2006, 10:46 PM
I know most of the posting are FC5 but this is a real problem for us.

I posted a while ago about 10 systems I have running FC4(all updates applied) and the systems will simply hang - absolutly not response. Reset button required.
The var/log/messages show this at the time it froze. 5 of the 10 machines have froze many times but the other 5 have not. All machines were built with the same equipment.
This time it hung shortly after turning on the system.
It hung at 14:09 and I pressed the reset button to bring it back up at 14:28


Mar 24 14:09:18 fc41 kernel: lp0: console ready
Mar 24 14:09:31 fc41 gdm(pam_unix)[2016]: session opened for user tina by (uid=0)
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release semaphore
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release SHM segment
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release SHM segment
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: No such file or directory
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release semaphore
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release SHM segment
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: Memory: Failed to release SHM segment
Mar 24 14:09:31 fc41 ainit: Error: No such file or directory
Mar 24 14:09:31 fc41 ainit: No such file or directory
Mar 24 14:09:32 fc41 gconfd (tina-2214): starting (version 2.10.0), pid 2214 user 'tina'
Mar 24 14:09:32 fc41 gconfd (tina-2214): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Mar 24 14:09:32 fc41 gconfd (tina-2214): Resolved address "xml:readwrite:/home/tina/.gconf" to a writable configuration source at position 1
Mar 24 14:09:32 fc41 gconfd (tina-2214): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Mar 24 14:09:38 fc41 gconfd (tina-2214): Resolved address "xml:readwrite:/home/tina/.gconf" to a writable configuration source at position 0
Mar 24 14:28:05 fc41 su(pam_unix)[2473]: session opened for user root by (uid=501)

mongenix
25th March 2006, 01:44 AM
Found that during boot the following was displayed:
MP-BIOS bug: 8254 timer not connected to IOAPIC

On several web sites, I found that this could cause network/other devices to randomly stop working.

One of the sites states that for kernel 2.6.x, add "acpi_skip_timer_override" to the boot line. I did this and the above message is no longer there during boot.

Does anyone know if this could cause my random freezes/hangs?

If I have no more hangs, I will post back.