> is it possible you are reading or writing outside the bounds of the partition?

no, the errors occured while filling venti and that partitions dont overlap. at
least disk/prep didnt complain as i created them. the offsets are more or
less random.

my dd-testscript was not that successfull in provoking errors.

in the case of the adaptec, i started 2 dd's: one reading from sdC0/data and the
other reading from sdD0/data. the last dd i started killst the first and the 
first
returns i/o error with no delay.

ok... lets leave that out (we dont know if this is really related) and keep on
the via chip.


i'm now testing with IDE (no RAID) mode one with single drive (sdC0).
just tried to create some disk load so i created venti arenas and isects
and started:

vac -h 127.1 /sys &
while(){ dd -if /dev/sdC0/data -of /dev/null -bs 65536 }

it paniced and here is the dump from serial console:

user[none]: glenda

time...

fossil(#S/sdC0/fossil)...version...time...



init: starting /bin/rc

command C8
data f193ca70 limit f193e870 dlen 65536 status 0 error 0
lba 10033153 -> 10033153, count 128 -> 128 (15)
 0x00 0x00 0x0F 0x18 0x99 0xE0 0x50
bmicx 09 bmisx 21 prdt f15a90d4
pa 0x0193CA70 count 00001590
pa 0x0193E000 count 80000870
atagenioretry: disabling dma
sdC0: retry: dma 00000000 rwm 0000
command 20
data f193d270 limit f193e870 dlen 65536 status 0 error 0
lba 10033153 -> 10033153, count 128 -> 128 (15)
 0x00 0x0A 0x06 0x18 0x99 0xE0 0x58
fossil: diskReadRaw failed: /dev/sdC0/fossil: score 0x0000664c: part=data block 
26188: i/o error
fossil: diskWriteRaw failed: /dev/sdC0/fossil: score 0x00006600: date Thu Feb  
7 07:17:41 EST 2008
 part=data block 26112: i/o error
fossil: diskWriteRaw failed: /decpu0: registers for stats 106

FLAGS=10093 TRAP=E ECODE=2 PC=F010036A SS=FF00 USP=F0158040

  AX FFFF8C10  BX F004A400  CX F8C9F438  DX 0000FF00

  SI 00000058  DI 00000000  BP FFFF1820

  CS 0010  DS 0008  ES 0008  FS 001B  GS 001B

  CR0 80010031 CR2 00000000 CR3 11ce5000 CR4 000000d0

  MCA 00000000 MCT 00000000

  ur f18215b0 up f03e29b0

panic: fault: 0x0




> - erik

Reply via email to