From owner-freebsd-current Sat Mar 8 13:21:12 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3C5937B401 for ; Sat, 8 Mar 2003 13:21:10 -0800 (PST) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 312A243FCB for ; Sat, 8 Mar 2003 13:21:09 -0800 (PST) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (matt@localhost.xtaz.co.uk [127.0.0.1]) by tao.xtaz.co.uk (8.12.8/8.12.8) with ESMTP id h28LL6mG001232 for ; Sat, 8 Mar 2003 21:21:06 GMT (envelope-from matt@xtaz.co.uk) From: "Matt" To: current@freebsd.org Subject: ddb & kernel panic's Date: Sat, 8 Mar 2003 21:21:06 +0000 Message-Id: <20030308211224.M17689@xtaz.co.uk> X-Mailer: Open WebMail 1.90 20030212 X-OriginatingIP: 192.168.1.10 (matt) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I run -CURRENT and have experienced a total lockup of the machine every couple of weeks where it would just freeze with nothing on the console and I would have to power cycle it to get it back. Previously I had all the debug options turned off such as ddb, witness, invarients etc but I thought I would enable them all to see if I could get anything out of it that would be of use to you for the next time it happened. Well it happened again 20 minutes ago but I had DDB_UNATTENDED in the kernel conf and fsck_y_enable="YES" in rc.conf and so I haven't been able to see anything. There is no core dump in /var/crash but this could well be because I only have 256 meg swap and 256 meg physical ram (I keep meaning to add more swap). Anyway my question is, is there anything now I can do or read to see what happened or is it too late now? I assumed DDB_UNATTENDED would still leave some kind of log somewhere of the panic but I can't spot anything. Or if it's too late now should I remove DDB_UNATTENDED and just get backtrace's etc from DDB at the time of crash in the future? Incidently my kernel/world build is from march 4th. Regards, Matt. --- Matt (matt@xtaz.co.uk) http://www.xtaz.co.uk/ --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message