From: "ionut cristian cucu" <cuciferus@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] new laptop
Date: Thu, 7 Feb 2008 16:16:06 +0200 [thread overview]
Message-ID: <567e56ca0802070616v28261ce9rd72328d60fdc9f84@mail.gmail.com> (raw)
In-Reply-To: <d257c3560802070048h1202bd7wb4f08ed864494fab@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
2008/2/7, Beso <givemesugarr@gmail.com>:
> 2008/2/7, ionut cristian cucu <cuciferus@gmail.com>:
> > ncpufreqd will not start but it doesn't print any errors either.
>
> have you set the /etc/ncpufreqd.conf?
I've looked there and apart from an /proc/acpi/CPU witch had to be
corrected to CPU0 everything else was oki
also, have you started cpufrequtils as
> a daemon and loaded the various cpufreq modules?!
Yup
> without them ncpufreqd won't work. to see if it starts try looking at the
> system log.
I have not yet setup the system log yet, and gentoo-wiki is not up
>
> > But
> > strange issue: I did a test: MAKEOPTS="-j" emerge amarok and guess
> > what the temp did not budge a degree over 50, but this morning as I'm
> > writing this my cpu is on 62% usage but the temp is 95 degrees.
>
>
> it's impossible for the thermal to be at only 50 when compiling unlimited
> jobs. maybe the temp you're seeing is the core and not the thermal one. it
> makes sense that core is at 50° and thermal at 95°.
Hmm I might have a little bit exagerated but hwmon1/2 were constant
and certainly in sane values
>
> > This
> > puzzles me. Stopping any emerge process did help, but last night it
> > went for hours with full 100% CPU load and now it overheats with
> > "-j1". It is clear, to me, that something somewhere is wicked.
> > LATER: I've just noticed that TZ01 in kima was 0 rebooting set it to
> > 50 and now with emerge keeping the cpu at max speed and load gives me
> > only 55 degrees. So how I will do a kernel update maybe will fix my
> > problem, because it looks to me like it's comming from there. Isn't
> > it?
>
> then the tz01 is the processor core thermal and not the thermal itself. then
> you should have another thermal zone other than TZ01. try looking in the
> /proc/acpi. or better do a ls -lR /proc/acpi > proc-contents.txt and append
> it here. it might be useful to see what your proc contains.
>
>
> --
> dott. ing. beso
[-- Attachment #2: proc-content.txt --]
[-- Type: text/plain, Size: 3181 bytes --]
/proc/acpi/:
total 0
dr-xr-xr-x 3 root root 0 Feb 7 16:15 ac_adapter
-rw-r--r-- 1 root root 0 Feb 7 16:15 alarm
dr-xr-xr-x 3 root root 0 Feb 7 16:15 battery
dr-xr-xr-x 5 root root 0 Feb 7 16:15 button
-r-------- 1 root root 0 Feb 7 16:15 dsdt
dr-xr-xr-x 3 root root 0 Feb 7 16:15 embedded_controller
-r--r----- 1 root haldaemon 0 Feb 7 09:43 event
-r-------- 1 root root 0 Feb 7 16:15 fadt
dr-xr-xr-x 2 root root 0 Feb 7 16:15 fan
-r--r--r-- 1 root root 0 Feb 7 16:15 info
dr-xr-xr-x 2 root root 0 Feb 7 16:15 power_resource
dr-xr-xr-x 4 root root 0 Feb 7 16:15 processor
-rw-r--r-- 1 root root 0 Feb 7 16:15 sleep
dr-xr-xr-x 3 root root 0 Feb 7 16:15 thermal_zone
-rw-r--r-- 1 root root 0 Feb 7 16:15 wakeup
/proc/acpi/ac_adapter:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 AC
/proc/acpi/ac_adapter/AC:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 state
/proc/acpi/battery:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 BAT0
/proc/acpi/battery/BAT0:
total 0
-rw-r--r-- 1 root root 0 Feb 7 16:15 alarm
-r--r--r-- 1 root root 0 Feb 7 16:15 info
-r--r--r-- 1 root root 0 Feb 7 16:15 state
/proc/acpi/button:
total 0
dr-xr-xr-x 3 root root 0 Feb 7 16:15 lid
dr-xr-xr-x 4 root root 0 Feb 7 16:15 power
dr-xr-xr-x 3 root root 0 Feb 7 16:15 sleep
/proc/acpi/button/lid:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 LID0
/proc/acpi/button/lid/LID0:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
-r--r--r-- 1 root root 0 Feb 7 16:15 state
/proc/acpi/button/power:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 PWRB
dr-xr-xr-x 2 root root 0 Feb 7 16:15 PWRF
/proc/acpi/button/power/PWRB:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
/proc/acpi/button/power/PWRF:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
/proc/acpi/button/sleep:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 SLPB
/proc/acpi/button/sleep/SLPB:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
/proc/acpi/embedded_controller:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 EC0
/proc/acpi/embedded_controller/EC0:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
/proc/acpi/fan:
total 0
/proc/acpi/power_resource:
total 0
/proc/acpi/processor:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 CPU0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 CPU1
/proc/acpi/processor/CPU0:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
-rw-r--r-- 1 root root 0 Feb 7 16:15 limit
-r--r--r-- 1 root root 0 Feb 7 16:15 performance
-r--r--r-- 1 root root 0 Feb 7 16:15 power
-rw-r--r-- 1 root root 0 Feb 7 16:15 throttling
/proc/acpi/processor/CPU1:
total 0
-r--r--r-- 1 root root 0 Feb 7 16:15 info
-rw-r--r-- 1 root root 0 Feb 7 16:15 limit
-r--r--r-- 1 root root 0 Feb 7 16:15 power
-rw-r--r-- 1 root root 0 Feb 7 16:15 throttling
/proc/acpi/thermal_zone:
total 0
dr-xr-xr-x 2 root root 0 Feb 7 16:15 TZ01
/proc/acpi/thermal_zone/TZ01:
total 0
-rw-r--r-- 1 root root 0 Feb 7 16:15 cooling_mode
-rw-r--r-- 1 root root 0 Feb 7 16:15 polling_frequency
-r--r--r-- 1 root root 0 Feb 7 16:15 state
-r--r--r-- 1 root root 0 Feb 7 16:15 temperature
-r--r--r-- 1 root root 0 Feb 7 16:15 trip_points
next prev parent reply other threads:[~2008-02-07 14:16 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 21:25 [gentoo-amd64] madwifi-ng not compile in amd64 agtdino
2008-01-28 21:54 ` Beso
2008-01-28 22:52 ` Volker Armin Hemmann
2008-01-29 7:51 ` Beso
2008-01-29 8:17 ` agtdino
2008-01-29 8:31 ` Steev Klimaszewski
2008-01-29 9:00 ` agtdino
2008-01-29 9:56 ` Beso
2008-01-29 10:52 ` agtdino
2008-01-29 11:22 ` Beso
2008-01-29 22:30 ` agtdino
2008-01-29 23:08 ` Beso
2008-01-30 1:20 ` Volker Armin Hemmann
2008-01-30 6:55 ` [gentoo-amd64] " Duncan
2008-01-30 8:04 ` Volker Armin Hemmann
2008-01-30 8:43 ` Beso
2008-01-30 16:59 ` Volker Armin Hemmann
2008-01-30 19:09 ` Beso
2008-01-30 19:47 ` Volker Armin Hemmann
2008-01-30 20:02 ` Beso
2008-01-30 8:32 ` Beso
2008-01-30 17:42 ` Duncan
2008-01-30 19:06 ` Beso
2008-01-31 10:14 ` Duncan
2008-02-03 13:42 ` [gentoo-amd64] new laptop ionut cucu
2008-02-03 13:55 ` Beso
2008-02-03 15:05 ` ionut cucu
2008-02-03 15:49 ` Beso
2008-02-04 7:39 ` ionut cucu
2008-02-04 8:11 ` [gentoo-amd64] " Duncan
2008-02-04 11:23 ` ionut cucu
2008-02-04 13:39 ` Duncan
2008-02-04 9:01 ` [gentoo-amd64] " Beso
2008-02-04 9:26 ` Beso
2008-02-04 13:48 ` ionut cucu
2008-02-04 14:21 ` Beso
2008-02-04 14:53 ` ionut cucu
2008-02-04 15:52 ` Beso
2008-02-06 11:50 ` ionut cucu
2008-02-06 13:44 ` Beso
2008-02-06 14:30 ` Brett Johnson
2008-02-06 15:45 ` Beso
2008-02-07 7:59 ` ionut cristian cucu
2008-02-07 8:48 ` Beso
2008-02-07 14:16 ` ionut cristian cucu [this message]
2008-02-04 11:51 ` ionut cucu
2008-01-30 8:18 ` [gentoo-amd64] madwifi-ng not compile in amd64 Beso
2008-01-31 22:19 ` agtdino
2008-02-01 8:26 ` Beso
2008-01-29 9:47 ` Beso
2008-01-29 10:30 ` agtdino
2008-01-28 23:21 ` [gentoo-amd64] Good Postfix / Mail Server how to Mateusz Mierzwinski
2008-01-28 23:24 ` Mark Haney
2008-01-28 23:45 ` Mateusz Mierzwinski
2008-01-29 2:15 ` Isaac Conway
2008-01-29 10:06 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=567e56ca0802070616v28261ce9rd72328d60fdc9f84@mail.gmail.com \
--to=cuciferus@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox