Date: Mon, 11 Jun 2001 10:47:54 +0100 From: Pete French <pfrench@firstcallgroup.co.uk> To: msmith@freebsd.org Cc: stable@FreeBSD.ORG Subject: Re: Very odd clock problem Message-ID: <E159OIc-000Pd8-00@dilbert.fcg.co.uk> In-Reply-To: <200106110001.f5B01k202445@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Er, the system clock is not capable of representing the year 1933 (in any
> valid fashion).
Well it surpised me too ! Can the system clock not take negative values
like time_t then ? (whatever type time_t happens to be this week :-) )
I was assuming it was a signed 32 bit number and was getting set to
something like 0xBB000000 or thereabouts.
> This sounds like either memory corruption or an in-kernel sniper bug of
> some sort. You don't help the diagnosis any by saying "losing time" and
> then complaining about a "jump". The two are very different things, and
> you need to be much more specific about what is actually happening.
Fair comment.
What happens specificly is this: I get a user (and its always the same user)
who complains that the dates on his outgoing emails are being timestamped in
1933. I login, type 'date' and sure enough it says it is a date in
1933. I then reset the date. There is nothing in the log files to indicate
what has happened - other than the date on other messages jumping back
to sometime in May (the year isnt logged in /var/log/messages I assume,
but the month change is very obvious and I am assuming this co-incides
with the year date change).
We were running ntpd, and stopped in case it was a corrupt ntp server
somewhere. That didnt help. We have also changed ntp servers to a different
set of machines. Once again to no effect. Could this be a clock
battery problem at all ? I wouldnt have thought the battery was used
with the machine powered up, but it is the only thing
I can think of off the top of my head. It happened again this morning,
there is no pattern to when the jumps occur that I can see.
Heres the output of dmesg to sow you what harwarde the machine is running
on. Anything else I can do to provide more info ?
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.3-STABLE #0: Thu May 31 11:28:05 BST 2001
pete@toybox.twisted.org.uk:/usr/obj/usr/src/sys/TOYBOX
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 267274587 Hz
CPU: AMD-K6(tm) 3D processor (267.27-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x58c Stepping = 12
Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>
AMD Features=0x80000800<SYSCALL,3DNow!>
real memory = 67043328 (65472K bytes)
avail memory = 62058496 (60604K bytes)
Preloaded elf kernel "kernel" at 0xc0330000.
K6-family MTRR support enabled (2 registers)
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
pci0: <VIA 85C586 ATA controller> at 7.1
pci0: <VIA 83C572 USB controller> at 7.2 irq 15
pci0: <ATI Mach64-GU graphics accelerator> at 8.0
xl0: <3Com 3c900B-TPO Etherlink XL> port 0xdc00-0xdc7f mem 0xe8002000-0xe800207f irq 11 at device 9.0 on pci0
xl0: Ethernet address: 00:50:da:38:22:5c
xl0: selecting 10baseT transceiver, half duplex
ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xe000-0xe0ff mem 0xe8001000-0xe8001fff irq 10 at device 11.0 on pci0
aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/da0s1a
da1 at ahc0 bus 0 target 1 lun 0
da1: <COMPAQ HB00441AA2 5541> Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <COMPAQ DDRS-34560W S99C> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C)
WARNING: / was not properly dismounted
uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 15 at device 7.2 on pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E159OIc-000Pd8-00>