Date: Tue, 29 Sep 2009 10:14:19 GMT From: kaN5300 <kan5300@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/139232: Kernel panic (spin lock held too long) Message-ID: <200909291014.n8TAEJOb027660@www.freebsd.org> Resent-Message-ID: <200909291020.n8TAK7wT040054@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 139232 >Category: i386 >Synopsis: Kernel panic (spin lock held too long) >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 29 10:20:07 UTC 2009 >Closed-Date: >Last-Modified: >Originator: kaN5300 >Release: 6.3-STABLE >Organization: MOU IIF RF >Environment: FreeBSD billing 6.3-STABLE FreeBSD 6.3-STABLE #0: Mon Feb 11 17:32:34 MSK 2008 root@utm.serpuhov.biz:/usr/obj/usr/src/sys/UTM-SMP i386 >Description: Hello. We have SMP-enabled billing server (Netup UTM5, MySQL). It was working perfect more then year with big uptime. Иге recently our server started to freeze with such an error: spin lock sleepq chain held by 8xc97e61 for > 5 seconds spin lock held too long (reasonable load) cpuid =3 It repeats in a period of 1 week or so. Now we are turning on kernel debugging mechanisms and preparing to use gdb and so on... We are interested, what is the nature of this panic (HW or SW). >How-To-Repeat: - >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909291014.n8TAEJOb027660>