From owner-freebsd-stable@FreeBSD.ORG Thu Aug 11 14:08:56 2011 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 F227C106566C for ; Thu, 11 Aug 2011 14:08:55 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 48AE28FC19 for ; Thu, 11 Aug 2011 14:08:55 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA15604; Thu, 11 Aug 2011 17:08:51 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E43E272.1060204@FreeBSD.org> Date: Thu, 11 Aug 2011 17:08:50 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Steven Hartland References: <47F0D04ADF034695BC8B0AC166553371@multiplay.co.uk> <4E4380C0.7070908@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: debugging frequent kernel panics on 8.2-RELEASE 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: Thu, 11 Aug 2011 14:08:56 -0000 on 11/08/2011 14:39 Steven Hartland said the following: > The trimmed down output, removed the 10,000's of ?? lines here:- > http://blog.multiplay.co.uk/dropzone/freebsd/panic-2011-08-11-1402.txt > > The raw output is here:- > http://blog.multiplay.co.uk/dropzone/freebsd/panic-full-2011-08-11-1402.txt.bz2 > > I'm not sure how useful its going to be as pretty much all of it seems > to be just:- > #0 sched_tswitch (td=0xffffff00194d4460, newtd=0xffffff000a74a000, flags=Variable > "flags" is not available. > #1 0xffffffff80385c86 in mi_switch (flags=260, newtd=0x0) at > /usr/src/sys/kern/kern_synch.c:449 > #2 0xffffffff803b8a0c in sleepq_catch_signals (wchan=0xffffff02f27c48c0, pri=92) > at /usr/src/sys/kern/subr_sleepqueue.c:418 > #3 0xffffffff803b9326 in sleepq_wait_sig (wchan=Variable "wchan" is not available. > #4 0xffffffff80386149 in _sleep (ident=0xffffff02f27c48c0, > lock=0xffffff02f27c49b8, priority=Variable "priority" is not available. > #5 0xffffffff8035079d in kern_wait (td=0xffffff00194d4460, pid=91362, > status=0xffffff86cdbffabc, options=Variable "options" is not available. > #6 0xffffffff80350e95 in wait4 (td=Variable "td" is not available. > #7 0xffffffff803bb8e5 in syscallenter (td=0xffffff00194d4460, > sa=0xffffff86cdbffba0) at /usr/src/sys/kern/subr_trap.c:315 > #8 0xffffffff80574a0b in syscall (frame=0xffffff86cdbffc40) at > /usr/src/sys/amd64/amd64/trap.c:888 > #9 0xffffffff8055d242 in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:377 > > On one machine we had a little more info on console which may indicate > java as the problem. > > http://blog.multiplay.co.uk/dropzone/freebsd/panic-java.jpg I would really appreciate if you could try to reproduce the problem with the patch that I sent earlier. -- Andriy Gapon