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: <IBM DDRS-39130D DC1B> 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: <IBM DDRS-39130D DC1B> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
