Hi, I'm a medium-experienced Ubuntu user from Spain. I'm trying to compile 2.6.14 kernel but my PC always shuts down in the process. It's unexpected and I'm not able to see what was in the console.
If you are using a laptop make sure that the appropriate drivers are loaded and that the fan does turn on. You may need to load some programs to control the fan if the system is not already controlling it correctly.
3) When this happens, does the system shut *all the way* off?
4) Can the system be immediately turned back on again, or do you have to wait a few minutes before it will turn on? (Give away for an overheat diagnosis)
5) What are the full and thorough results of running memtest86+? (takes a few hours)
6) Can you reproduce the issue by running a stress test? (see for example, 'man stress' for an easy CPU stressor)
7) Does it always happen after the same period of time, or is there a defined range of time in which it always happens?
8) You can see the console using a serial console, if available (hardware needed: 1 x-over serial cable, 1 spare computer). Also, later kernels have a nice "kdump/kexec" feature to help see what killed the system. (/usr/src/linux-source-2.6.x/Documentation/serial-console.txt and /usr/src/linux-source-2.6.x/Documentation/kdump/kdump.txt for more info)
1. Overheating
2. Bad memory
3. Incapable or failing power supply
(Of course there is the fourth - failed support chips - but that's a motherboard replacement.)
Absolutely nothing you have said supports your idea that your computer is not overheating, so don't tell us that it's not overheating. You still didn't provide information asked by the other poster about your system, like it is it a laptop/desktop/etc - we really can't help if you keep providing information we didn't ask for and won't give us what we are asking for.
Overheated CPU?
Overheated CPU?
hot CPU
If you are using a laptop make sure that the appropriate drivers are loaded and that the fan does turn on. You may need to load some programs to control the fan if the system is not already controlling it correctly.
<NEEDINFO>
Troubleshooting:
1) Has this ever happened except during compile?
2) Desktop or portable?
3) When this happens, does the system shut *all the way* off?
4) Can the system be immediately turned back on again, or do you have to wait a few minutes before it will turn on? (Give away for an overheat diagnosis)
5) What are the full and thorough results of running memtest86+? (takes a few hours)
6) Can you reproduce the issue by running a stress test? (see for example, 'man stress' for an easy CPU stressor)
7) Does it always happen after the same period of time, or is there a defined range of time in which it always happens?
8) You can see the console using a serial console, if available (hardware needed: 1 x-over serial cable, 1 spare computer). Also, later kernels have a nice "kdump/kexec" feature to help see what killed the system. (/usr/src/linux-source-2.6.x/Documentation/serial-console.txt and /usr/src/linux-source-2.6.x/Documentation/kdump/kdump.txt for more info)
Answering
I don't think it's a matter of overheading, since compilation is the only performing task. Besides, it usually crashes at the same point.
I could detect the problem... I think. Check this output:
make[3]: *** [drivers/block/paride/paride.o] Colgado (Hung)
make[2]: *** [drivers/block/paride] Colgado (Hung)
make[1]: *** [drivers] Colgado (Hung)
make: *** [stamp-build] Colgado (Hung)
When crashing, a beep is heard and few seconds later the computer turns off, sometimes suddenly and sometimes in the usual way.
Can you figure out something with this info? If not, I'll answer all your questions.
By the way, desktop PC.
Thanks.
memtest
not really...
maybe a memory problem? check your sticks with memtest86+ for a whole day
possible problems
Three typical problems still remain:
1. Overheating
2. Bad memory
3. Incapable or failing power supply
(Of course there is the fourth - failed support chips - but that's a motherboard replacement.)
Absolutely nothing you have said supports your idea that your computer is not overheating, so don't tell us that it's not overheating. You still didn't provide information asked by the other poster about your system, like it is it a laptop/desktop/etc - we really can't help if you keep providing information we didn't ask for and won't give us what we are asking for.