In message <86lispaztm.fsf_at_ds4.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= wr ites: >Dag-Erling Sm=C3=B8rgrav <des_at_des.no> writes: >> I've just built a kernel with KTR support, and with KTR_SPARE2, KTR_INTR >> and KTR_SCHED enabled by default. I'll see what turns up. I'm also >> going to try machdep.idle=3Dhlt with kern.eventtimer.idletick=3D0, and us= >ing >> a PCI re(4) instead of the on-board msk(4) while running with default >> settings. > >Great, the bug does not occur when KTR is enabled. The machine has been >up for 14+ hours without crashing, despite plenty of network activity, >which usually triggers a freeze within minutes. For what it's worth, I regularly (=every 10-12 days or so) see all timer activity in the system die and have to use the 4-sec power-switch to get the system down. This is on: FreeBSD critter.freebsd.dk 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r224239M: Fri Aug 19 14:35:16 UTC 2011 phk_at_critter.freebsd.dk:/sys/amd64/compile/CRITTER amd64 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Thu Oct 13 2011 - 10:10:08 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:19 UTC