From owner-freebsd-stable Tue Oct 15 6:49:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FBCF37B401 for ; Tue, 15 Oct 2002 06:49:30 -0700 (PDT) Received: from mail.cise.ufl.edu (beach.cise.ufl.edu [128.227.205.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76F6343E97 for ; Tue, 15 Oct 2002 06:49:29 -0700 (PDT) (envelope-from jfh@cise.ufl.edu) Received: from cise.ufl.edu (waterspout.cise.ufl.edu [128.227.205.52]) by mail.cise.ufl.edu (Postfix) with ESMTP id 8A7D569AC for ; Tue, 15 Oct 2002 09:49:28 -0400 (EDT) To: stable@freebsd.org Subject: Panic: init dying with 4.7 kernel Date: Tue, 15 Oct 2002 09:49:28 -0400 From: "James F. Hranicky" Message-Id: <20021015134928.8A7D569AC@mail.cise.ufl.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've just upgraded from FreeBSD 4.6-STABLE (CISEKERN) #15: Tue Aug 20 14:37:29 EDT 2002 to FreeBSD 4.7-STABLE #18: Mon Oct 14 14:59:08 EDT 2002 and for some reason, with the 4.7 kernel, init is dying: FreeBSD 4.7-STABLE #18: Mon Oct 14 14:59:08 EDT 2002 root@palm.cise.ufl.edu:/private/freebsd-src/obj/private/freebsd-src/src/sys/CISEKERN [ ... ] BRIDGE 020214 loaded DUMMYNET initialized (011031) ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 19470MB [39560/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 afd0: 96MB [96/64/32] at ata1-slave PIO0 Mounting root from ufs:/dev/ad0s1a init died (signal 6, exit 0) panic: Going nowhere without my init! Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.429 db> trace Debugger(c039bddb) at Debugger+0x34 panic(c039ac40,c039ac20,6,0,2) at panic+0x70 exit1(ce3cce00,6,bfbfffe4,bfbffff2,c03e9daa) at exit1+0x37 execve(ce3cce00,ce3d3f90,bfbfffe4,bfbffff2,bfbfffe8,bfbffffd,bfbfffec,0) at execve+0x7bf start_init(0) at start_init+0x26d fork_trampoline() at fork_trampoline+0x8 Strangely enough, I can still boot with the old 4.6 kernel and the system comes up fine. Here's what a 4.6 boot looks like: BRIDGE 020214 loaded DUMMYNET initialized (011031) IPsec: Initialized Security Association Processing. IP Filter: v3.4.27 initialized. Default = pass all, Logging = enabled ad0: 19470MB [39560/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 afd0: 96MB [96/64/32] at ata1-slave PIO0 Mounting root from ufs:/dev/ad0s1a DEPENDENCY NOTE: portmap will be enabled to support NIS dumpon: crash dumps to /dev/ad0s1b (116, 131073) vinum: loaded vinum: no drives found ** no drives found: No such file or directory swapon: adding /dev/ad0s1b as swap device Automatic boot in progress... /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 1243627 free (17019 frags, 153326 blocks, 0.8% fragmentation) /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 11290267 free (101195 frags, 1398634 blocks, 0.7% fragmentation) /dev/ad0s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 213716 free (10220 frags, 25437 blocks, 1.0% fragmentation) Originally, I had added support for IPFW2 to the kernel and libalias/ipfw, but I've taken that out, and I'm still getting the panic. Is there a good way to trace init's execution so I can find where it's dying? ---------------------------------------------------------------------- | Jim Hranicky, Senior SysAdmin UF/CISE Department | | E314D CSE Building Phone (352) 392-1499 | | jfh@cise.ufl.edu http://www.cise.ufl.edu/~jfh | ---------------------------------------------------------------------- "Given a choice between a complex, difficult-to-understand, disconcerting explanation and a simplistic, comforting one, many prefer simplistic comfort if it's remotely plausible, especially if it involves blaming someone else for their problems." -- Bob Lewis, _Infoworld_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message