System Crash (ainit error) in FC4

hazmatt20 · 07-17-2006, 11:19 PM

At first, I thought I was having a problem with one of my hard drives. It kept crashing while I was moving files from it to another and watching video on it (note: this was at the same time). Fsck did have some errors, but it kept doing even it after reformatting. I found this in the messages log. I did a cat messages|grep ainit to just show the relevent ones.

Code:

Jul 17 19:10:39 localhost ainit: Memory: Failed to release semaphore
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: Memory: Failed to release SHM segment
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: Memory: Failed to release SHM segment
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: No such file or directory
Jul 17 19:10:39 localhost ainit: Memory: Failed to release semaphore
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: Memory: Failed to release SHM segment
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: Memory: Failed to release SHM segment
Jul 17 19:10:39 localhost ainit: Error: No such file or directory
Jul 17 19:10:39 localhost ainit: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release semaphore
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release SHM segment
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release SHM segment
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release semaphore
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release SHM segment
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: Memory: Failed to release SHM segment
Jul 17 22:16:24 localhost ainit: Error: No such file or directory
Jul 17 22:16:24 localhost ainit: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release semaphore
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release SHM segment
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release SHM segment
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release semaphore
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release SHM segment
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: Memory: Failed to release SHM segment
Jul 17 23:21:48 localhost ainit: Error: No such file or directory
Jul 17 23:21:48 localhost ainit: No such file or directory

Note that right after these timestamps, the system would crash. Also, the last one occurred shortly after opening an mp3 in xine. What can I do?

Matir · 07-17-2006, 11:57 PM

Try running memtest86 to check on the state of your system's memory.

hazmatt20 · 07-18-2006, 02:42 PM

Aw, crap. I'm going to be upset if it's the ram. Thanks, David. I'll try it when I get a chance and let you know how it goes.

Matir · 07-18-2006, 03:43 PM

LOL. I didn't even notice the poster name until just now. That's what I get for reading LQ at work.

hazmatt20 · 07-20-2006, 12:45 PM

Man, why do you have to be right? I ran memtest for just a little over 2 hours (long story why not longer), and in that time it found 68 errors in the first GB of memory, so it looks like I'll be sending it off to get replaced. Gotta check them individually to find out which one, but shouldn't be a problem. Yay for lifetime warranty.

Matir · 07-20-2006, 12:59 PM

That sucks. You didn't overclock or anything, did you? By the way, which brand is your RAM?

hazmatt20 · 07-20-2006, 03:29 PM

No overclocking, and it's Corsair.

Matir · 07-20-2006, 03:38 PM

I usually have good luck with Corsair. I currently have 2x512 Corsair ValueRam in my desktop, running rock solid since ~ 7/03. (Wow, my box is 3 years old... yikes)

hazmatt20 · 07-21-2006, 07:30 AM

Yeah, I have 2x1GB Corsair ValueRam in mine that's been running fine for about a year.

Matir · 07-21-2006, 09:37 AM

Eh, I need to upgrade. Don't really know why, just like new stuff.

hazmatt20 · 07-22-2006, 04:42 AM

Bah, problem totally changed direction on me. Look here http://www.linuxquestions.org/questi...d.php?t=466488.