Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Stuart Brady <sdbrady@ntlworld.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Hanging with kernels >= 2.4.22
Date: Sat, 21 Feb 2004 07:58:49 +0000	[thread overview]
Message-ID: <20040221075849.GA1642@calypso> (raw)
In-Reply-To: <20040219062907.GC13916@colo.lackof.org>

On Wed, Feb 18, 2004 at 11:29:07PM -0700, Grant Grundler wrote:
> On Wed, Feb 18, 2004 at 11:52:25PM +0000, Stuart Brady wrote:
> > I'm having problems with kernels >= 2.4.22 on a 715/100.
> 
> Stuart,
> All your symptoms point at disk IO hanging.
> Setting the default queue depth to 1 would be worth trying.
> I've forgotten the details for setting queue depth.
>  
> search parisc-linux mailing list archives "scsi queue tags".
> http://lists.parisc-linux.org/pipermail/parisc-linux/2004-January/022087.html

Thanks! Changing NCR_700_MAX_TAGS to 1 in drivers/scsi/53c700.h did the
trick. Will I now have poor disk performance? If so, might I get away
with setting it to something higher, like 2 or 4, maybe?

I've not heard of tagged command queues before - the idea seems to be to
transfer data to the drive as early as possible, but make decisions as
to what should be written first at a later stage. Is that correct?

http://lists.parisc-linux.org/pipermail/parisc-linux/2002-February/015465.html
says that no tagged queue is a bad thing. Why is that?

> btw, 715/50 is NOT the same as 715/100.
> 715/100 should have "coherent" DMA and 715/50 does not.
> 
> Maybe a FAQ entry for "715/xxx hangs" could be your first contribution?

That's a good idea. Where should I send the entry? Here?
-- 
Stuart Brady

  reply	other threads:[~2004-02-21  7:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 23:52 [parisc-linux] Hanging with kernels >= 2.4.22 Stuart Brady
2004-02-19  6:29 ` Grant Grundler
2004-02-21  7:58   ` Stuart Brady [this message]
2004-02-21 17:05     ` Carlos O'Donell
2004-02-21 18:24       ` Matthew Wilcox
2004-02-22  6:04         ` Carlos O'Donell
2004-02-22 14:46       ` Riccardo
2004-02-22 15:30         ` Joel Soete
2004-02-22 17:16           ` Riccardo
2004-02-22 17:54             ` Joel Soete
2004-02-22  6:21     ` Grant Grundler

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=20040221075849.GA1642@calypso \
    --to=sdbrady@ntlworld.com \
    --cc=parisc-linux@lists.parisc-linux.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