From owner-freebsd-arch@FreeBSD.ORG Sun Jan 11 18:08:13 2015 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4B1F62F; Sun, 11 Jan 2015 18:08:13 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 759F3D92; Sun, 11 Jan 2015 18:08:13 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so10636026wiw.1; Sun, 11 Jan 2015 10:08:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VnGetawWylm6NWbF7Xtqco8qkR2obuELXhzTC30b8q4=; b=eva84R1V5MkpdhSDeXpYHCYXilQD1pXiQVYtbQWnbJsgUYiaaKiquVWUdu8H28w+3E 7OUGdBWXIXmeSgVmywZNAz6zS6IZiInO7MFai5cO5jvGja6A43ipIIdVdXFL6kvm3rqP FInEbuOFmgBJTIAxxhLtPrqcNFq3P8N0DMwPNGaDOKbw0IQL7bx+U8u0pw2cOidesHFh 2KOKFQ9rghClon2CQSou3sf+nujZow1P0E7//K5HmMKieH5e0VKNgHYN9qSxv4Oy7d5i nvOpCRBKvoAj58Qko2JWPQeEApn5qt6jvr/5X+NC5fvugWnpmHrP7Ut4gBH7rmeRAgLX AMHQ== MIME-Version: 1.0 X-Received: by 10.194.234.40 with SMTP id ub8mr24213326wjc.100.1420999691727; Sun, 11 Jan 2015 10:08:11 -0800 (PST) Received: by 10.216.0.129 with HTTP; Sun, 11 Jan 2015 10:08:11 -0800 (PST) In-Reply-To: <54B29A49.3080600@selasky.org> References: <54A1B38C.1000709@selasky.org> <20150101005613.4f788b0c@nonamehost.local> <54A49CA5.2060801@selasky.org> <54A4A002.8010802@selasky.org> <54A53F4F.2000003@selasky.org> <54A92ED1.2070906@selasky.org> <54A9A71E.70609@selasky.org> <54B29A49.3080600@selasky.org> Date: Sun, 11 Jan 2015 11:08:11 -0700 Message-ID: Subject: Re: [RFC] kern/kern_timeout.c rewrite in progress From: Jason Wolfe To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: Adrian Chadd , FreeBSD Current , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2015 18:08:14 -0000 Hans, We've had 50 machines running 10.1-STABLE with this patch for the better part of a week without issue. Prior we would have seen a panic every few days at the least, so things are looking very promising on our front. Jason On Sun, Jan 11, 2015 at 8:44 AM, Hans Petter Selasky wrote: > On 01/07/15 00:10, Jason Wolfe wrote: >> >> >> Hans, >> >> We've been running into 'spin lock held too long' panics in the kernel >> idle threads on 10-STABLE over the past 6 months, so I was interested >> to see your work here in the callout code. I went ahead and brought >> this patch back to a recent 10.1-STABLE base without much issue, >> kern_timeout.c was actually the only piece with some easily resolvable >> rejections. >> >> I've had a box running stable under load with this patch for a few >> days, and 10 more have just been added to the rotation. Anyway just >> figured you might be interested in the some feedback while the changes >> are reviewed. >> > > Hi, > > Thank your for testing this patch. Any updates? > > --HPS >