-1

I recently installed Linux MINT 15 64bit as a guest in a UBUNTU 12.04 LTS host. Everything is working just fine, except that the complete machine turns off completely (the host, physical machine) and the screen turns black. Has anyone an idea how to fix (or even find) the problem? Is this failing hardware or has it to do with the virtualBox-thing? Any help appreciated.

If I pause the guest when CPU gets over 65°C, the machine doesn't freeze anymore. My CPU is not overclocked. Is there any way to allow only a specific percentage of CPU-usage (or only a specific freq) to prevent overheating? Is there any chance do anything in Hardware without changing the CPU?

Note: the built-in CPU-limiter in vBox doesn't work.

Improve this question

2 Answers 2

Reset to default
0

I COULD be wrong, but it could be a hardware issue. You need to provide more details. Full system specs, CPU, GPU, PSU, HDD, and RAM. As much information about these as you can. So don't do anything drastic like buy a new PSU or CPU based on this advice!

It's possible a power fluctuation is causing the trouble. If your processor is overclocked, it could easily be causing this. It's common for overclocked processors to run fine under normal conditions and then cause your computer to randomly crash. This is caused by power fluctuations, and THOSE are caused by electrical noise of a variety of sorts. Your PSU doesn't provide a perfect stream of power, and under certain conditions, it fluctuates more, sometimes too much, and the CPU shut down when an incorrect voltage is received.

Similar problems can arise with any component in your computer, the two most common I find, being the RAM and the CPU. My RAM has to be manually revolted to 1.65V, because that is it's specified range, but my Mobo automatically sets it to 1.5V for whatever reason. Cleaning up glitches like that will stabilize your system.

If you have extra components, or another PC, try swapping parts (PSU, RAM, GPU) as well and see if any of that stops your random crashing. It could be a voltage glitch, or your PSU may need to be replaced for all we know.

Improve this answer
4
  • Hi, thank you for your speedy answer. Point is, i don't have a clue how to report the requested system data or logs. If i had i already would have posted them... ;)
    – zulu34sx
    Aug 3, 2013 at 12:00
  • You could've been more constructive by giving me any shell commands that would give me and you any logs or information that are valuable. I thought this community is to help each other and not to already know...
    – zulu34sx
    Aug 6, 2013 at 16:27
  • You cant trouble shoot hardware if you don't know how to find out how much ram you have or what your CPU GPU and PSU specs are. Google it, there is tons of useful documentation, and you need to learn about the guts of your PC before you troubleshoot hardware. I'm not going to retype guides on how to identify your hardware when thousands of videos and docs already exist, that's redundant. Use Google.
    – Alex
    Aug 6, 2013 at 19:32
  • CPU: AMD Athlon(tm) II X3 435 Processor × 3 GPU: ATI Radeon HD 5700 Series, Driver vers.: 012.019.000.003.000000
    – zulu34sx
    Aug 7, 2013 at 12:56
0

This could be at least two problems:

  1. Many BIOS have a setting to halt the CPU (to prevent damage to the CPU) once it reaches a certain temp.

  2. There's issue which plagued me for months with an HP P7-1240 (AMD A10-5700) where the default 'ondemand' CPU governor can result in a hang. I switched to use 'conservative' instead and the problem has not reoccurred.

You need to either build a kernel which does this by default or change it ASAP once you login.

One problem I am seeing is that even if I build the kernel that at some point soon after I login it will be changed back to 'ondemand'. I don't know what is changing it. Changing it back to 'conservative' seems to 'stick'. [1]

From the documentation for CONFIG_CPU_FREQ_GOV_CONSERVATIVE (emphasis added):

'conservative' - this driver is rather similar to the 'ondemand' governor both in its source code and its purpose, the difference is its optimisation for better suitability in a battery powered environment. The frequency is gracefully increased and decreased rather than jumping to 100% when speed is required.

If you have a desktop machine then you should really be considering the 'ondemand' governor instead, however if you are using a laptop, PDA or even an AMD64 based computer (due to the unacceptable step-by-step latency issues between the minimum and maximum frequency transitions in the CPU) you will probably want to use this governor.

EDIT: [1] Found it. This is /etc/init.d/ondemand:

root@care:/tmp# sysv-rc-conf --list ondemand
ondemand     2:on       3:on    4:on    5:on

disable it:

root@care:/tmp# sysv-rc-conf ondemand off
root@care:/tmp# sysv-rc-conf --list ondemand
ondemand     2:off      3:off   4:off   5:off
Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .