From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: Jens Axboe <axboe@suse.de>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, andre@linux-ide.org,
linux-kernel@vger.kernel.org
Subject: Re: HighPoint 374
Date: Mon, 20 Oct 2003 10:10:56 +0200 (MEST) [thread overview]
Message-ID: <6286.1066637456@www51.gmx.net> (raw)
In-Reply-To: <20031020064831.GT1128@suse.de>
> On Sun, Oct 19 2003, Bartlomiej Zolnierkiewicz wrote:
> >
> > Andre, thanks for helpful hint.
> > Svetoslav, the right person to whine about TCQ stuff is Jens Axboe 8-).
>
> Well that's correct, but this looks more like an AS iosched bug :)
> > > You do not enable TCQ on highpoint without using the hosted polling
> timer.
> > > Oh and I have not added it, and so hit Bartlomiej up for the
> additions.
>
> For what? TCQ tests fine on a HPT370 here.
cmdline : acpi=off pci=noacpi elevator=deadline
hdparm -d1 -X69 -Q32 /dev/hd[a,e,g]
---------------------------------------------------------------------
blk: queue f7dd2e00, I/O limit 4095Mb (mask 0xffffffff)
hda: tagged command queueing enabled, command queue depth 32
blk: queue f7dd2400, I/O limit 4095Mb (mask 0xffffffff)
ide_dmaq_intr: stat=40, not expected
ide_dmaq_intr: stat=40, not expected
hde: tagged command queueing enabled, command queue depth 32
ide_dmaq_intr: stat=40, not expected
hdg: set_drive_speed_status: status=0x58 { DriveReady SeekComplete
DataRequest }
blk: queue f7dcce00, I/O limit 4095Mb (mask 0xffffffff)
hdg: dma_timer_expiry: dma status == 0x20
hdg: DMA timeout retry
hdg: timeout waiting for DMA
hdg: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdg: drive not ready for command
hdg: tagged command queueing enabled, command queue depth 32
ide_dmaq_intr: hdg: error status ff
hdg: ide_dmaq_complete: status=0xff { Busy }
hdg: invalidating tag queue (1 commands)
hdg: ide_intr: huh? expected NULL handler on exit
hdg: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdg: drive_cmd: error=0x04 { DriveStatusError }
hdg: set_drive_speed_status: status=0xff { Busy }
ide_tcq_intr_timeout: timeout waiting for completion interrupt
hdg: invalidating tag queue (0 commands)
hdg: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdg: drive not ready for command
hdg: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdg: drive not ready for command
hdg: CHECK for good STATUS
ide_dmaq_intr: hde: error status ff
hde: ide_dmaq_complete: status=0xff { Busy }
hde: invalidating tag queue (1 commands)
hde: ide_intr: huh? expected NULL handler on exit
hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hde: drive_cmd: error=0x04 { DriveStatusError
}
--------------------------------------------------------------------------------------
hdparm -m16 -d1 -X69 -Q32
/dev/hd[a,e,g]
--------------------------------------------------------------------------------------
blk: queue f7dd2e00, I/O limit 4095Mb (mask 0xffffffff)
blk: queue f7dd2400, I/O limit 4095Mb (mask 0xffffffff)
hde: tagged command queueing enabled, command queue depth 32
blk: queue f7dcce00, I/O limit 4095Mb (mask 0xffffffff)
hdg: tagged command queueing enabled, command queue depth 32
ide_dmaq_intr: hdg: error status ff
hdg: ide_dmaq_complete: status=0xff { Busy }
hdg: invalidating tag queue (1 commands)
hdg: ide_intr: huh? expected NULL handler on exit
hdg: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdg: drive_cmd: error=0x04 { DriveStatusError
}
--------------------------------------------------------------------------------------
hdparm -m0 -d1 -X69 -Q32
/dev/hd[a,e,g]
--------------------------------------------------------------------------------------
blk: queue f7dd2e00, I/O limit 4095Mb (mask 0xffffffff)
blk: queue f7dd2400, I/O limit 4095Mb (mask 0xffffffff)
blk: queue f7dcce00, I/O limit 4095Mb (mask 0xffffffff)
hdg: tagged command queueing enabled, command queue depth 32
ide_dmaq_intr: hdg: error status ff
hdg: ide_dmaq_complete: status=0xff { Busy }
hdg: invalidating tag queue (1 commands)
hdg: ide_intr: huh? expected NULL handler on exit
hdg: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdg: drive_cmd: error=0x04 { DriveStatusError
}
-------------------------------------------------------------------------------------
upto now no transfer to the drives, except to the root partition(system
activity) which is on hdg
dd if=/dev/zero of=/mnt/tmp/1/10Gb.zeros bs=512k count=20000
[/dev/hde]
------------------------------------------------------------------------------
ide_dmaq_intr: hde: error status ff
hde: ide_dmaq_complete: status=0xff { Busy }
hde: invalidating tag queue (1 commands)
hde: ide_intr: huh? expected NULL handler on exit
hde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hde: drive_cmd: error=0x04 { DriveStatusError }
and a bit later
ide_dmaq_intr: hda: error status ff
hda: ide_dmaq_complete: status=0xff { Busy }
hda: invalidating tag queue (1 commands)
hda: ide_intr: huh? expected NULL handler on exit
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
only /boot ~ 90Mb was mounted on hda and i don't think the system accessed
it
on second thoght i also have a swap partition on it,
but i have currently 1.9Mb swap used
svetljo
--
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService
Jetzt kostenlos anmelden unter http://www.gmx.net
+++ GMX - die erste Adresse für Mail, Message, More! +++
next prev parent reply other threads:[~2003-10-20 8:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 19:57 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 [this message]
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
-- 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=6286.1066637456@www51.gmx.net \
--to=svetljo@gmx.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome