From owner-freebsd-current Sat Jul 27 13:58:33 2002 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 75A5137B400 for ; Sat, 27 Jul 2002 13:58:31 -0700 (PDT) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id C53B143E3B for ; Sat, 27 Jul 2002 13:58:30 -0700 (PDT) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id C5EB25E92C; Sat, 27 Jul 2002 14:04:36 -0700 (PDT) Date: Sat, 27 Jul 2002 14:04:36 -0700 From: Arun Sharma To: current@freebsd.org Subject: panic with -current Message-ID: <20020727210436.GA18213@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i 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 This is with the GENERIC kernel. Known problem ? How can I get a -current kernel that boots to multiuser so that I can tinker around with it ? Are there any magic config files that suppress these panics ? db> trace _mtx_lock_flags(7069307e,0,c03ff2e0,530) at _mtx_lock_flags+0x3e securelevel_ge(bfbffe00,3,c0291194,c04b0e60,c04b0ca8) at securelevel_ge+0x3c ip_fw_ctl(cad2fcc0,c026213c,0,c2075410,cad2fcac) at ip_fw_ctl+0x30 rip_ctloutput(c2075410,cad2fcc0,cad2fd14,c0d6c540,cad2fcec) at rip_ctloutput+0xe sosetopt(c2075410,cad2fcc0,c2075410,1,0) at sosetopt+0x2c setsockopt(c0d6c540,cad2fd14,5,0,213) at setsockopt+0x8e syscall(2f,2f,2f,8093879,bfbffe73) at syscall+0x233 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message