From owner-freebsd-current@FreeBSD.ORG Thu Apr 29 09:58:21 2004 Return-Path: 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 3792C16A4CE for ; Thu, 29 Apr 2004 09:58:21 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A18943D31 for ; Thu, 29 Apr 2004 09:58:21 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 192DE72DF0; Thu, 29 Apr 2004 09:58:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1635A72DBF; Thu, 29 Apr 2004 09:58:21 -0700 (PDT) Date: Thu, 29 Apr 2004 09:58:21 -0700 (PDT) From: Doug White To: Donn Miller In-Reply-To: <408F5C1B.3000003@cvzoom.net> Message-ID: <20040429095632.I56562@carver.gumbysoft.com> References: <408F5C1B.3000003@cvzoom.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Panic on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 16:58:21 -0000 On Wed, 28 Apr 2004, Donn Miller wrote: > I've been getting similar panics for the past 2 weeks or so on my HP > Pavilion laptop (N5440, 850 MHz Pentium III). Sometimes when I attempt > to boot, like 1 out of 20 times, it doesn't panic for some reason. But > I do get the same results with every panic, so I know it's not a > hardware problem. These occur after "vga0" is probed. It's an S3 > Savage chipset. [...] > stopped at module_lookupbyname+0x24: movl 0x1c(%ebx), %eax > module_lookupbyname(c06d27e1,0,0,c2bbf300,c06efb78) at > module_lookupbyname+0x24 > module_register_init(c0726a8,c1ec00,c1e000,c1ec00,c1e000) at > module_register_init+0x32 > mi_startup() at mi_startup+0xb5 > begin() at begin+0x2c Looks like you might have a bogus or corrupted module. Can you try booting single-user and disabling any _load directives in boot.conf? If you can get the system up otherwise, try rebuilding and reinstalling your kernel. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org