From owner-freebsd-alpha Tue Nov 14 13:18:21 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3325437B4C5; Tue, 14 Nov 2000 13:18:16 -0800 (PST) Received: from bonsai.knology.net (user-24-214-88-8.knology.net [24.214.88.8]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id eAELID701563; Tue, 14 Nov 2000 15:18:14 -0600 (CST) Received: (from steve@localhost) by bonsai.knology.net (8.11.0/8.9.3) id eAELID665537; Tue, 14 Nov 2000 15:18:13 -0600 (CST) (envelope-from steve) Date: Tue, 14 Nov 2000 15:18:12 -0600 From: Steve Price To: alpha@freebsd.org Cc: hackers@freebsd.org Subject: kernel boot question Message-ID: <20001114151812.F62344@bonsai.knology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. 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... -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message