From owner-freebsd-current@FreeBSD.ORG Tue May 10 01:29:40 2011 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 EF201106564A for ; Tue, 10 May 2011 01:29:39 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6AB8FC13 for ; Tue, 10 May 2011 01:29:39 +0000 (UTC) Received: by wwc33 with SMTP id 33so5983873wwc.31 for ; Mon, 09 May 2011 18:29:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9yh0sGLfUq4ySMmUTmMZ0LjHTvhWmJes8ubje4WaQqs=; b=chixmA5MtCKX1oT4AohfdbeVvoF3s6/yHAWBMpDaXOMqcTyy8KWAj3ibFwU/SsL138 CXEhEtgoTXCuCCZuVyofK449+dcXlqDhE9AoxB7dk7AgCjYj0K4DVIK3Jt+O9GZYZm7N 2K5OhrlYoMMmBj5rdT0j4DPUIu5xSTMHJna5c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=CiAZQJtQaQQIczU3rGLxemwYU6AnbOQE+i1ikOKDSg3okFuzQKgvBpqB8k9vVsuI2v ztVvxPY3gBWonh96lt0e08czfXIm2gh0gdSPxxresMkcD/AbI57PC2pL08QA1RKC/4/V VfnvuU3V+fZXaEkigI4YUqpTPFokC8ufpVuHY= Received: by 10.227.157.134 with SMTP id b6mr7334608wbx.59.1304990978390; Mon, 09 May 2011 18:29:38 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (95-109-173-184.dialup.umc.net.ua [95.109.173.184]) by mx.google.com with ESMTPS id z9sm4092117wbx.0.2011.05.09.18.29.33 (version=SSLv3 cipher=OTHER); Mon, 09 May 2011 18:29:37 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DC894F5.5040804@FreeBSD.org> Date: Tue, 10 May 2011 04:29:25 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110310 Thunderbird/3.1.9 MIME-Version: 1.0 To: Doug Barton References: <4DC25396.1070909@dougbarton.us> <4DC30EC5.3090703@FreeBSD.org> <4DC50804.6000809@dougbarton.us> <4DC51434.3000501@FreeBSD.org> <4DC87D68.30707@dougbarton.us> In-Reply-To: <4DC87D68.30707@dougbarton.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: My problems with stability on -current 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: Tue, 10 May 2011 01:29:40 -0000 On 10.05.2011 02:48, Doug Barton wrote: >>>> I would start from most obvious problems. I need to know more about >>>> crashes. As usual: how to trigger, stack backtraces, etc. >>> >>> Triggering is easy, I can start a buildworld with -j2, and a build of >>> ports/www/firefox with FORCE_MAKE_JOBS, and within 30 minutes the system >>> will reboot. I posted a panic message relative to r220282, (-current >>> archives, 4/4) but kib said it didn't make any sense. Usually I don't >>> get a panic at all. >> >> Could you hint me the thread? > > Go to http://www.FreeBSD.org/ > Click 'mailing lists' > Click 'listed in the FreeBSD Handbook.' > Click freebsd-current > Click freebsd-current Archives > Click April 2011 > search for r220282 > Voila! :) OK, but URL would be fine also. :) I am agree with kib@ -- the message doesn't match the backtrace. >>>> What's about time problems, I would try to collect more data: >>>> - show `sysctl kern.eventtimer`, `sysctl kern.timecounter` and verbose >>>> dmesg outputs; >>> >>> http://people.freebsd.org/~dougb/dougb-current-r221566.txt >>> >>>> - what eventtimer is used now and does it helps to switch to another >>>> one with kern.eventtimer.timer sysctl? >>> >>> When I was trying to track down the problems last summer I vaguely >>> remember trying RTC, but eventually we realized that the real problem >>> was throttling, so I stopped specifying RTC and let it go back to the >>> default. What do you suggest I try? >> >> As I see, now you are using HPET (chosen automatically). I would try >> switch to the LAPIC. Just make sure to disable C-states if you are >> enabled them to be sure that LAPIC timer won't stop. > > Ok, so kern.eventtimer.timer="LAPIC" in /boot/loader.conf should do > that, right? Yes. You can do it in run-time also. > I don't use C-states (in part as a result of previous investigation) but > I do use powerd as such: > powerd_flags="-a adaptive -b adaptive -n adaptive" > >>>> - does the timer runs in periodic or one-shot mode and does it helps to >>>> switch to another one? >>> >>> How could I tell, and how would I switch? >> >> `sysctl kern.eventtimer.periodic`. > > kern.eventtimer.periodic: 0 > >> And read eventtimers(4) please. > > I did that, but I don't see anything in there as to which choice is > one-shot, and how to change to periodic. I assume 0 is the default, > which I also assume is one-shot. Does setting that to 1 change to > periodic? Also, can I safely do this while the system is running, or > should it be in /boot/loader.conf as well? Yes, nonzero value means periodic. And yes, changing in run-time is safe. -- Alexander Motin