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.
> 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 do with the speed stepping of the CPU to save battery. Far as I know there's no fix yet. Guys is it possible to hack powerd to change a sysctl variable when it changes the CPU frequency or isn't it that simple? -Clay
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 clear about that, from what has been written already. --John -- LHPDR! SDF Public Access UNIX System - http://sdf.lonestar.org
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 ThinkPad T42p laptop.I'm sorry this isn't more conclusive... This almost sounds like an interrupt-related problem while in a power-saving state. I swear I just read a thread about this on -stable, pertaining to how certain power states disable features of interrupt controllers... I can't seem to find the discussion though, argh! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Fernando Jiménez Solano
2007-May-02 06:58 UTC
clock too slow - big time offset with ntpdate
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 an IBM ThinkPad T42p laptop. > > Can this be solved? > thanks > m.You have the option of running ntpd instead of ntpdate. This assures a continous polling against the server. IIRC ntpd would solve the clock skew via ntp.drift. -- How fortunate the man with none.
now i have both "acd0" and "cd0" is that a problem? bsd@/root# ls /dev acd0 cuad0.init kmem psm0 ttyv5 acpi cuad0.lock log ptyp0 ttyv6 ad0 devctl lpt0 ptyp1 ttyv7 ad0s1 devstat lpt0.ctl ptyp2 ttyv8 ad0s1a dsp0.0 mdctl random ttyv9 ad0s1b dsp0.1 mem sndstat ttyva ad0s1c dspW0.0 mixer0 stderr ttyvb ad0s1d dspW0.1 net stdin ttyvc ad0s2 dspr0.1 net1 stdout ttyvd agpgart fd net2 sysmouse ttyve apm fido net3 ttyd0 ttyvf ata fw0 net4 ttyd0.init ums0 atkbd0 fw0.0 network ttyd0.lock urandom audio0.0 fwmem0 nfs4 ttyp0 usb audio0.1 fwmem0.0 nfslock ttyp1 usb0 bpsm0 geom.ctl null ttyp2 usb1 cd0 io pass0 ttyv0 usb2 console kbd0 pccard0.cis ttyv1 usb3 consolectl kbd1 pccard1.cis ttyv2 xpt0 ctty kbdmux0 pci ttyv3 zero cuad0 klog ppi0 ttyv4 bsd@/root# On Wed, 2 May 2007, Gary Palmer wrote:> On Tue, May 01, 2007 at 08:41:40PM -0700, KAYVEN RIESE wrote: >> >> i was told by a guy on experts-exchange >> >> gheist: >> You have to install SCSI over ATAPI driver. GENERIC kernel does not have >> one. Only burncd in base system can use acd driver for burning CD/DVD, >> others do use SCSI cd driver > > You forgot to mention what release of FreeBSD you are running, but > in theory > > kldload atapicam > > from a root command prompt should fix it. If it does, put the line > > atapicam_load="YES" > > into /boot/loader.conf >
KAYVEN RIESE wrote:> now i have both "acd0" and "cd0" is that a problem? > > bsd@/root# ls /dev > acd0 cuad0.init kmem psm0 ttyv5 > acpi cuad0.lock log ptyp0 ttyv6 > ad0 devctl lpt0 ptyp1 ttyv7 > ad0s1 devstat lpt0.ctl ptyp2 ttyv8 > ad0s1a dsp0.0 mdctl random ttyv9 > ad0s1b dsp0.1 mem sndstat ttyva > ad0s1c dspW0.0 mixer0 stderr ttyvb > ad0s1d dspW0.1 net stdin ttyvc > ad0s2 dspr0.1 net1 stdout ttyvd > agpgart fd net2 sysmouse ttyve > apm fido net3 ttyd0 ttyvf > ata fw0 net4 ttyd0.init ums0 > atkbd0 fw0.0 network ttyd0.lock urandom > audio0.0 fwmem0 nfs4 ttyp0 usb > audio0.1 fwmem0.0 nfslock ttyp1 usb0 > bpsm0 geom.ctl null ttyp2 usb1 > cd0 io pass0 ttyv0 usb2 > console kbd0 pccard0.cis ttyv1 usb3 > consolectl kbd1 pccard1.cis ttyv2 xpt0 > ctty kbdmux0 pci ttyv3 zero > cuad0 klog ppi0 ttyv4 > bsd@/root#No, it is not a problem. It is meant to do that. And please do not top-post.> > On Wed, 2 May 2007, Gary Palmer wrote: > >> On Tue, May 01, 2007 at 08:41:40PM -0700, KAYVEN RIESE wrote: >>> >>> i was told by a guy on experts-exchange >>> >>> gheist: >>> You have to install SCSI over ATAPI driver. GENERIC kernel does not >>> have >>> one. Only burncd in base system can use acd driver for burning CD/DVD, >>> others do use SCSI cd driver >> >> You forgot to mention what release of FreeBSD you are running, but >> in theory >> >> kldload atapicam >> >> from a root command prompt should fix it. If it does, put the line >> >> atapicam_load="YES" >> >> into /boot/loader.conf >> > >
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(-1000000) > > To me it seems that you are running with acpi disabled. For example I have > this: > kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000) > kern.timecounter.hardware: ACPI-fast > > Re-enabling acpi may solve the problem.I have had so many problems with acpi, that this is not an option. Suspend impossible, pccards not working etc. m.