All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: linux-rt-users@vger.kernel.org
Subject: megaraid_sas problems on rt
Date: Fri, 10 Aug 2007 10:21:57 -0300	[thread overview]
Message-ID: <20070810132157.GG3375@ghostprotocols.net> (raw)

Hi,

      I've been experiencing problems with the megaraid_sas driver under
some simple stress testing when using the rt patch. Simply running:

cat /dev/sda > /dev/null

will after a while make the driver start sending this to the logs:

sd 0:2:0:0: [sda] megasas: RESET -285224 cmd=28 retries=0
megasas: [ 0]waiting for 2 commands to complete
megasas: [ 5]waiting for 2 commands to complete
megasas: [10]waiting for 2 commands to complete


Till it gets to:

megasas: cannot recover from previous reset failures
sd 0:2:0:0: scsi: Device offlined - not ready after error recovery

And then no more I/O goes thru.

This happens with 2.6.21 + patch-2.6.21.5-rt10 and 2.6.23-rc2 +
patch-2.6.23-rc2-rt2, while not happening without the rt patch.

I looked at driver/scsi/megaraid/megaraid_sas.c and as what its
interrupt handler does is to just ack the int to the firmware and
schedule its tasklet I tried using IRQ_NODELAY and it made the problem
go away, after more than 20 hours of stress testing the system doesn't
exhibits the problem.

Ah, of course in the two machines were I tested, both Dell Poweredge
systems, the IRQ used by the cards was not shared with any other device.

I'm trying some ideas, such as making tasklet_schedule, when run from an
interrupt handler routine to run the tasklet action right away, not
waiting for the tasklet kthread to be scheduled, but the problem only
seems to take more time to happen.

Ideas?

- Arnaldo

                 reply	other threads:[~2007-08-10 13:22 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=20070810132157.GG3375@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=linux-rt-users@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.