From owner-freebsd-hackers Tue Nov 14 14:26:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6ED5837B4D7; Tue, 14 Nov 2000 14:26:27 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAEMQJB01936; Tue, 14 Nov 2000 14:26:19 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001114151812.F62344@bonsai.knology.net> Date: Tue, 14 Nov 2000 14:26:49 -0800 (PST) From: John Baldwin To: Steve Price Subject: RE: kernel boot question Cc: hackers@FreeBSD.org, alpha@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Nov-00 Steve Price wrote: > This may seem like a strange request but ... I'm trying to rebuild > my Alpha box with the latest 4.2RC bits so I can start and new > package build with the new libc (with version no. bump). The box > is two hours North of here and everyone that is at the office right > now is pretty clueless about computers. I updated everything but > the box is not coming back up. I either have to figure out how to > get it back on its feet remotely or drive 2 hours up there to fix > it myself. I talked one of the people through booting it back up > with kernel.old so I can get back into the box now. > > My question is is there a way to seed the boot process try a new > (test) kernel once and if it panics then go back to using the regular > kernel? So it would go something like this. > > boot kernel.test > panic > boot kernel > tweak and rebuild new kernel > rinse and repeat > > Thanks. Don't compile ddb into your test kernel. :) > BTW, the last part of the dmesg output looks like this and the only > thing I changed in the GENERIC kernel config was 'maxusers 64': > > Mounting root from ufs:/dev/da0a > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > da1 at sym0 bus 0 target 9 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > WARNING: / was not properly dismounted > panic: kmem_malloc(536887296): kmem_map too small: 5685248 total allocated > > syncing disks... 8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 > giving up on 3 buffers > Uptime: 2m4s > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... Looks like your mountd is out of sync with your kernel. > -steve -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message