The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: linux-kernel@vger.kernel.org
Subject: Re: IBM Desktar disk problem?
Date: Sat, 6 Jul 2002 00:58:43 +0200	[thread overview]
Message-ID: <20020705225843.GA4061@merlin.emma.line.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0207052243190.3950-100000@moje.ich.vabo.cz>

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]


AGAIN: Please DO NOT CC: ME on mailing lists unless I ask for a Cc:

On Fri, 05 Jul 2002, Tomas Konir wrote:

> On Fri, 5 Jul 2002, Matthias Andree wrote:
> 
> > Are there any strong hints that TCQ caused these?
> 
> only hypothesis, but vith high probability, because there were no problems 
> before using TCQ. My hypothesis is that my IBM disk is oveloaded when 
> using TCQ. (This is only HW problem. No TCQ ).

Well, DTLA break down without giving advance warnings. So TCQ need not
be related to this problem.

> > That's your liberty to choose. :-) (And I can understand the IBM part of
> > it.)
> 
> Yes but is there any other disk which supports TCQ ?

I think all relevant SCSI drives do. Not what you intended, but I'm not
aware of any ATA disks other than IBM DPTA, DTLA, IC35L*AV*.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-07-05 22:56 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 10:27 IBM Desktar disk problem? venom
2002-07-05 10:40 ` Jens Axboe
2002-07-05 10:50   ` Anton Altaparmakov
2002-07-05 12:36     ` Jens Axboe
2002-07-05 13:27   ` venom
2002-07-05 14:15     ` Tomas Konir
2002-07-05 14:26       ` Jens Axboe
2002-07-05 14:48         ` Tomas Konir
2002-07-05 15:38           ` Daniel Egger
2002-07-05 15:42             ` Tomas Konir
2002-07-05 20:11       ` Matthias Andree
2002-07-05 20:21         ` Tomas Konir
2002-07-05 20:39           ` Matthias Andree
2002-07-05 20:50             ` Tomas Konir
2002-07-05 22:58               ` Matthias Andree [this message]
     [not found]         ` <Pine.LNX.4.44L0.0207052216410.3293-100000@moje.ich.vabo.cz >
2002-07-05 21:05           ` Anton Altaparmakov
2002-07-05 21:08             ` Tomas Konir
2002-07-07 12:46               ` Timo Jantunen
2002-07-11 15:14                 ` Thunder from the hill
2002-07-10 16:15               ` Bill Shirley
2002-07-10 17:09                 ` Matthias Andree
2002-07-05 23:00             ` Mohammad A. Haque
2002-07-05 12:50 ` Daniel Egger
2002-07-05 14:03   ` Thunder from the hill
2002-07-05 13:50     ` Zwane Mwaikambo
2002-07-05 15:18     ` Bartlomiej Zolnierkiewicz
2002-07-05 16:58       ` Thunder from the hill
2002-07-05 15:23     ` Daniel Egger
2002-07-05 20:23     ` Matthias Andree
     [not found]   ` <Pine.LNX.4.44.0207050801190.10105-100000@hawkeye.luckynet. adm>
2002-07-05 14:29     ` Anton Altaparmakov
2002-07-05 15:32       ` Daniel Egger
2002-07-05 16:57         ` Thunder from the hill
2002-07-09 13:23         ` Bill Davidsen
2002-07-09 20:35           ` Daniel Egger
  -- strict thread matches above, loose matches on Subject: below --
2002-07-05 15:04 Randal, Phil
2002-07-05 18:01 Voluspa
2002-07-05 18:05 ` Bartlomiej Zolnierkiewicz
2002-07-05 18:19   ` Voluspa
2002-07-11 19:29 Iain Thomas

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=20020705225843.GA4061@merlin.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.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