On Sat, 16 Aug 2003 10:25:33 +0200 "Poul-Henning Kamp" wrote:
| In message <[EMAIL PROTECTED]>, MATOBA Hirozumi wri
| tes:
| > On Fri, 15 Aug 2003 22:50:47 +0200 Thorsten Greiner wrote:
| >| $ dmesg | grep counter
| >| Timecounter "i8254" frequency 1193182 Hz
| >| Timecounter "ACPI-fast" frequen
In message <[EMAIL PROTECTED]>, MATOBA Hirozumi wri
tes:
> On Fri, 15 Aug 2003 22:50:47 +0200 Thorsten Greiner wrote:
>| $ dmesg | grep counter
>| Timecounter "i8254" frequency 1193182 Hz
>| Timecounter "ACPI-fast" frequency 3579545 Hz
>| Timecounter "TSC" frequency 1595302164 Hz
>| $ sysctl -w
Thorsten Greiner wrote:
> * Bob Fleck <[EMAIL PROTECTED]> [2003-08-15 22:46]:
> > So, what should be done to restore the proper behavior of the
> > timekeeping on these systems?
>
> $ dmesg | grep counter
> Timecounter "i8254" frequency 1193182 Hz
> Timecounter "ACPI-fast" frequency 3579545 Hz
>
On Fri, 15 Aug 2003 22:50:47 +0200 Thorsten Greiner wrote:
| $ dmesg | grep counter
| Timecounter "i8254" frequency 1193182 Hz
| Timecounter "ACPI-fast" frequency 3579545 Hz
| Timecounter "TSC" frequency 1595302164 Hz
| $ sysctl -w kern.timecounter.hardware=i8254
| Fixes the problem for me. I s
* Bob Fleck <[EMAIL PROTECTED]> [2003-08-15 22:46]:
> So, what should be done to restore the proper behavior of the
> timekeeping on these systems?
$ dmesg | grep counter
Timecounter "i8254" frequency 1193182 Hz
Timecounter "ACPI-fast" frequency 3579545 Hz
Timecounter "TSC" frequency 1595302164
On Fri, 2003-08-15 at 14:03, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, MATOBA Hirozumi wri
> tes:
>
> >On condition of hw.acpi.cpu.performance_speed as 8,
> >the clock works
>
> You should not be using the TSC for timekeeping if you change the
> frequency of it.
So, what should
In message <[EMAIL PROTECTED]>, MATOBA Hirozumi wri
tes:
>On condition of hw.acpi.cpu.performance_speed as 8,
>the clock works
You should not be using the TSC for timekeeping if you change the
frequency of it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] |
I changed 3 files in quoted mail below (tsc.c clock.h clock.c)
back to the previous revision,
on my ThinkPad A22e (the last cvsup was on Aug 13),
and recompiled kernel (the config file is almost the same as GENERIC),
and compared behavior of the clock between 2 kernels as:
kernel with the
On Thu, 2003-08-14 at 19:50, Nate Lawson wrote:
> This indicates that the problem was introduced in a kernel change between
> Aug 2 and Aug 9 and that acpi is not at fault. Try searching the cvs-all
> archives between those dates (and perhaps narrowing the date more).
I misunderstand Nate Lawson
On Thu, 2003-08-14 at 19:50, Nate Lawson wrote:
> This indicates that the problem was introduced in a kernel change between
> Aug 2 and Aug 9 and that acpi is not at fault. Try searching the cvs-all
> archives between those dates (and perhaps narrowing the date more).
To help narrow the date: I'
From: Nate Lawson <[EMAIL PROTECTED]>
Date: Thu, 14 Aug 2003 12:50:17 -0700 (PDT)
| Try searching the cvs-all
| archives between those dates (and perhaps narrowing the date more).
Thank you for your advice.
I will try this method.
(reading source,
or by doing cvsup with "date=" optio
On Fri, 15 Aug 2003, MATOBA Hirozumi wrote:
> | Between Aug 2 and 9, there were no significant changes to ACPI.
>
> I tryed sets of kernel and acpi.ko.
>
> kenel acpi.ko clock works on CPU speed as 4
>
> Aug 2 Aug 2 normally
> Aug 9 Aug 9 slowly
> Aug
From: Nate Lawson <[EMAIL PROTECTED]>
Date: Thu, 14 Aug 2003 11:20:12 -0700 (PDT)
| Between Aug 2 and 9, there were no significant changes to ACPI. I
| imported the userland tools, added tunable access to an existing variable,
| and increased the default sleep delay from 0 to 5. The last one is
Between Aug 2 and 9, there were no significant changes to ACPI. I
imported the userland tools, added tunable access to an existing variable,
and increased the default sleep delay from 0 to 5. The last one is the
only functional change and can be undone by doing:
sysctl hw.acpi.sleep_delay=0
Pl
I have a problem about clock when I change CPU speed (hw.acpi.cpu).
The default hw.acpi.cpu status of my ThinkPad A22e is
# sysctl hw.acpi.cpu
hw.acpi.cpu.max_speed: 8
hw.acpi.cpu.current_speed: 8
hw.acpi.cpu.performance_speed: 8
hw.acpi.cpu.economy_speed: 4
and, the clock
15 matches
Mail list logo