Jump to content
17 posts in this topic

Recommended Posts

I don't know what to do. The problem is the following: my hack os reboots without any visible reason in random moments. It can happen any time -- after 3 days of uptime or after 15 minutes. Reboot is not instant -- for 2-3 seconds I can notice that the mouse pointer starts to move not smooth, after few seconds it freezes. If something is playing in the spekers (itunes, flash, mplayer -- anything) the sound loops in ~one second interval. No kernel panic is shown and if I press command+S in the first moments when mouse only "starts freezing" I can successfully save anything.

I don't know how to catch the reason -- I can see nothing in logs and I can't see any repeating sequence to reproduce that behavior.

 

My system is iAtkos S3 v2, Snow Leopard 10.6.5, vanilla kernel (Darwin Kernel Version 10.5.0: Fri Nov 5 23:19:13 PDT 2010; root:xnu-1504.9.17~1/RELEASE_X86_64 x86_64), chameleon rc5.

My hardware is Core i7 930, 6gb ram, Nvidia gtx460 (latest tonyosx86 drivers), X58 chipset.

 

logs are attached:

kernel.log: http://foo.ru/files/kernel.log

system.log: http://foo.ru/files/system.log

system.log.0.bz2: http://foo.ru/files/system.log.bz2

Tip -- last "random" reboot happened about Dec 6 13:03

 

Help, please!

Does it happen only while using OS X or Windows as well? Try that out if you only have OS X installed, it could be a PSU problem, my friend had it, also the guys at www.jupiterbroadcasting.com look for hackintosh episodes.

Try running the Torture test in Prime95 for a while. I found that while my system had tested out fine when I built it about 2 years ago, I had started to get random reboots, KPs and freezes. When I ran the torture test, it immediately failed with FATAL ERROR : Rounding error. I had to override the auto RAM speeds and slow them down a notch to get the test to run for a few hours. After that, no reboots or lockup. Still get the odd KP from VoodooHDA, but at least I know what to expect there.

 

There's a version for OS X.

zicoos: only OSX -- Linux and Win7 work perfect

 

 

ntsmkfob: thanks, I'll try it now and write if it fails

 

Try running the Torture test in Prime95 for a while. I found that while my system had tested out fine when I built it about 2 years ago, I had started to get random reboots, KPs and freezes. When I ran the torture test, it immediately failed with FATAL ERROR : Rounding error. I had to override the auto RAM speeds and slow them down a notch to get the test to run for a few hours. After that, no reboots or lockup. Still get the odd KP from VoodooHDA, but at least I know what to expect there.

 

There's a version for OS X.

 

 

It doesn't fail. But I don't know how long to wait; now there is:

 

[Dec 6 18:00] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.

....

[Dec 6 18:14] Test 7, 4000 Lucas-Lehmer iterations of M18474367 using FFT length 1024K.

[Dec 6 18:16] Self-test 1024K passed!

[Dec 6 18:16] Test 1, 800000 Lucas-Lehmer iterations of M172031 using FFT length 8K.

....

[Dec 6 18:30] Test 8, 800000 Lucas-Lehmer iterations of M143361 using FFT length 8K.

[Dec 6 18:32] Self-test 8K passed!

[Dec 6 18:32] Test 1, 560000 Lucas-Lehmer iterations of M212991 using FFT length 10K.

....

[Dec 6 18:45] Test 7, 560000 Lucas-Lehmer iterations of M194561 using FFT length 10K.

[Dec 6 18:47] Self-test 10K passed!

[Dec 6 18:47] Test 1, 4500 Lucas-Lehmer iterations of M17432577 using FFT length 896K.

....

 

Some more ideas?

zicoos: only OSX -- Linux and Win7 work perfect

 

 

ntsmkfob: thanks, I'll try it now and write if it fails

 

 

 

 

It doesn't fail. But I don't know how long to wait; now there is:

 

[Dec 6 18:00] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.

[Dec 6 18:03] Test 2, 4000 Lucas-Lehmer iterations of M19922943 using FFT length 1024K.

[Dec 6 18:05] Test 3, 4000 Lucas-Lehmer iterations of M19374367 using FFT length 1024K.

[Dec 6 18:07] Test 4, 4000 Lucas-Lehmer iterations of M19174369 using FFT length 1024K.

[Dec 6 18:09] Test 5, 4000 Lucas-Lehmer iterations of M18874369 using FFT length 1024K.

[Dec 6 18:11] Test 6, 4000 Lucas-Lehmer iterations of M18874367 using FFT length 1024K.

[Dec 6 18:14] Test 7, 4000 Lucas-Lehmer iterations of M18474367 using FFT length 1024K.

