Date: Thu, 25 May 2000 21:40:31 -0400 From: "Douglas Smith" <dsmith@netway.com> To: <questions@FreeBSD.ORG>, <dsmith@netway.com> Subject: Help with "/kernel: calcru..." error on 4.0R Message-ID: <002601bfc6b3$622068c0$9c0dfea9@tower>
next in thread | raw e-mail | index | archive | help
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492193679 usec for
pid 172 (dnews)
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492194174 usec for
pid 172 (dnews)
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492194692 usec for
pid 172 (dnews)
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492195422 usec for
pid 172 (dnews)
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492195973 usec for
pid 172 (dnews)
May 25 21:38:13 news2 /kernel: calcru: negative time of 1492196513 usec for
pid 172 (dnews)
At a rate of about 120 a second. Also the time moves MUCH faster... An
hour takes about 10 minutes or even less than that.
The system can be up for anywhere from 10 minutes to 90 minutes before this
error starts...
[I am NOT on the BSD list so please if anyone responds please make sure to
CC me in email.]
I'm hoping someone can give me with some pointers in resolving this problem.
I will start out by saying what I HAVE done before someone decides to FLAME
me.
Searched freebsd.org and found:
>
>Q: My machine prints "calcru: negative time..."
>
>A: This can be caused by various hardware and/or software ailments relating
to >interrupts. It may be due to bugs but can also happen by nature of
certain >devices. Running TCP/IP over the parallel port using a large MTU is
one good >way to provoke this problem. Graphics accelerators can also get
you here, in >which case you should check the interrupt setting of the card
first.
>
>A side effect of this problem are dying processes with the message "SIGXCPU
>exceeded cpu time limit".
>
>For FreeBSD 3.0 and later from Nov 29, 1998 forward: If the problem cannot
be >fixed otherwise the solution is to set this sysctl variable:
>
> sysctl -w kern.timecounter.method=1
>
>This means a performance impact, but considering the cause of this problem,
>you probably will not notice. If the problem persists, keep the sysctl set
to one >and set the "NTIMECOUNTER" option in your kernel to increasingly
large values. >If by the time you have reached "NTIMECOUNTER=20" the problem
isn't solved, >interrupts are too hosed on your machine for reliable
timekeeping
>
I did the sysctl and it did not resolve the problem. I built three
different kernel's using NTIMECOUNTER=[10,15,20] without it helping at all.
Since none helped I am back to the GENERIC Kernel.
I contacted dnews support... They telnet'ed into the site and built a
dnews specific to my machine so that I would not be running a strange
binary. No help. They looed around and could not find out why this was
happening. They are sure it is not the software.
Here is my system:
AMD Athlon 800Mhz
Abit KA7 Motherboard
(4) 256Meg PC133 DIMM's
Intel EtherExpress PRO/100+ "Management Adapter" Ethernet Card
Trident PCI Video Card
Adaptec 39160 PCI SCSI Controller
(2) 9 Gig Quantum Atlas V ultra160 Drives (Set to 80Mbps)
(6) 18Gig Quantum Atlas V ultra160 Drives (Set to 80Mbps)
news2# uname -a
FreeBSD news2.mdc.net 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Mon Mar 20
22:50:22 GMT 2000 root@monster.cdrom.com:/usr/src/sys/compile/GENERIC
i386
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000
root@monster.cdrom.com:/usr/src/sys/compile/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x621 Stepping = 1
Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
PAT,PSE36,MMX,FXSR>
AMD Features=0xc0400000<AMIE,DSP,3DNow!>
real memory = 1073676288 (1048512K bytes)
config> di psm0
config> di sio1
config> di sio0
config> di ppc0
config> di sn0
config> di lnc0
config> di le0
config> di ie0
config> di fe0
config> di ed0
config> di cs0
config> di bt0
config> di ata1
config> di ata0
config> di aic0
config> di aha0
config> di adv0
config> q
avail memory = 1038553088 (1014212K bytes)
Preloaded elf kernel "kernel" at 0xc03c0000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc03c009c.
Pentium Pro MTRR support enabled
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: <PCI to PCI bridge (vendor=1106 device=8391)> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
isab0: <VIA 82C686 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA66 controller> port 0xd000-0xd00f at device 7.1 on
pci0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0xdc00-0xdc3f mem
0xd5200000-0xd52fffff,0xd5311000-0xd53
11fff irq 10 at device 9.0 on pci0
fxp0: Ethernet address 00:d0:b7:83:f2:13
fxp0: supplying EUI64: 00:d0:b7:ff:fe:83:f2:13
ahc0: <Adaptec 3960D Ultra160 SCSI adapter> port 0xe000-0xe0ff mem
0xd5312000-0xd5312fff irq 15 at device 15.
0 on pci0
ahc0: aic7899 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: <Adaptec 3960D Ultra160 SCSI adapter> port 0xe400-0xe4ff mem
0xd5310000-0xd5310fff irq 11 at device 15.
1 on pci0
ahc1: aic7899 Wide Channel B, SCSI Id=7, 16/255 SCBs
pci0: <Trident model 9440 VGA-compatible display device> at 17.0 irq 12
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-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
ahc1: Data Parity Error Detected during address or write data phase
ahc0: Data Parity Error Detected during address or write data phase
Waiting 15 seconds for SCSI devices to settle
da0 at ahc0 bus 0 target 0 lun 0
da0: <QUANTUM ATLAS_V__9_WLS 0200> Fixed Direct Access SCSI-3 device
da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da0: 8755MB (17930694 512 byte sectors: 255H 63S/T 1116C)
da4 at ahc1 bus 0 target 0 lun 0
da4: <QUANTUM ATLAS_V__9_WLS 0200> Fixed Direct Access SCSI-3 device
da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da4: 8755MB (17930694 512 byte sectors: 255H 63S/T 1116C)
da1 at ahc0 bus 0 target 1 lun 0
da1: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da1: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
da5 at ahc1 bus 0 target 1 lun 0
da5: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da5: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da5: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
da2 at ahc0 bus 0 target 2 lun 0
da2: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da2: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
da6 at ahc1 bus 0 target 2 lun 0
da6: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da6: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da6: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
da3 at ahc0 bus 0 target 3 lun 0
da3: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da3: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
da7 at ahc1 bus 0 target 3 lun 0
da7: <QUANTUM ATLAS_V_18_WLS 0200> Fixed Direct Access SCSI-3 device
da7: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing
Enabled
da7: 17510MB (35861388 512 byte sectors: 255H 63S/T 2232C)
Mounting root from ufs:/dev/da0s1a
fxp0: starting DAD for fe80:0001::02d0:b7ff:fe83:f213
fxp0: DAD complete for fe80:0001::02d0:b7ff:fe83:f213 - no duplicates found
Thanks,
Doug
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002601bfc6b3$622068c0$9c0dfea9>