From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 21:51:14 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 E1F4616A4CE for ; Thu, 8 Jan 2004 21:51:14 -0800 (PST) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.208.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DFC743D5A for ; Thu, 8 Jan 2004 21:51:13 -0800 (PST) (envelope-from lambert@lambertfam.org) Received: by mail.lambertfam.org (Postfix, from userid 999) id 0E85E34D50; Fri, 9 Jan 2004 00:51:13 -0500 (EST) Date: Fri, 9 Jan 2004 00:51:12 -0500 From: Scott Lambert To: current@freebsd.org Message-ID: <20040109055112.GB22533@www.lambertfam.org> Mail-Followup-To: current@freebsd.org References: <200312220101.hBM11WgL071526@repoman.freebsd.org> <3FFCA854.7040707@isi.edu> <3FFD9C96.7070802@vbservices.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FFD9C96.7070802@vbservices.net> User-Agent: Mutt/1.5.5.1i Subject: Re: Immediate reboot after memory probe 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: Fri, 09 Jan 2004 05:51:15 -0000 On Thu, Jan 08, 2004 at 01:08:22PM -0500, mjoyner wrote: > Also seen here on a AMD Athlon. > Work Around: Load Modules AFTER kernel boots. > > Yu-Shun Wang wrote: > >Hi, > > > >Updated a couple of machines after the holiday and they blowed > >up on me. :-) As said in the subject, after installing the new > >kernel based on today's current, the machines (Dell duo Xeon > >2.4GHz with 1G RDRAM) would not boot, or more precisely they'd > >immediately reboot after preloading the modules and showing > >the CPU/Mem specs: > > Sound modules? I've been setting up my new Compaq Presario 2195US and decided to load all the sound modules to see if any of them worked as well as the if_ndis module. It dropped to gdb very early in the boot but did not respond to the keyboard. I unloaded the snd modules on the next boot and it came up fine. (if_ndis is cool! I'm currently connected through my Broadcom WiFi part using "Project Evil". The coolest thing is how dead simple it was to get it working. ) -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org