>Number:         18419
>Category:       port-i386
>Synopsis:       can't dump to a RAIDframe device
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 25 11:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Chris Jones
>Release:        NetBSD 1.6
>Organization:
chris@mt.sri.com -----------------------------------------------------
Chris Jones                                    SRI International, Inc.
www.mt.sri.com                                             www.sri.com
>Environment:
	
	
System: NetBSD gamera.mt.sri.com 1.6 NetBSD 1.6 (GAMERA) #0: Mon Sep 23 16:47:30 MDT 2002 chris@legolas.mt.sri.com:/usr/src/sys/arch/i386/compile/GAMERA i386
Architecture: i386
Machine: i386

Configuration follows:

total memory = 127 MB
avail memory = 115 MB

pciide0 at pci0 dev 7 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
wd0 at pciide0 channel 0 drive 0: <Maxtor 5T060H6>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 58644 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 120103200 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel wired to compatibility mode
pciide0: disabling secondary channel (no drives)
pciide1 at pci0 dev 14 function 0: Promise Ultra100/ATA Bus Master IDE Accelerator (rev. 0x02)
pciide1: bus-master DMA support present
pciide1: primary channel configured to native-PCI mode
pciide1: using irq 9 for native-PCI interrupt
wd1 at pciide1 channel 0 drive 0: <MAXTOR 6L080J4>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 76345 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 156355584 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
pciide1: secondary channel configured to native-PCI mode
wd2 at pciide1 channel 1 drive 0: <MAXTOR 6L080J4>
wd2: drive supports 16-sector PIO transfers, LBA addressing
wd2: 76345 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 156355584 sectors
wd2: 32-bit data port
wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
wd2(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)

gamera# raidctl -s raid0
Components:
           /dev/wd2e: optimal
           /dev/wd1e: optimal

gamera# cat /etc/fstab
/dev/raid0a / ffs rw,softdep 1 1
/dev/wd1a /altroot ffs rw,softdep 1 2
/dev/wd2a /altroot2 ffs rw,softdep 1 2
/dev/raid0b none swap sw 0 0
/dev/raid0b none swap dp 0 0
/dev/raid0b /tmp mfs rw 0 0
/dev/raid0e /usr ffs rw,softdep 1 2
/dev/raid0h /users ffs rw,softdep 1 2
/dev/raid0g /data ffs rw,softdep 1 3
/dev/raid0f /var ffs rw,softdep 1 4
/dev/wd0e /stage ffs rw,softdep 1 2
/kern /kern kernfs rw 0 0
/dev/fd0a /floppy msdos rw,noauto 0 0

gamera# disklabel raid0
...
#        size    offset     fstype  [fsize bsize cpg/sgs]
 a:    140032         0     4.2BSD   1024  8192    16   # (Cyl.    0 - 546)
 b:   2097152    140032       swap                      # (Cyl.  547 - 8738)
 c: 156055136         0     unused      0     0         # (Cyl.    0 - 609590*)
 d: 156055136         0     unused      0     0         # (Cyl.    0 - 609590*)
 e:   4194304   2237184     4.2BSD   1024  8192    16   # (Cyl. 8739 - 25122)
 f:  41943040   6431488     4.2BSD   1024  8192    16   # (Cyl. 25123 - 188962)
 g:  25165824  48374528     4.2BSD   1024  8192    16   # (Cyl. 188963 - 287266)
 h:  82514784  73540352     4.2BSD   1024  8192    32   # (Cyl. 287267 - 609590*)

>Description:
When the machine tries to write a crash dump to raid0b, it fails.
It says, "dumping to dev x,y offset z", followed by,
"dump device bad".
>How-To-Repeat:
Entering ddb and typing "sync" does the trick.  Actually, it panics the
machine.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted: