Date: Mon, 15 Aug 2011 09:31:07 -0400 From: Joe Schaefer <joesuf4@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: Clock stalls on Sabertooth 990FX Message-ID: <CAOzHqcJMWrO1Q-v8WpzxnyB0-TMQvVaBC9WQ6Qf_CkK_FtT3VA@mail.gmail.com> In-Reply-To: <4E4911F1.9030808@FreeBSD.org> References: <CAOzHqcJMZkJUOqtz29ZaC98azfJJo5efzF557gijv3ORMNkucg@mail.gmail.com> <4E4911F1.9030808@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 15, 2011 at 8:32 AM, Andriy Gapon <avg@freebsd.org> wrote: > on 13/08/2011 20:16 Joe Schaefer said the following: >> Brand new machine with a Phenom II X6 1100T and under chronic load >> the clock will stop running periodically until the machine eventually co= mpletely >> freezes. =C2=A0Note: during these stalls the kernel is still running, th= e >> machine is still >> mostly responsive, it's just that the clock is frozen in time. >> >> I've disabled Turbo mode in the bios and toyed with just about every >> other setting but nothing seems to resolve this problem. =C2=A0Based on = the behavior >> of the machine (just making buildworld will eventually kill it, upping >> the -j flag >> just kills it faster), I'm guessing it has something to do with the >> Digi+ VRM features >> but again nothing I've tried modifying in the bios seems to help. >> >> I've tried both 8.2-RELEASE and FreeBSD 9 (head). =C2=A0Running head now= with >> a dtrace enabled kernel. >> >> Suggestions? > > On head, start with checking what source is used for driving clocks: > sysctl kern.eventtimer % sysctl kern.eventtimer [master] kern.eventtimer.choice: HPET(450) HPET1(450) HPET2(450) LAPIC(400) i8254(100) RTC(0) kern.eventtimer.et.LAPIC.flags: 15 kern.eventtimer.et.LAPIC.frequency: 0 kern.eventtimer.et.LAPIC.quality: 400 kern.eventtimer.et.HPET.flags: 3 kern.eventtimer.et.HPET.frequency: 14318180 kern.eventtimer.et.HPET.quality: 450 kern.eventtimer.et.HPET1.flags: 3 kern.eventtimer.et.HPET1.frequency: 14318180 kern.eventtimer.et.HPET1.quality: 450 kern.eventtimer.et.HPET2.flags: 3 kern.eventtimer.et.HPET2.frequency: 14318180 kern.eventtimer.et.HPET2.quality: 450 kern.eventtimer.et.i8254.flags: 1 kern.eventtimer.et.i8254.frequency: 1193182 kern.eventtimer.et.i8254.quality: 100 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.periodic: 0 kern.eventtimer.timer: HPET kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 2 > > When the problem starts using vmstat -i to check interrupt rates and see = if any > relevant counter gets stuck. (during a buildworld run): joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 56943 1 irq19: ahci0 1004414 24 irq22: fwohci0 653499 16 irq46: atapci1 60047 1 irq256: hpet0:t0 8309347 205 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 93596 2 Total 10177889 251 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 57019 1 irq19: ahci0 1009467 24 irq22: fwohci0 653921 16 irq46: atapci1 60146 1 irq256: hpet0:t0 8381321 207 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 93694 2 Total 10255611 253 joe@sextant:~% date [mas= ter] Mon Aug 15 09:18:25 EDT 2011 joe@sextant:~% date [mas= ter] Mon Aug 15 09:18:27 EDT 2011 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 57410 1 irq19: ahci0 1019054 25 irq22: fwohci0 654275 16 irq46: atapci1 60230 1 irq256: hpet0:t0 8438249 208 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 93835 2 Total 10323096 254 joe@sextant:~% date [mas= ter] Mon Aug 15 09:19:41 EDT 2011 joe@sextant:~% date [mas= ter] Mon Aug 15 09:19:41 EDT 2011 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 57432 1 irq19: ahci0 1019054 25 irq22: fwohci0 654275 16 irq46: atapci1 60230 1 irq256: hpet0:t0 8438249 208 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 93852 2 Total 10323135 254 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 57436 1 irq19: ahci0 1019054 25 irq22: fwohci0 654275 16 irq46: atapci1 60230 1 irq256: hpet0:t0 8438249 208 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 93866 2 Total 10323153 254 joe@sextant:~% date [mas= ter] Mon Aug 15 09:19:41 EDT 2011 joe@sextant:~% date [mas= ter] Mon Aug 15 09:24:16 EDT 2011 joe@sextant:~% date [mas= ter] Mon Aug 15 09:24:16 EDT 2011 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 59317 1 irq19: ahci0 1020250 24 irq22: fwohci0 654352 16 irq46: atapci1 60248 1 irq256: hpet0:t0 8440763 206 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 94258 2 Total 10329231 252 joe@sextant:~% vmstat -i [mas= ter] interrupt total rate irq16: hdac2 39 0 irq17: ehci0 ehci1+ 2 0 irq18: ohci0 ohci1* 59330 1 irq19: ahci0 1020471 24 irq22: fwohci0 654411 16 irq46: atapci1 60263 1 irq256: hpet0:t0 8442455 206 irq259: hdac0 1 0 irq260: hdac1 1 0 irq261: re0 94325 2 Total 10331298 252 joe@sextant:~% date [mas= ter] Mon Aug 15 09:24:33 EDT 2011
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOzHqcJMWrO1Q-v8WpzxnyB0-TMQvVaBC9WQ6Qf_CkK_FtT3VA>