[Dec 6 18:16] Self-test 1024K passed!

[Dec 6 18:16] Test 1, 800000 Lucas-Lehmer iterations of M172031 using FFT length 8K.

[Dec 6 18:18] Test 2, 800000 Lucas-Lehmer iterations of M163839 using FFT length 8K.

[Dec 6 18:20] Test 3, 800000 Lucas-Lehmer iterations of M159745 using FFT length 8K.

[Dec 6 18:22] Test 4, 800000 Lucas-Lehmer iterations of M157695 using FFT length 8K.

[Dec 6 18:24] Test 5, 800000 Lucas-Lehmer iterations of M155649 using FFT length 8K.

[Dec 6 18:26] Test 6, 800000 Lucas-Lehmer iterations of M153599 using FFT length 8K.

 

Some more ideas?

 

Could you tell me where I can find the log files that you have in the OP? Asked earlier here but no reply. It would be greatly appreciated!

Robert

Could you tell me where I can find the log files that you have in the OP? Asked earlier here but no reply. It would be greatly appreciated!

Robert

 

Oh, excuse me, i didn't notice the question. They are located at /var/log/. You couldn't find them because you can't see this folder using finder. The simpliest way to get them is the following (step by step):

 

1) Open Programs/Service applications (i don't know how it exactly named in english osx). There is an application named Terminal. Open it

2) You will see some kind of console, do not fear.

3) Type in the console:

cd /var/log/

ls

 

4) After the second command you will see the list of files that are located in /var/log. You can copy any log to another place with the command "cp". For example this will copy /var/log/kernel.log to the desktop:

cp /var/log/kernel.log ~/Desktop

 

5) You can copy any file with this command obviously. And any log in /var/log/ in particular. The third step is only for understanding what logs do you have

fallen again :rolleyes: I think it's not connected with the test -- it was working for two hours.

Updated logs. Help!

 

kernel.log: http://foo.ru/files/kernel.log

system.log: http://foo.ru/files/system.log

system.log.0.bz2: http://foo.ru/files/system.log.bz2

fallen at ~20:10

You can get to the logs from the Apple Icon/About this Mac/More Info and Logs is listed halfway down the Software section on the left.

Thats alot easier! Thanks!! What log should I look at to see what's making it give be the restart dialog? Feel like I'm hijacking his thread. Sorry.

Hmm, your issue reminds me of what would happen when I installed "Little Snitch" would reboot in about 2 hours. And I also had issues when I installed an app from Samsung to adjust the monitor.

 

Just brain storming: Can you install a new untouched Retail OS X with only the needed kext's and see if it behaves the same?

Hmm, your issue reminds me of what would happen when I installed "Little Snitch" would reboot in about 2 hours. And I also had issues when I installed an app from Samsung to adjust the monitor.

 

Just brain storming: Can you install a new untouched Retail OS X with only the needed kext's and see if it behaves the same?

 

 

Maybe on the next hollydays if I won't solve the problem -- I don't have time now. I haven't nor Little Snitch, neither Samsung apps.

But I'm not a novice in hack os -- it's my fourth pc under mac osx since 2005. So I installed everything only with needed kexts eventually. This problem surprised me very much -- I don't remember any other problem that hasn't left any clues in the logs

 

 

But I hope I've found the solution, I'm testing it now. It seems that the problem of iMac users is incompatibility of different RAM modules. I have a 3x2gb Kingston memory kit. But I noticed that it wasn't shown in hardware list correctly -- it had written that I have 3x2gb 800mhz memory of unknown manufacturer instead of 1600mhz from Kingston. So I have installed Chameleon RC4-AsereBLN-1.1.9 instead of Chaeleon RC5 pre-release6. Now the memory is shown with correct values.

I will write if it fails again or if it wouldn't be failing for 2 days at least

If it fails again, the reply from zicoos may be worth looking at. Boot into the BIOS and check your voltages. I can recall having a client with a PSU giving out of spec 12v, which caused hangs and BSODs in XP. I think he was getting about 11.3v instead of 12v. New PSU fixed it.

If it fails again, the reply from zicoos may be worth looking at. Boot into the BIOS and check your voltages. I can recall having a client with a PSU giving out of spec 12v, which caused hangs and BSODs in XP. I think he was getting about 11.3v instead of 12v. New PSU fixed it.

 

Still nothing fails :)

 

I've checked it already -- I just haven't written about it. I have Corsair power supply unit, it's stable as a rock and accurate as sniper :rolleyes:

 

Thanks for your help

 

 

 

By the way, it's very funny that I can repair this instability and the owners of generic iMacs can't -- they have to wait for official update to detect their memory units in the right way

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...