In message <[EMAIL PROTECTED]>, Kyle Butt writes:
>> I've stared at the data file and I'll be damned if I can find anything
>> which would case the clock to double its speed :-(
>
>Perhaps something else is causing the clock to run twice as fast?
>Maybe two things that are working properly are b
At Sat, 30 Mar 2002 11:02:47 +0100,
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
> >In message <[EMAIL PROTECTED]>, David Malone writes:
> >>On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
> >>> This is an interesting machine: A K6 wiht
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes:
>In message <[EMAIL PROTECTED]>, David Malone writes:
>>On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
>>> This is an interesting machine: A K6 wiht ACPI, havn't seen that
>>> before.
>>
>>I had one of these machines and
At Wed, 27 Mar 2002 18:42:43 +0100,
Poul-Henning Kamp wrote:
>
>
> Can you put the file a place where I can fetch it ? my antique mailer
> cannot seem to extract it from your emails...
>
Sorry About that.
http://cc.usu.edu/~kylebutt/acpi-samples.gz
> --
> Poul-Henning Kamp | UNIX since
Can you put the file a place where I can fetch it ? my antique mailer
cannot seem to extract it from your emails...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to mali
egHLfXwBy31+Act9gQHLfYQBy32GAct9iAHLfYoBy32MAct9jgHLfZABy32TAct9lQHLfZcBy32Z
Act9mwHLfZ0By32fAct9ogHLfaUBy32nAct9qQHLfasBy32tAct9rwHLfbIBy320Act9tgHLfbgB
y326Act9vAHLfb4By33BAct9wwHLfcUBy33IAct9ygHLfcwBy33OAct90AHLfdMBy33VAct91wHL
fdkBy33bAct93QHLfd8By33hAct95AHLfeYBy33oAct96wHLfe0By33vAct98QHLffM
esp9W3rKfed6yn3pesp963rKfe16yn3vesp98XrKffN6yn32esp9+HrKffp6yn38esp9/nrKfQB7
yn0Ee8p9BnvKfQh7yn0Ke8p9DXvKfQ97yn0Re8p9E3vKfRV7yn0Xe8p9GXvKfRx7yn0ee8p9IHvK
fSJ7yn0ke8p9KHvKfSt7yn0te8p9L3vKfTF7yn0ze8p9NXvKfTh7yn06e8p9PHvKfT57yn1Ae8p9
QnvKfUR7yn1He8p9SXvKfU17yn1Pe8p9UXvKfVN7yn1We8p9WHvKfVp7yn1ce8p9Xnv
yX3mx8l96MfJferHyX3sx8l978fJffHHyX3zx8l99cfJfffHyX35x8l9/MfJff7HyX0ByMl9A8jJ
fQXIyX0HyMl9CcjJfQvIyX0NyMl9EMjJfRLIyX0UyMl9FsjJfRjIyX0ayMl9HMjJfR/IyX0iyMl9
JMjJfSbIyX0oyMl9KsjJfSzIyX0uyMl9McjJfTPIyX01yMl9N8jJfTnIyX07yMl9PcjJfUDIyX1E
yMl9RsjJfUjIyX1KyMl9TMjJfU/IyX1RyMl9U8jJfVXIyX1XyMl9WcjJfVvIyX1eyMl
fRNCyX0VQsl9F0LJfRlCyX0bQsl9HULJfSJCyX0kQsl9JkLJfShCyX0qQsl9LELJfS9CyX0xQsl9
M0LJfTVCyX03Qsl9OULJfTtCyX09Qsl9QELJfUJCyX1GQsl9SELJfUpCyX1MQsl9T0LJfVFCyX1T
Qsl9VULJfVdCyX1ZQsl9W0LJfV5CyX1gQsl9YkLJfWRCyX1mQsl9akLJfW1CyX1vQsl9cULJfXNC
yX11Qsl9d0LJfXpCyX18Qsl9fkLJfYBCyX2CQsl9hELJfYZCyX2JQsl9i0LJfY9CyX2
Kr3IfSy9yH0wvch9M73IfTW9yH03vch9Ob3IfTu9yH09vch9P73IfUK9yH1Evch9Rr3IfUi9yH1K
vch9TL3IfU69yH1Rvch9Vb3IfVe9yH1Zvch9W73IfV29yH1gvch9Yr3IfWS9yH1mvch9aL3IfWq9
yH1svch9b73IfXG9yH1zvch9db3IfXq9yH18vch9f73IfYG9yH2Dvch9hb3IfYe9yH2Jvch9i73I
fY69yH2Qvch9kr3IfZS9yH2Wvch9mL3IfZq9yH2fvch9ob3IfaO9yH2lvch9p73Ifam
fcSIy33GiMt9yIjLfcqIy33MiMt9zojLfdGIy33ViMt914jLfdmIy33biMt93YjLfd+Iy33iiMt9
5IjLfeaIy33oiMt96ojLfeyIy33uiMt98YjLffOIy331iMt9+YjLffuIy339iMt9AInLfQKJy30E
ict9BonLfQiJy30Kict9DInLfQ+Jy30Rict9E4nLfRWJy30Xict9GYnLfR6Jy30gict9IonLfSSJ
y30mict9KInLfSqJy30tict9L4nLfTGJy30zict9NYnLfTeJy305ict9PInLfT6Jy31
PMh9LDzIfS48yH0wPMh9MjzIfTU8yH03PMh9OTzIfTs8yH09PMh9PzzIfUE8yH1EPMh9RjzIfUo8
yH1MPMh9TjzIfVA8yH1TPMh9VTzIfVc8yH1ZPMh9WzzIfV08yH1gPMh9YjzIfWQ8yH1mPMh9aDzI
fWo8yH1vPMh9cTzIfXM8yH11PMh9dzzIfXk8yH17PMh9fjzIfYA8yH2CPMh9hDzIfYY8yH2IPMh9
ijzIfY08yH2PPMh9kzzIfZU8yH2XPMh9mTzIfZs8yH2ePMh9oDzIfaI8yH2kPMh9pjz
From: Kyle Butt <[EMAIL PROTECTED]>
To: Poul-Henning Kamp <[EMAIL PROTECTED]>
Cc: Kyle Butt <[EMAIL PROTECTED]>,
Dag-Erling Smorgrav <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Superfast clock on current.
In-Reply-To: <[EMAIL PROTECTED]>
References
In message <[EMAIL PROTECTED]>, Kyle Butt writes:
>At Wed, 27 Mar 2002 10:49:15 +0100,
>Poul-Henning Kamp wrote:
>>
>>
>> Uhm, I just whacked the code into my editor, you may need
>> more #includes like or
>
>Thanks. That did the trick. Now how do I go about finding that
>port? Is that somethi
At Wed, 27 Mar 2002 10:49:15 +0100,
Poul-Henning Kamp wrote:
>
>
> Uhm, I just whacked the code into my editor, you may need
> more #includes like or
Thanks. That did the trick. Now how do I go about finding that
port? Is that something I can glean from the dmesg, or do I have
to look somewhe
Uhm, I just whacked the code into my editor, you may need
more #includes like or
In message <[EMAIL PROTECTED]>, Kyle Butt writes:
>At Wed, 27 Mar 2002 08:42:49 +0100,
>
>bash-2.04$ gcc -o apci apci.c
>In file included from apci.c:2:
>/usr/include/machine/cpufunc.h:72: syntax error before `bsf
At Wed, 27 Mar 2002 08:42:49 +0100,
bash-2.04$ gcc -o apci apci.c
In file included from apci.c:2:
/usr/include/machine/cpufunc.h:72: syntax error before `bsfl'
/usr/include/machine/cpufunc.h:72: syntax error before `mask'
/usr/include/machine/cpufunc.h: In function `bsfl':
/usr/include/machine/cp
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Kyle Butt <[EMAIL PROTECTED]> writes:
>> My system clock is running twice as fast as it should be,
>> but it doesn't affect timing functions. Ex:
>> [...]
>> Has anyone else experienced this problem?
>
>I'm seeing the exact same problem
At Tue, 26 Mar 2002 07:40:10 -0700,
Kyle Butt wrote:
>
> At Tue, 26 Mar 2002 09:59:29 +0100,
> Poul-Henning Kamp wrote:
> >
> >
> > This is an interesting machine: A K6 wiht ACPI, havn't seen that
> > before.
> >
> > Could you please try to boot -v and give me the ACPI timecounter
> > probe li
Kyle Butt <[EMAIL PROTECTED]> writes:
> My system clock is running twice as fast as it should be,
> but it doesn't affect timing functions. Ex:
> [...]
> Has anyone else experienced this problem?
I'm seeing the exact same problem on, guess what...
FreeBSD 5.0-CURRENT #162: Sat Mar 23 19:49:09 CE
At Tue, 26 Mar 2002 09:59:29 +0100,
Poul-Henning Kamp wrote:
>
>
> This is an interesting machine: A K6 wiht ACPI, havn't seen that
> before.
>
> Could you please try to boot -v and give me the ACPI timecounter
> probe lines ? (about ten lines which talk about it being GOOD or
> BAD).
>
Her
In message <[EMAIL PROTECTED]>, David Malone writes:
>On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
>> This is an interesting machine: A K6 wiht ACPI, havn't seen that
>> before.
>
>I had one of these machines and concluded that the ACPI time counter
>was busted. I dunno if it
I too have experienced this problem with -current. I'm running on a Thinkpad A21p,
but with a fairly out-of-date build (September 1, 2001).
This happens, I believe. because the kernel thinks the processor is running at one
speed and then that speed changes to reflect different power management
On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote:
> This is an interesting machine: A K6 wiht ACPI, havn't seen that
> before.
I had one of these machines and concluded that the ACPI time counter
was busted. I dunno if it is possible to sanity check the time
counter before using
This is an interesting machine: A K6 wiht ACPI, havn't seen that
before.
Could you please try to boot -v and give me the ACPI timecounter
probe lines ? (about ten lines which talk about it being GOOD or
BAD).
Poul-Henning
In message <[EMAIL PROTECTED]>, Kyle Butt writes:
>My system clock is r
My system clock is running twice as fast as it should be,
but it doesn't affect timing functions. Ex:
bash-2.04$ date ; sleep 5 ; date
Tue Mar 26 01:48:45 MST 2002
Tue Mar 26 01:48:55 MST 2002
bash-2.04$
Has anyone else experienced this problem? I'm running X4.2.0 but
not from the ports. (I upg
26 matches
Mail list logo
