public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alvaro Figueroa <fede2@fuerzag.ulatina.ac.cr>
To: LKML <linux-kernel@vger.kernel.org>
Subject: "Disk Sleep" status on qlogic scsi sbus card on a sparc station 20 (sparc32, 2.4.17)
Date: 03 Apr 2002 20:57:24 -0600	[thread overview]
Message-ID: <1017889044.221.10.camel@lucy> (raw)

I know sparc32 is not mantained any more, but I'm still posting in case
this problem with give light to a problem that might apear on another
arquitecture.

I'm running kernel 2.4.17 on a sparc station 20 (with 2 procesors)
running splack -current.

I have a scsi qlogic sbus card on this box on with I attatch an scsi
tape or a multipack storage with some 8 to 12 disks on it.

While I run diferent aplications (not at a time) that are some I/O
intensive on the devices attatched to this qlogic card and I sometimes
see some huge sleeps on the process that is working on them.

I cat'ed /proc/{PID}/status and I see "State:  D (disk sleep)".

Sometimes the process goes on working, but not often. I also can't send
this process to sleep nor I can kill them.

I have used tar to back up an filesystem to a DD3 tape, and have also
used rsync from another host (On a 100Mb LAN) to a raid formed by the
disks that are attatched to the controller.

BTW, this does *NOT* occur on an ultra1 box (which is sparc64) running
the same kernel version, and with the same set of disk or the same tape
with the same qlogic scsi sbus card.

What test could I run on this box to give some more information to you
guys that would help to resolve this problem?

Or else, what could be that problem, and what could I do to solve it?

Thanks in advance.

-- 
Alvaro Figueroa


                 reply	other threads:[~2002-04-04  3:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1017889044.221.10.camel@lucy \
    --to=fede2@fuerzag.ulatina.ac.cr \
    --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