On Wed, 9 May 2007, Ian Smith wrote:
Bottom line might be: if it hurts when you run powerd with APM,
don't.
If you want powerd to work, I'd suggest trying ACPI again
ok, using ACPI solved the clock problem, the suspend problem
has to be solved later
m.
On Thu, 3 May 2007, Martin Dieringer wrote:
> On Thu, 3 May 2007, Ian Smith wrote:
> >
> > > > Now I got following while playing sound on the Compaq:
> > > >
> > > > kernel: calcru: runtime went backwards from 183711700 usec to
> > > > 183167434 usec for pid 12 (swi4: clock sio)
> > > >
>
On Thu, 3 May 2007, Pieter de Goeje wrote:
On Thursday 03 May 2007, Martin Dieringer wrote:
# sysctl kern.timecounter
kern.timecounter.hardware: i8254
kern.timecounter.choice: TSC(-1000) i8254(0) dummy(-100)
To me it seems that you are running with acpi disabled. For example I have
this:
On Thursday 03 May 2007, Martin Dieringer wrote:
> # sysctl kern.timecounter
> kern.timecounter.hardware: i8254
> kern.timecounter.choice: TSC(-1000) i8254(0) dummy(-100)
To me it seems that you are running with acpi disabled. For example I have
this:
kern.timecounter.choice: TSC(800) ACPI-fa
On Thu, 3 May 2007, Ian Smith wrote:
> > Now I got following while playing sound on the Compaq:
> >
> > kernel: calcru: runtime went backwards from 183711700 usec to 183167434
usec for pid 12 (swi4: clock sio)
> >
> > here I have a working clock, but also intermittent sound output
To which I s
On Thu, 3 May 2007, Martin Dieringer wrote:
> On Wed, 2 May 2007, Doug Barton wrote:
>
> > Martin Dieringer wrote:
> >
> >> On Wed, 2 May 2007, John Walthall wrote:
> >>
> >>> On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> I think it has to do with powerd, if I
On Wed, 2 May 2007, Doug Barton wrote:
Martin Dieringer wrote:
On Wed, 2 May 2007, John Walthall wrote:
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
I think it has to do with powerd, if I kill that, the time stays correct.
With powerd enabled, are you able to maintain
On Wed, May 02, 2007 at 02:30:38PM -0700, Kevin Oberman wrote:
> A few more comments:
>
> If ntpd is started with the '-g' flag, it will initially step the time
> so you get your clock set as you would have with ntpdate. This is set in
> /etc/rc.conf as 'ntpd_flags="-p /var/run/ntpd.pid -f /var/db
> Date: Wed, 2 May 2007 20:02:54 +0200
> From: Henrik Brix Andersen <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> On Wed, May 02, 2007 at 10:23:09AM -0700, Doug Barton wrote:
> [snip /etc/ntp.conf configuration file instructions]
> > Then make sure you have the following in /etc/rc.conf:
>
On Wed, May 02, 2007 at 10:23:09AM -0700, Doug Barton wrote:
[snip /etc/ntp.conf configuration file instructions]
> Then make sure you have the following in /etc/rc.conf:
>
> ntpdate_enable="yes"
> ntpdate_flags="-sb 1.2.3.4"
> ntpd_enable="yes"
Just a side note - according to the ntpdate(8)
Martin Dieringer wrote:
On Wed, 2 May 2007, John Walthall wrote:
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
I think it has to do with powerd, if I kill that, the time stays
correct.
With powerd enabled, are you able to maintain a "reasonably"
correct time with frequen
On Wed, 2007-05-02 at 04:04 +0200, Martin Dieringer wrote:
>
> the hiccups have reappeared, so they are not related to powerd.
>
> I still have 0.5 seconds time offsets after 10 minutes, on the
> thinkpad, without powerd...
>
> m.
I think the two effects (losing time, sound hiccups) are unrelat
On Wed, 2 May 2007, Martin Dieringer wrote:
[chomping, ccs too]
> >> > >>> I get about half a second time offsets after 10 seconds, and more
> >> > >>> than 100s after half an hour or so.
> >> > >>> I think it has to do with powerd, if I kill that, the time stays
> >> correct.
> >> > >>> It
On Wed, 2 May 2007, Martin Dieringer wrote:
On Wed, 2 May 2007, Ian Smith wrote:
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10
On Wed, 2 May 2007, Ian Smith wrote:
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10 seconds, and more
> >>> than 100s after half an
On Wed, 2 May 2007, John Walthall wrote:
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
I think it has to do with powerd, if I kill that, the time stays correct.
With powerd enabled, are you able to maintain a "reasonably"
correct time with frequent NTP syncronizations?
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10 seconds, and more
> >>> than 100s after half an hour or so.
> >>> I think it
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> Hi,
>
> I get about half a second time offsets after 10 seconds, and more
> than 100s after half an hour or so.
> I think it has to do with powerd, if I kill that, the time stays correct.
> It happens both on a Compaq nc4000 and a
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> I get about half a second time offsets after 10 seconds, and more
> than 100s after half an hour or so.
> I think it has to do with powerd, if I kill that, the time stays correct.
> It happens both on a Compaq nc4000 and an IBM
On Tue, 1 May 2007, Martin Dieringer wrote:
On Tue, 1 May 2007, Clayton Milos wrote:
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> I think it has to do with powerd, if I kill that, the time stays correct.
With powerd enabled, are you able to maintain a "reasonably" correct time with
frequent NTP syncronizations? Sorry if it's just me, but I am not quite clea
On Tuesday 01 May 2007 18:10:38 Martin Dieringer wrote:
> not to mention the energy waste
power off solve this if it is really your issue ... :S
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacent
On Tue, 1 May 2007, Clayton Milos wrote:
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can t
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can this be solved?
thanks
m.
This has got to
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can this be solved?
thanks
m.
_
25 matches
Mail list logo
