On Tue, 12 Jun 2007, Matthew Dillon wrote:
MD> :s,/kernel,/boot/kernel/kernel, ;-)
MD> :
MD> :well, strange enough result for me:
MD> :
MD> :(kgdb) print cpu_ticks
MD> :$1 = (cpu_tick_f *) 0x8036cef0
MD> :
MD> :Does this mean that kernel uses tsc? sysctl reports
MD> :
MD> :kern.timecounte
:s,/kernel,/boot/kernel/kernel, ;-)
:
:well, strange enough result for me:
:
:(kgdb) print cpu_ticks
:$1 = (cpu_tick_f *) 0x8036cef0
:
:Does this mean that kernel uses tsc? sysctl reports
:
:kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-100)
:kern.timecounter.hardw
On Mon, 11 Jun 2007, Matthew Dillon wrote:
MD>
MD>
:==
MD> : cs3661.rinet.ru 192.38.7.240 2 u 354 1024 3775.305 -66314.
4321.47
MD> : ns.rinet.ru 130.207.244.240 2 u 365 1024 3776.913 -66316.
430
:==
: cs3661.rinet.ru 192.38.7.240 2 u 354 1024 3775.305 -66314. 4321.47
: ns.rinet.ru 130.207.244.240 2 u 365 1024 3776.913 -66316. 4305.33
: whale.rinet.ru 195.2.64.5 2 u 358 1024 3777
On Sat, 9 Jun 2007, Matthew Dillon wrote:
MD> :Well, I can of course shut the kernel up, but kernel time stability is
still my
MD> :concern. I run ntpd there and while sometimes it seems stable (well,
sorta:
MD> :drift are within several seconds...) there are cases of half-a-minute time
MD> :
DM> MD> :Well, I can of course shut the kernel up, but kernel time stability is
still my
DM> MD> :concern. I run ntpd there and while sometimes it seems stable (well,
sorta:
DM> MD> :drift are within several seconds...) there are cases of half-a-minute
time
DM> MD> :steps.
DM> MD>
DM> MD>
On Sat, 9 Jun 2007, Matthew Dillon wrote:
MD> :Well, I can of course shut the kernel up, but kernel time stability is
still my
MD> :concern. I run ntpd there and while sometimes it seems stable (well,
sorta:
MD> :drift are within several seconds...) there are cases of half-a-minute time
MD> :
:Well, I can of course shut the kernel up, but kernel time stability is still
my
:concern. I run ntpd there and while sometimes it seems stable (well, sorta:
:drift are within several seconds...) there are cases of half-a-minute time
:steps.
:
:Sincerely,
:D.Marck
On Sat, 9 Jun 2007, Matthew Dillon wrote:
MD> :Hmm, i'm not sure I understand you right: what do you mean by 'kgdb live
MD> :kernel'? I send break over serial console, and in ddb got
MD> :
MD> :db> print cpu_ticks
MD> :Symbol not found
MD> :
MD> :Sincerely,
MD> :D.Marck
:Hmm, i'm not sure I understand you right: what do you mean by 'kgdb live
:kernel'? I send break over serial console, and in ddb got
:
:db> print cpu_ticks
:Symbol not found
:
:Sincerely,
:D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
I think it works the same on Fr
On Wed, 6 Jun 2007, Matthew Dillon wrote:
MD> :IV> > Upd: on GENERIC/amd64 kernel I got the same errors.
MD> :IV>
MD> :IV> Do you perhaps run with TSC timecounter? (that's the only cause I've
notice
MD> :IV> that can generate this message).
MD> :
MD> :Nope:
MD> :
MD> :[EMAIL PROTECTED]:~> sysctl
On Wednesday 06 June 2007 17:17:28 Ivan Voras wrote:
> Dmitry Morozovsky wrote:
> > Dear colleagues,
> >
> > on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP
> > kernel I got zillions of 'runtime went backwards' errors, both on i386
> > and amd64 kernels.
> >
> > Upd: on GENERIC/
:IV> > Upd: on GENERIC/amd64 kernel I got the same errors.
:IV>
:IV> Do you perhaps run with TSC timecounter? (that's the only cause I've notice
:IV> that can generate this message).
:
:Nope:
:
:[EMAIL PROTECTED]:~> sysctl kern.timecounter
:kern.timecounter.tick: 1
:kern.timecounter.choice: TSC(-1
On Wed, 6 Jun 2007, Ivan Voras wrote:
IV> > on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel
IV> > I got zillions of 'runtime went backwards' errors, both on i386 and amd64
IV> > kernels.
IV> >
IV> > Upd: on GENERIC/amd64 kernel I got the same errors.
IV>
IV> Do you per
Dmitry Morozovsky wrote:
Dear colleagues,
on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel I
got zillions of 'runtime went backwards' errors, both on i386 and amd64
kernels.
Upd: on GENERIC/amd64 kernel I got the same errors.
Do you perhaps run with TSC timecounte
Dear colleagues,
on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel I
got zillions of 'runtime went backwards' errors, both on i386 and amd64
kernels.
Upd: on GENERIC/amd64 kernel I got the same errors.
Any hints to eliminate this? Thanks in advance.
Sincerely,
D.Marck
16 matches
Mail list logo