Date: Tue, 7 Jul 2009 04:12:14 +0300 From: Dan Naumov <dan.naumov@gmail.com> To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: 7.2-release/amd64: panic, spin lock held too long Message-ID: <cf9b1ee00907061812r3da70018i1c8d8d12bb038a80@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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? - Sincerely, Dan Naumov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cf9b1ee00907061812r3da70018i1c8d8d12bb038a80>