From owner-freebsd-stable@FreeBSD.ORG Sun Aug 14 23:45:02 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 16BB4106564A; Sun, 14 Aug 2011 23:45:02 +0000 (UTC) (envelope-from prvs=120731b379=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 666118FC1C; Sun, 14 Aug 2011 23:45:00 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Mon, 15 Aug 2011 00:44:00 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Mon, 15 Aug 2011 00:44:00 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50014600121.msg; Mon, 15 Aug 2011 00:43:59 +0100 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=120731b379=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: "Attilio Rao" , "Jeremy Chadwick" References: <47F0D04ADF034695BC8B0AC166553371@multiplay.co.uk><4E4380C0.7070908@FreeBSD.org><44DD20E1CFA949E8A1B15B3847769DCB@multiplay.co.uk><20110811092858.GA94514@icarus.home.lan> Date: Mon, 15 Aug 2011 00:44:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 Cc: freebsd-stable@freebsd.org, Andriy Gapon 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: Sun, 14 Aug 2011 23:45:02 -0000 ----- Original Message ----- From: "Attilio Rao" > Anyway, we really would need much more information in order to take a > proactive action. > Would it be possible to access to one of the panic'ing machine? Is it > always the same panic which is happening or it is variadic (like: once > page fault, once fatal double fault, once fatal trap, etc.). They are always double fault, 99% of the time with no additional info we've seen 1 mention of java on one of the machines but the vmcore didn't seem to mention anything to do with that after dump. My colleague informs me when he did the upgrade to add in schedule stop patch, pretty much every machine paniced when shutting the java servers down, which is essentially a jail stop. I've also had two panics when rebooting my test machine to change kernel settings, although this could be a side effect of the scheduler patch? This single test machine is now running with the following none standard settings:- options INVARIANTS options INVARIANT_SUPPORT options DDB options KSTACK_PAGES=12 I've got several vmcores from a number or different machines but none seem to be any use, as they don't seem to list any thread that caused the panic i.e. no mention of dump, or fault. Is there something else in particular I should be looking for? Circumstantial evidence seems to indicate uptime may to be a factor, machines under 2 days seem much less likely to panic. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.