From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 21:32:52 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B89D91065670 for ; Sat, 12 Sep 2009 21:32:52 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 45E8B8FC16 for ; Sat, 12 Sep 2009 21:32:51 +0000 (UTC) Received: by bwz2 with SMTP id 2so1334268bwz.43 for ; Sat, 12 Sep 2009 14:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=z+5MjJAG0qJ9YBcjvLSDUv5v38S7WcvveMktZnLzxic=; b=WQwPVcw7v5I+wIMTg4wGfi1KWzIGxS1nhoRfQL9iJVcvr2kQgI/aL82Hs4nVuOgJFo u68ZKfR+kUmVOftTQycU5keMKTJItOVffJVqSaG1Am7zIfp38JtPN9zj/IASnjamMU2g 9Mg7TNwSVVClkLXnh744fxzI3wPsGW55pcDGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=q4yMYyIoE+44vtmNDLhb7t3fxsw3NkpRH0CEORDzbaxFXKAP72h3fQDfyELRauzVC4 Jif6emDYG1vojeKiLMLckcI3X1f376PLXEehvS2uKrh4pBG8quhhs7peYkvTwfMALqAg AvUCFl2gkFrXJsSmGTphjiDUpeee00AMiI1ag= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.54.15 with SMTP id o15mr1711319fag.96.1252791170995; Sat, 12 Sep 2009 14:32:50 -0700 (PDT) In-Reply-To: References: Date: Sat, 12 Sep 2009 23:32:50 +0200 X-Google-Sender-Auth: 56b95be0a9e4b209 Message-ID: <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> From: Attilio Rao To: Dan Naumov Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD-STABLE Mailing List Subject: Re: 7.2-release/amd64: panic, spin lock held too long X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Sep 2009 21:32:52 -0000 2009/7/7 Dan Naumov : > I just got a panic following by a reboot a few seconds after running > "portsnap update", /var/log/messages shows the following: > > Jul 7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel > Jul 7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock > 1) held by 0xffffff00017d8370 (tid 100054) too long > Jul 7 03:49:38 atom kernel: panic: spin lock held too long > > /var/crash looks empty. This is a system running official 7.2-p1 > binaries since I am using freebsd-update to keep up with the patches > (just updated to -p2 after this panic) running with very low load, > mostly serving files to my home network over Samba and running a few > irssi instances in a screen. What do I need to do to catch more > information if/when this happens again? Dan, is that machine equipped with Hyperthreading? Attilio -- Peace can only be achieved by understanding - A. Einstein