On Tue, 25 Apr 2000, Peter Seebach wrote:

=> >>>>>>
=> >fatal kernel trap:
=> >
=> >    trap entry = 0x2 (memory management fault)
=> >    a0         = 0x0
=> >    a1         = 0x1
=> >    a2         = 0x0
=> >    pc         = 0xfffffc0000433efc
=> >    ra         = 0xfffffc0000433e48
=> >    curproc    = 0xfffffc0000d3a708
=> >        pid = 4, comm = ioflush
=> 
=> Hmm.  What kind of drive are you using?  Soft updates could change the
=> load patterns on a disk substantially.

Here is the disk-related output when booting:

>>>>>
tcds0 at tc0 slot 4 offset 0x0: TurboChannel Dual SCSI (baseboard)
tcds0: fast mode set for chip 0
asc0 at tcds0 chip 0: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
probe(asc0:0:0): max sync rate 5.00MB/s
sd0 at scsibus0 target 0 lun 0: <IBM OEM, DCHS04Z, 6161> SCSI2 0/direct fixed
sd0: 4340 MB, 6077 cyl, 9 head, 162 sec, 512 bytes/sect x 8888543 sectors
sd1 at scsibus0 target 5 lun 0: <DEC, RX26     (C) DEC, 0070> SCSI1 0/direct removable
sd1: drive offline
<<<<<

The IBM drive never appears to give me any problems otherwise.  (I've
even thrashed it with bonnie at one time.)

Cheers,

Paul.

e-mail: paul@gromit.dlib.vt.edu

"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa