When I try to emerge GNOME, during the emerging of Xorg 6.8.0, my system gives three warnings that the system will HALT now, and, how predictable, does a complete system-halt.
I also got the same problem when wanting to emerge firefox.
Last night I completely rebuild my Gentoo-installation. Started with the live-cd and got all the necessary packages from the net. (Stage3-tarbal and portage-snapshot of 20041228 (last one of 2004))
Did an emerge -u world without any problems (including updating portage).
When I try to emerge GNOME, *** HALT ***.
The reason I rebuilt my system was because of these errors
Very little adjustments to standard installation.
Added -pipe to CFLAGS and removed -fomit-frame-pointer from it
added USE="-kda -qt gnome gtk gtk2 dvd alsa cdr"
Previous installation (with same problem) had MAKEOPTS="-j2"
Since this is my first real endeavor with Linux, please aid me with letting me help you (I don't know nothing about Linux at all... sort of....)
Please help me!!
Steps to Reproduce:
1. emerge gnome
2. wait for poweroff/halt
So this problem is solved now that you rebuilt your system, or is it still reproducable? Can you explain in more detail the halt messages that appear? (or get a photo or something?)
Could you try 2.6.10?
Could be a heat issue - causing the CPU to create an MCE and rebooting.
Problem is still reproducable, even after rebuild..
I'm now doing the same install on another machine (different HW) to see what that does, but that's gonna take some time...
At first I thought about a heat-prob, but it always happens when compiling specific packages (GNOME, firefox, libxml)
I'm not able to make a photo -> nog digital camera.
What happens is that I get three warnings on screen that the system is going down for halt now...
In the logfiles I see that the runlevel is set to runlevel 0..
Well, firefox in particular probably hits the CPU pretty hard so I woudn't rule out heat. Does your comp have ACPI with temp information? (You may need to add it to your kernel.) Keep an eye on the temp while compiling:
or better yet, make a quick log:
cat /proc/acpi/thermal_zone/THM/temperature >> templog
When you bring your system back up peek at the last entry in the log.
Well, strange things happen.. I set my machine to do the old hangerupper again yesterday. I was out yesterday, so I'd figure, just let it emerge gnome again, and see what happens...
When I got home, 11 hours later, my machine was still on!!
Then I emerged firefox, and that too got emerged without a problem!!
I just read the last entry (about the heat-log) this morning, but it seems like that could have been the case after all....
Thank you all for your support!
Well, thought I was out of the woods, but allas...
emerge liteamp now seems to crash the thing....
Made a script with the stuff Michael mentioned.. I don't have a THM, however, but TZ1 through 3..
Just figured to let the script cat all three of them and put them in the log...
We'll see what heppens now...
Seems to be indeed heat-problem..
TZ1 and TZ2 in the 70 C....
Have to check what those TZ's stand for....
You could examine the "trip_points" file - by the looks of it, the system will shut down when the critical level is met.
Looked at the trip_points and found out the problem list with TZ1 -> critical of 75 C.. and that is 1 C above last recorded temperature of that TZ..
Still don't know what that TZ stands for.. think it's the CPU...
Any ideas how I can make the fan spin faster and sooner? Can the trip_points-file be edited, or is it recreated every time?
TZ is "thermal zone"
It's not easy to say which temperature reading comes from where.
Which cooling_mode is in use?
You can modify the trip points like this:
echo "99:98:97:96:95:94" > trip_points
order is: critical:hot:passive:active0:active1:active2
Even if you don't see all those parameters in the file, just set them to some value, then the valid ones you change will be modified
You can change cooling mode to active (always on) with: echo 0 > cooling_mode
You can change it to passive (economical) with: echo 1 > cooling_mode
Closing, this is a user problem with cooling/temperatures.