Date: Sun, 13 Sep 2009 01:02:36 +0300 From: Dan Naumov <dan.naumov@gmail.com> To: Attilio Rao <attilio@freebsd.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: 7.2-release/amd64: panic, spin lock held too long Message-ID: <cf9b1ee00909121502v66566b46p754ed2f2e549555@mail.gmail.com> In-Reply-To: <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> References: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com> <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 13, 2009 at 12:32 AM, Attilio Rao <attilio@freebsd.org> wrote: > 2009/7/7 Dan Naumov <dan.naumov@gmail.com>: >> I just got a panic following by a reboot a few seconds after running >> "portsnap update", /var/log/messages shows the following: >> >> Jul =A07 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel >> Jul =A07 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock >> 1) held by 0xffffff00017d8370 (tid 100054) too long >> Jul =A07 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 Yes. It's an Intel Atom 330, which is a dualcore CPU with HT (4 cores visible in "top" as a result) - Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf9b1ee00909121502v66566b46p754ed2f2e549555>