Subject: Restore CD 2.0-1 may still have issue for some install *** Feedback
To: None <port-cobalt@netbsd.org>
From: Daniel Ouellet <daniel@presscom.net>
List: port-cobalt
Date: 03/10/2005 02:01:00
Hi all,
I would appreciate feedback on this install if any have actually done so.
Testing more on this, looks like the distribution we have done for the
2.0 may still have an issue with it.
The default kernel have the RAIDframe enable in it by default
See here:
http://netbsd.ouellet.biz/iso/config-20.html
More specifically here:
<snip>
# Disk/mass storage pseudo-devices
#pseudo-device ccd 4 # concatenated disk devices
#pseudo-device cgd 4 # cryptographic disk devices
>>>pseudo-device raid 8 # RAIDframe disk driver
>>>options RAID_AUTOCONFIG # auto-configuration of RAID
# Options to enable various other RAIDframe RAID types.
# options RF_INCLUDE_EVENODD=1
# options RF_INCLUDE_RAID5_RS=1
# options RF_INCLUDE_PARITYLOGGING=1
# options RF_INCLUDE_CHAINDECLUSTER=1
# options RF_INCLUDE_INTERDECLUSTER=1
# options RF_INCLUDE_PARITY_DECLUSTERING=1
# options RF_INCLUDE_PARITY_DECLUSTERING_DS=1
#pseudo-device md 1 # memory disk device (ramdisk)
#pseudo-device vnd 4 # disk-like interface to files
<snip>
But in our distribution of the 1.6.2, we do not have it.
http://netbsd.ouellet.biz/iso/config-162.html
Look here:
<snip>
# Disk/mass storage pseudo-devices
#pseudo-device ccd 4 # concatenated disk devices
#pseudo-device raid 8 # RAIDframe disk driver
#options RAID_AUTOCONFIG # auto-configuration of RAID
# Options to enable various other RAIDframe RAID types.
# options RF_INCLUDE_EVENODD=1
# options RF_INCLUDE_RAID5_RS=1
# options RF_INCLUDE_PARITYLOGGING=1
# options RF_INCLUDE_CHAINDECLUSTER=1
# options RF_INCLUDE_INTERDECLUSTER=1
# options RF_INCLUDE_PARITY_DECLUSTERING=1
# options RF_INCLUDE_PARITY_DECLUSTERING_DS=1
#pseudo-device md 1 # memory disk device (ramdisk)
pseudo-device vnd 4 # disk-like interface to files
<snip>
With the result that for a new install, I get a few times this:
<snip>
>>>>>Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
wd0 at atabus0 drive 0INTRF
panic: siop_intr: I shouldn't be there !
Stopped at 0x801b5808: jr ra
bdslot: nop
ddb>
So, I am looking into this, but I would appreciate some feedback to make
this better.
I really don't think anyone will put RAIDframe on a Cobalt right?
We do love it, but even this box have limits. (:>
Let me know, but look like we will do a trim on the default kernel for
the cobalt to make this reliable on each install.
Daniel