From: cinap_lenrek@gmx.de
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work
Date: Thu, 7 Feb 2008 00:26:33 +0100 [thread overview]
Message-ID: <f81d65d63b53526d8a04de4cb3da12e5@gmx.de> (raw)
In-Reply-To: <e5314c21c4f54c7c465eb9186a2be430@quanstro.net>
> 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
next prev parent reply other threads:[~2008-02-06 23:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 1:31 [9fans] usb ohci support arrives geoff
2008-02-06 2:16 ` Michael Andronov
2008-02-06 4:01 ` lucio
2008-02-06 12:55 ` [9fans] usb ohci support arrives -- caution Richard Miller
2008-02-06 16:18 ` [9fans] usb ohci support arrives C H Forsyth
2008-02-06 16:23 ` Juan M. Mendez
2008-02-06 17:23 ` [9fans] usb ohci support arrives -- another caution Richard Miller
2008-02-06 17:58 ` Sape Mullender
2008-02-06 19:08 ` Richard Miller
2008-02-06 19:23 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work cinap_lenrek
2008-02-06 20:04 ` erik quanstrom
2008-02-06 22:29 ` cinap_lenrek
2008-02-06 22:40 ` erik quanstrom
2008-02-06 23:26 ` cinap_lenrek [this message]
[not found] <54b639a7eb08c31e4ef2a6d9fd7b6a62@quanstro.net>
2008-02-08 9:35 ` Kernel Panic
2008-02-08 14:55 ` erik quanstrom
2008-02-08 14:56 ` Robert Raschke
2008-02-08 15:27 ` Robert Raschke
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 22:13 cinap_lenrek
2008-02-06 8:41 ` Kernel Panic
2008-02-06 9:45 ` erik quanstrom
2008-02-06 10:43 ` Kernel Panic
2008-02-06 11:03 ` erik quanstrom
2008-02-05 8:18 Kernel Panic
2008-02-05 8:54 ` Lorenzo Fernando Bivens de la Fuente
2008-02-05 13:20 ` erik quanstrom
2008-02-05 19:48 ` Robert Raschke
2008-02-06 2:01 ` arisawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f81d65d63b53526d8a04de4cb3da12e5@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).