From: "Tomi Orava" <Tomi.Orava@ncircle.nullnet.fi>
To: "Bartlomiej Zolnierkiewicz" <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: "Svetoslav Slavtchev" <svetljo@gmx.de>,
"Carlos Fernandez Sanz" <cfs-lk@nisupu.com>,
linux-kernel@vger.kernel.org
Subject: Re: HighPoint 374
Date: Tue, 21 Oct 2003 21:50:32 +0300 (EEST) [thread overview]
Message-ID: <35640.192.168.9.10.1066762232.squirrel@ncircle.nullnet.fi> (raw)
In-Reply-To: <200310202325.05384.bzolnier@elka.pw.edu.pl>
Ups, hit enter while still writing the message, sorry about that.
Anyway, I just wanted to know if the following error messages
tell you anything new.
The test was done by copying almost 40GB data simultaneously
from one RAID1-mirror (disks 1&2 on hpt374) to disks 3&4 on
hpt374 as well _and_ to disks 1&2 on an external Sil680 PCI-card.
Kernel version was 2.4.23-pre7.
In my tests the hdparm -m doesn't solve anything.
The hardware was Epox 8K9A3+ with integrated hpt374-chip.
Processor is AMD 1.4TB, no overclocking of any kind.
Regards,
Tomi Orava
---------------------------------------------------------------
Oct 21 20:15:05 alderan kernel: hdk: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Oct 21 20:15:05 alderan kernel: hdk: drive_cmd: error=0x04 {
DriveStatusError }
Oct 21 20:15:05 alderan kernel: hdk: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Oct 21 20:15:05 alderan kernel: hdk: drive_cmd: error=0x04 {
DriveStatusError }
Oct 21 20:15:17 alderan kernel: hdk: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Oct 21 20:15:17 alderan kernel: hdk: drive_cmd: error=0x04 {
DriveStatusError }
Oct 21 20:22:36 alderan kernel: hdg: set_drive_speed_status: status=0xff {
Busy }
Oct 21 20:30:57 alderan kernel: hdi: dma_timer_expiry: dma status == 0x20
Oct 21 20:30:57 alderan kernel: hdi: timeout waiting for DMA
Oct 21 20:30:57 alderan kernel: hdi: timeout waiting for DMA
Oct 21 20:30:57 alderan kernel: hdi: (__ide_dma_test_irq) called while not
waiting
Oct 21 20:30:57 alderan kernel: hdi: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct 21 20:30:57 alderan kernel:
Oct 21 20:30:57 alderan kernel: hdi: drive not ready for command
Oct 21 20:30:57 alderan kernel: hdi: status timeout: status=0xd0 { Busy }
Oct 21 20:30:57 alderan kernel:
Oct 21 20:30:57 alderan kernel: hdi: drive not ready for command
Oct 21 20:30:57 alderan kernel: ide4: reset: success
Oct 21 20:30:57 alderan kernel: blk: queue c0498a50, I/O limit 4095Mb
(mask 0xffffffff)
Oct 21 20:30:57 alderan kernel: hdi: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct 21 20:31:01 alderan kernel:
Oct 21 20:31:10 alderan kernel: hdi: drive not ready for command
Oct 21 20:31:17 alderan kernel: hdi: dma_timer_expiry: dma status == 0x20
Oct 21 20:31:20 alderan kernel: hdi: timeout waiting for DMA
Oct 21 20:31:20 alderan kernel: hdi: timeout waiting for DMA
Oct 21 20:31:20 alderan kernel: hdi: (__ide_dma_test_irq) called while not
waiting
Oct 21 20:31:20 alderan kernel: hdi: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct 21 20:31:20 alderan kernel:
Oct 21 20:31:20 alderan kernel: hdi: drive not ready for command
Oct 21 20:31:20 alderan kernel: hdi: status timeout: status=0xd0 { Busy }
Oct 21 20:31:20 alderan kernel:
Oct 21 20:31:20 alderan kernel: hdi: drive not ready for command
Oct 21 20:31:20 alderan kernel: ide4: reset: success
Oct 21 20:32:36 alderan kernel: hdi: lost interrupt
--
Tomi.Orava@ncircle.nullnet.fi
next prev parent reply other threads:[~2003-10-21 18:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 19:57 HighPoint 374 Svetoslav Slavtchev
2003-10-19 20:30 ` Andre Hedrick
2003-10-19 20:46 ` Svetoslav Slavtchev
2003-10-19 20:51 ` Bartlomiej Zolnierkiewicz
2003-10-19 20:54 ` Svetoslav Slavtchev
2003-10-20 6:48 ` Jens Axboe
2003-10-20 7:43 ` Tomi Orava
2003-10-20 8:10 ` Svetoslav Slavtchev
2003-10-20 8:21 ` Nick Piggin
2003-10-20 8:30 ` Svetoslav Slavtchev
2003-10-19 21:51 ` Tomi Orava
2003-10-19 22:00 ` Svetoslav Slavtchev
2003-10-19 22:11 ` Svetoslav Slavtchev
2003-10-19 22:24 ` Tomi Orava
2003-10-20 7:53 ` Svetoslav Slavtchev
2003-10-20 8:03 ` Tomi Orava
2003-10-20 9:03 ` Svetoslav Slavtchev
2003-10-20 17:02 ` Carlos Fernandez Sanz
2003-10-20 19:14 ` Svetoslav Slavtchev
2003-10-20 20:23 ` Carlos Fernandez Sanz
2003-10-20 21:07 ` Svetoslav Slavtchev
2003-10-20 21:25 ` Bartlomiej Zolnierkiewicz
2003-10-20 21:25 ` Svetoslav Slavtchev
2003-10-21 18:43 ` Tomi Orava
2003-10-21 18:50 ` Tomi Orava [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 9:23 Jindrich Makovicka
2003-10-21 16:59 ` Tomi Orava
2003-10-19 19:42 Christian Guggenberger
2003-10-19 19:54 ` Tomi Orava
2003-10-18 9:44 Carlos Fernandez Sanz
2003-10-18 10:15 ` Måns Rullgård
2003-10-19 12:13 ` Tomi Orava
2003-10-19 16:48 ` Carlos Fernandez Sanz
2003-10-19 17:16 ` Tomi Orava
2003-10-19 17:39 ` Carlos Fernandez Sanz
2003-10-19 19:27 ` Tomi Orava
2003-10-19 19:35 ` Carlos Fernandez Sanz
2003-10-19 15:59 ` Joel Smith
2003-10-19 17:24 ` Tomi Orava
2003-10-19 17:42 ` Måns Rullgård
2003-10-19 19:14 ` Tomi Orava
2003-10-19 19:27 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Tomi Orava
2003-10-19 20:12 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Måns Rullgård
2003-10-19 19:54 ` David B. Stevens
2003-10-20 8:38 ` Geller Sandor
2003-10-19 21:12 ` Joel Smith
2003-10-19 17:28 ` Carlos Fernandez Sanz
2003-10-19 21:35 ` Joel Smith
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=35640.192.168.9.10.1066762232.squirrel@ncircle.nullnet.fi \
--to=tomi.orava@ncircle.nullnet.fi \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=cfs-lk@nisupu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=svetljo@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.