All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.13-ac7
Date: Sun, 04 Nov 2001 20:58:16 -0500	[thread overview]
Message-ID: <3BE5F238.6121972C@torque.net> (raw)

Alan,
I getting repeatable lockups on my SMP box (dual Celeron
Abit hack) after sg does direct IO in this new version.

This sequence using sg_rbuf from my sg3_utils package
(www.torque.net/sg) locks at the end of the transfer
just before returning:
   $ echo 1 > /proc/scsi/sg/allow_dio
   $ sg_rbuf -d -b=512 /dev/sg0
# /dev/sg0 is a fast disk.
# this executes multiple READ BUFFER commands each 512 KB

The box is still usable but the "sg_rbuf" process is
unkillable and ps locks just before it would have 
listed the damaged process. Alt-SysRq-T shows that
the sg_rbuf task in "D" state. The stack backtrace is:
  write_chan
  rwsem_down_write_failed
  ????
  ret_from_fork

This is with sg version 3.2.21 utilising alloc_kiovec_sz()
and friend. I didn't see this "feature" when I tested it
against ac4 before submitting it to you. Changing the "nbhs"
value from 0 to 256 doesn't make any difference. I have
just retested with ac4+sg3.1.21 and it works.

When normal double buffering is used (i.e. no "-d" switch
to the above sg_rbuf) there is no lockup.

Doug Gilbert

             reply	other threads:[~2001-11-05  1:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05  1:58 Douglas Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-04  0:25 Linux 2.4.13-ac7 Thomas Hood
2001-11-03 18:52 Alan Cox
2001-11-04 16:59 ` Marcus Meissner
2001-11-04 17:35   ` Greg KH

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=3BE5F238.6121972C@torque.net \
    --to=dougg@torque.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 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.