Re: too short/too long (sys/kern_tc.c)



On 02/27/07 08:25, Etienne Robillard wrote:
Had this problem for a while.. It seems
to have disappear when booting with acpi enabled??

Oh - jsut realized it wasn't loaded (etherbooting doesn't load the modules, and I've been spoiled by having it autoload). Adding to my kernel now.

Dunno what may cause your bug, however I still gets
some of this:

calcru: runtime went backwards from 37004444177421276
usec to 18502193351497934 usec for pid 81026 (zsh)

FreeBSD flick 7.0-CURRENT FreeBSD 7.0-CURRENT #13: Mon
Jan 29 14:05:04 EST 2007 root@flick:/usr/src/sys/i386/compile/CURRENT i386


Are both bugs described correlated?

I don't know for sure. Seems that slamming the CPU to 100% busy makes the messages occur much less.

Yikes! Look at this:

# vmstat -i
interrupt total rate
irq0: clk 8299985 116
irq1: atkbd0 67 0
irq4: sio0 5325 0
irq8: rtc 1065804 14
irq11: re0 73060 1
irq14: ata0 15 0
irq15: ata1 58 0
Total 9444314 132

Maybe acpi will help that too.

Eric



TIA,
Etienne


--- Eric Anderson <anderson@xxxxxxxxxxx> wrote:

When I boot a -CURRENT box with boot verbose enabled
inside qemu, I see
one of these messages about every second:

15.f68c5ee76faebe10 too short
16.0f822e13092c5580 too long

I can obviously whack the printf's, but what's the
'right way' to fix
this? Set HZ to something? Pick a different timer?

kern.timecounter.tick: 1
kern.timecounter.choice: TSC(800) i8254(0)
dummy(-1000000)
kern.timecounter.hardware: TSC
kern.timecounter.nsetclock: 2
kern.timecounter.ngetmicrotime: 80036
kern.timecounter.ngetnanotime: 0
kern.timecounter.ngetbintime: 0
kern.timecounter.ngetmicrouptime: 29057
kern.timecounter.ngetnanouptime: 109
kern.timecounter.ngetbinuptime: 488
kern.timecounter.nmicrotime: 1708
kern.timecounter.nnanotime: 11
kern.timecounter.nbintime: 1719
kern.timecounter.nmicrouptime: 687
kern.timecounter.nnanouptime: 0
kern.timecounter.nbinuptime: 3734
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.mask: 4294967295
kern.timecounter.tc.i8254.counter: 7769
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.TSC.mask: 4294967295
kern.timecounter.tc.TSC.counter: 809045640
kern.timecounter.tc.TSC.frequency: 1995115260
kern.timecounter.tc.TSC.quality: 800
kern.timecounter.smp_tsc: 0

FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Fri Feb
23 09:28:20 CST
2007 i386

Eric


_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscribe@xxxxxxxxxxx"



----
Etienne Robillard
7680 de jouvence, La Plaine
J7M-2K9, Québec
Telephone: 450-478-5026
Yahoo Messenger ID: granted14
Skype ID: incidah

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: too short/too long (sys/kern_tc.c)
    ... Indeed adding ACPI fixed that problem, and also increased the processing performance of my qemu machine by around a factor of 5x. ... FreeBSD flick 7.0-CURRENT FreeBSD 7.0-CURRENT #13: ... Yahoo Messenger ID: granted14 ... Mail has the best spam protection around http://mail.yahoo.com ...
    (freebsd-current)
  • Re: Centrino - Made for Microsoft Windows XP?
    ... I have a dell D600 and FreeBSD works with no problem ... I think I had some problems with ACPI but then I fixed ... that prob. ... Información de Estados Unidos y América Latina, en Yahoo! ...
    (freebsd-questions)
  • Re: Panic during boot
    ... So ACPI is dispabled. ... >> freeBSD using boot floppies kern.flp and ... Do you Yahoo!? ...
    (freebsd-questions)
  • Interrupt storm on an MS-1029 (AMD Turion 64)
    ... FreeBSD 6.1 runs very slowly out of the box on my MS-1029 AMD Turion ... Booting in safe mode and with ACPI disabled did not help. ... driver was still using irq19 and was having an interrupt storm. ... <ACPI PCI bus> on pcib0 ...
    (freebsd-questions)
  • Re: Cannot get freebsd up and running...
    ... Well, I don't wish to offend, but if that message was formatted anything like this one, probably nobody at that forum wished to deal with it. ... SeaGate ST340810A Hard drive as slave (This one has FreeBSD on it) ... Almost everything you're discussing here depends on the motherboard. ... ACPI I got through the installer by ...
    (freebsd-questions)