From owner-freebsd-stable@FreeBSD.ORG Wed Jul 16 19:39:01 2008 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 7F5E7106566B; Wed, 16 Jul 2008 19:39:01 +0000 (UTC) (envelope-from john@basicnets.co.uk) Received: from server252.basicnets.co.uk (server8.basicnets.co.uk [81.6.221.8]) by mx1.freebsd.org (Postfix) with ESMTP id 183908FC1D; Wed, 16 Jul 2008 19:39:01 +0000 (UTC) (envelope-from john@basicnets.co.uk) Received: from www by server252.basicnets.co.uk with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KJCq4-000EIv-AH; Wed, 16 Jul 2008 20:39:00 +0100 Received: from 192.168.137.67 ([192.168.137.67]) by mail.basicnets.co.uk (Horde MIME library) with HTTP; Wed, 16 Jul 2008 20:39:00 +0100 Message-ID: <20080716203900.5jt4qce17gg0og0o@mail.basicnets.co.uk> X-Priority: 3 (Normal) Date: Wed, 16 Jul 2008 20:39:00 +0100 From: john@basicnets.co.uk To: Kris Kennaway References: <854CADB9D95147CAB10BC35887A8E5DC@emea.hubersuhner.net> <20080716031640.7DC744500E@ptavv.es.net> <62b856460807160743v3fce951eg1b2bd9e50a35ba1d@mail.gmail.com> <487E0D1B.2060902@FreeBSD.org> In-Reply-To: <487E0D1B.2060902@FreeBSD.org> MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) / FreeBSD-6.2 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Description: Plaintext Version of Message X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load 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: Wed, 16 Jul 2008 19:39:01 -0000 > OK, the first thing to do is disable bg fsck, then force a full fsck of > all filesystems.=A0 bg fsck does a poor job of fixing arbitrary > filesystem corruption (it's not designed to do so, in fact), and you > can get into a situation where corrupted filesystems cause further > panics. Done, nothing really found wrong size in superblock which it corrected. > Removing KDB_UNATTENDED from your kernel will allow you to interact > with the debugger and obtain backtraces etc, which is useful when dumps > are not being saved. Easier said than done, this cause a few panics - no dumps though ...grrrr= !! Still the same result ... the system seems to panic twice then =20 hang.=A0 I will keep trying unless you have some other ideas?? Thanks for your support John ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.