Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Don Lewis wrote: > The silent reboots that I was seeing with WITNESS go away if I add > WITNESS_SKIPSPIN. Witness doesn't complain about anything. I've tracked down the the silent reboot problem. It happens when a userland sysctl call gets down into calcru1(), which tries to print a

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: > on 30/09/2010 02:27 Don Lewis said the following: >> I tried enabling apic and got worse results. I saw ping RTTs as high as >> 67 seconds. Here's the timer info with apic enabled: [snip] >> Here's the verbose boot info with apic: >>

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 30 Sep, Andriy Gapon wrote: > on 30/09/2010 02:27 Don Lewis said the following: > vmstat -i ? I didn't see anything odd in the vmstat -i output that I posted to the list earlier. It looked more or less normal as the ntp offset suddenly went insane. >> I did manage to catch the problem with

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

on 30/09/2010 02:27 Don Lewis said the following: > On 29 Sep, Andriy Gapon wrote: >> on 29/09/2010 11:56 Don Lewis said the following: >>> I'm using the same kernel config as the one on a slower !SMP box which >>> I'm trying to squeeze as much performance out of as possible. My kernel >>> config

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Andriy Gapon wrote: > on 29/09/2010 11:56 Don Lewis said the following: >> I'm using the same kernel config as the one on a slower !SMP box which >> I'm trying to squeeze as much performance out of as possible. My kernel >> config file contains these statements: >> nooptions

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

on 29/09/2010 11:56 Don Lewis said the following: > I'm using the same kernel config as the one on a slower !SMP box which > I'm trying to squeeze as much performance out of as possible. My kernel > config file contains these statements: > nooptions SMP > nodeviceapic >

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Andriy Gapon wrote: > on 29/09/2010 00:11 Don Lewis said the following: >> On 28 Sep, Don Lewis wrote: >> >> >>> % vmstat -i >>> interrupt total rate >>> irq0: clk 60683442 1000 >>> irq1: atkbd0 6

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

on 29/09/2010 00:11 Don Lewis said the following: > On 28 Sep, Don Lewis wrote: > > >> % vmstat -i >> interrupt total rate >> irq0: clk 60683442 1000 >> irq1: atkbd0 6 0 >> irq8: rtc

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Jeremy Chadwick wrote: > On Wed, Sep 29, 2010 at 12:39:49AM -0700, Don Lewis wrote: >> On 29 Sep, Jeremy Chadwick wrote: >> >> > Given all the information here, in addition to the other portion of the >> > thread (indicating ntpd reports extreme offset between the system clock >> > and

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On Wed, Sep 29, 2010 at 12:39:49AM -0700, Don Lewis wrote: > On 29 Sep, Jeremy Chadwick wrote: > > > Given all the information here, in addition to the other portion of the > > thread (indicating ntpd reports extreme offset between the system clock > > and its stratum 1 source), I would say the mo

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 29 Sep, Jeremy Chadwick wrote: > Given all the information here, in addition to the other portion of the > thread (indicating ntpd reports extreme offset between the system clock > and its stratum 1 source), I would say the motherboard is faulty or > there is a system device which is behaving b

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On Tue, Sep 28, 2010 at 10:31:27PM -0700, Don Lewis wrote: > On 28 Sep, Don Lewis wrote: > > > Looking at the timestamps of things and comparing to my logs, I > > discovered that the last instance of ntp instability happened when I was > > running "make index" in /usr/ports. I tried it again with

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Don Lewis wrote: > Looking at the timestamps of things and comparing to my logs, I > discovered that the last instance of ntp instability happened when I was > running "make index" in /usr/ports. I tried it again with entertaining > results. After a while, the machine became unrespons

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Jeremy Chadwick wrote: > Still speaking purely about ntpd: > > The above doesn't indicate a single problem. The deltas shown in both > delay, offset, and jitter are all 100% legitimate. A dd (to induce more > interrupt use) isn't going to exacerbate the problem (depending on your > s

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Don Lewis wrote: > % vmstat -i > interrupt total rate > irq0: clk 60683442 1000 > irq1: atkbd0 6 0 > irq8: rtc7765537127 > irq9: acpi0

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Jeremy Chadwick wrote: > On Tue, Sep 28, 2010 at 10:15:34AM -0700, Don Lewis wrote: >> My time source is another FreeBSD box with a GPS receiver on my LAN. My >> other client machine isn't seeing these time jumps. The only messages >> from ntp in its log from this period are these: >>

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On Tue, Sep 28, 2010 at 10:15:34AM -0700, Don Lewis wrote: > My time source is another FreeBSD box with a GPS receiver on my LAN. My > other client machine isn't seeing these time jumps. The only messages > from ntp in its log from this period are these: > > Sep 23 04:12:23 mousie ntpd[]: ke

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On 28 Sep, Chip Camden wrote: > Quoth Don Lewis on Monday, 27 September 2010: >> CPU time accounting is broken on one of my machines running 8-STABLE. I >> ran a test with a simple program that just loops and consumes CPU time: >> >> % time ./a.out >> 94.544u 0.000s 19:14.10 8.1% 62+2054k 0+0io 0

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

Quoth Don Lewis on Monday, 27 September 2010: > CPU time accounting is broken on one of my machines running 8-STABLE. I > ran a test with a simple program that just loops and consumes CPU time: > > % time ./a.out > 94.544u 0.000s 19:14.10 8.1% 62+2054k 0+0io 0pf+0w > > The display in top shows

Re: CPU time accounting broken on 8-STABLE machine after a few hours of uptime

On Mon, Sep 27, 2010 at 09:25:10PM -0700, Don Lewis wrote: > CPU time accounting is broken on one of my machines running 8-STABLE. I > ran a test with a simple program that just loops and consumes CPU time: > > % time ./a.out > 94.544u 0.000s 19:14.10 8.1% 62+2054k 0+0io 0pf+0w > > The display

CPU time accounting broken on 8-STABLE machine after a few hours of uptime

CPU time accounting is broken on one of my machines running 8-STABLE. I ran a test with a simple program that just loops and consumes CPU time: % time ./a.out 94.544u 0.000s 19:14.10 8.1%62+2054k 0+0io 0pf+0w The display in top shows the process with WCPU at 100%, but TIME increments very sl