Date: Fri, 17 Feb 2012 11:37:09 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.org> Cc: Alexander Kabaev <kan@FreeBSD.org>, threads@FreeBSD.org, FreeBSD Stable <freebsd-stable@FreeBSD.org>, David Xu <davidxu@FreeBSD.org>, Jung-uk Kim <jkim@FreeBSD.org> Subject: Re: pthread_cond_timedwait() broken in 9-stable? [possible answer] Message-ID: <4F3E1FC5.2020103@FreeBSD.org> In-Reply-To: <4F3DB3AE.5000109@freebsd.org> References: <4F3C2671.3090808__7697.00510795719$1329343207$gmane$org@freebsd.org> <4F3D3E2D.9090100@FreeBSD.org> <4F3D6FDD.9050808@freebsd.org> <4F3D89CD.9050309@freebsd.org> <4F3DA27A.3090903@freebsd.org> <4F3DB3AE.5000109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 17/02/2012 03:55 Julian Elischer said the following: > > kern.timecounter.tick: 1 > kern.timecounter.choice: TSC-low(1000) i8254(0) HPET(950) ACPI-fast(900) > dummy(-1000000) > kern.timecounter.hardware: ACPI-fast > kern.timecounter.stepwarnings: 0 > > switching the machine from TSC_low to ACPI-fast fixes the problem. > > in 8.x it used to default to ACPI > but I used to switch it to "TSC" to get better performance. > > I wonder why TSC-low is now bad to use.. > maybe the TSCs are not as well sychronised as they were in 8.x? > maybe the pthreads code didn't get the memo about changing timers? More useful information that you can provide: - C-states configuration - CPU identification I see that you've already contacted jkim, that's useful too. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3E1FC5.2020103>