From owner-freebsd-current@FreeBSD.ORG Sat Sep 18 16:54:58 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE9531065698; Sat, 18 Sep 2010 16:54:58 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from mtaout02-winn.ispmail.ntl.com (mtaout02-winn.ispmail.ntl.com [81.103.221.48]) by mx1.freebsd.org (Postfix) with ESMTP id 01AAE8FC19; Sat, 18 Sep 2010 16:54:57 +0000 (UTC) Received: from know-smtpout-4.server.virginmedia.net ([62.254.123.3]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20100918165456.IHAG3192.mtaout02-winn.ispmail.ntl.com@know-smtpout-4.server.virginmedia.net>; Sat, 18 Sep 2010 17:54:56 +0100 Received: from [86.27.35.5] (helo=unknown) by know-smtpout-4.server.virginmedia.net with esmtp (Exim 4.63) (envelope-from ) id 1Ox0gi-0000IY-L7; Sat, 18 Sep 2010 17:54:56 +0100 Date: Sat, 18 Sep 2010 17:54:52 +0100 From: Bruce Cran To: Alexander Motin Message-ID: <20100918175452.00003b6f@unknown> In-Reply-To: <4C94EC05.4070406@FreeBSD.org> References: <4C94EC05.4070406@FreeBSD.org> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=4QByPj+6Iq2k/6L54d+eVKTdgQxdscpRskJJReCfdXo= c=1 sm=0 a=3hKMM-ERg8wA:10 a=kj9zAlcOel0A:10 a=6I5d2MoRAAAA:8 a=3UN-ILmPtE4iyNsp15EA:9 a=tVVvfL-UV2JRiOiVEV0A:7 a=WIa4WGfKwUdkB2EXx45Fkwt98_YA:4 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Cc: FreeBSD-Current Subject: Re: One-shot timer broken on Xen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2010 16:54:59 -0000 On Sat, 18 Sep 2010 19:42:45 +0300 Alexander Motin wrote: > Bruce Cran wrote: > > I built a new kernel from HEAD on my Xen domU today and found that > > it hung after the following messages: > > > > smist0: on cpu0 > > device_attach: smist0 attach returned 6 > > Device configuration finished. > > procfs registered > > Timecounter "TSC" frequency 2000118476 Hz quality 800 > > lapic: Divisor 2, Frequency 50001605 Hz > > > > Setting kern.eventtimer.periodic to 1 allows the system to boot. > > This doesn't tells much. What event timers found by the system there > and what of them was used? Sorry - here's the kern.eventtimer output: kern.eventtimer.choice: LAPIC(400) i8254(100) RTC(0) kern.eventtimer.et.LAPIC.flags: 15 kern.eventtimer.et.LAPIC.frequency: 50001856 kern.eventtimer.et.LAPIC.quality: 400 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: 1 kern.eventtimer.timer: LAPIC kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 4 > Looking on kern.eventtimer.periodic support, I assume you are using > HVM? PV kernel wasn't refactored yet, but I think it would be nice. Yes, it's an i386 HVM system. > May be you could give me an access to some Xen machine? I'm going to be decomissioning another Xen machine so I can certainly give you access to that one. -- Bruce Cran