From owner-freebsd-questions Mon Jul 24 7:14: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sibptus.tomsk.ru (sibptus.tomsk.ru [212.111.92.16]) by hub.freebsd.org (Postfix) with ESMTP id B45A937B9A7 for ; Mon, 24 Jul 2000 07:14:04 -0700 (PDT) (envelope-from sudakov@sibptus.tomsk.ru) Received: (from sudakov@localhost) by sibptus.tomsk.ru (8.9.3/8.9.3) id WAA17166 for questions@freebsd.org; Mon, 24 Jul 2000 22:14:02 +0800 (KRAST) (envelope-from sudakov) Date: Mon, 24 Jul 2000 22:14:02 +0800 From: Victor Sudakov To: questions@freebsd.org Subject: getting out of ddb(4) Message-ID: <20000724221402.A17077@sibptus.tomsk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Organization: AO "Svyaztransneft", SibPTUS Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. After a crash the box got into the kernel debugger. All my attempts to leave the debugger and continue operation were in vain. What I did: 1. Tried 'continue'. It just prints the trap message once again. 2. Tried 'panic'. It says 'Panic from debugger, Uptime 0s' and hangs. No disk activity, no more messages. I waited about 5 minutes. 3. Cold restart. After a cold restart the kernel would drop into ddb again and again. There was no way to boot the box. The only way out for me was to mount the fixit floopy and 'mv kernel.old kernel'. Only after that I was able to boot. BTW I found out that chflags was not on the floppy, but it is another story. Is this behaviour of ddb correct? How do I get out of it next time? And why did cold restart not help? Thanks for any input. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/149@fidonet http://vas.tomsk.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message