All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason White <jason@jasonjgw.net>
To: linux-scsi@vger.kernel.org
Subject: SCSI queue warnings under 2.6.31 with LSI SAS1064E controller
Date: Fri, 9 Oct 2009 03:07:16 +0000 (UTC)	[thread overview]
Message-ID: <ham9d4$ihu$1@ger.gmane.org> (raw)

With apologies in advance if this is the wrong mailing list for this, after
upgrading from 2.6.30 to 2.6.31 I get the following warnings in syslog
frequently

Oct  9 12:19:21 jdc kernel: [ 1785.096275] sd 6:1:0:0: strange observation,
the queue depth is (64) meanwhile fw queue depth (65)
Oct  9 12:19:51 jdc kernel: [ 1815.312019] sd 6:1:0:0: Queue depth not changed yet

The Debian bug report is here
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550190

Following a suggestion by Debian developers, I tried patching 2.6.31.3 with
this commit, but with no effect.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9d2e9d66a3f032667934144cd61c396ba49f090d

However, this also shows the problem can be reproduced under 2.6.31.3.

I would prefer to avoid running git bisect on this machine if I can, but I'll
gladly test a patch if it is unlikely to corrupt the file system.

HP XW6400 workstation, two SAS drives configured for striping, x86-64
architecture.

I haven't noticed any file corruption so far - I'm not sure how serious this
problem is.



             reply	other threads:[~2009-10-09  3:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  3:07 Jason White [this message]
2009-10-09 12:04 ` SCSI queue warnings under 2.6.31 with LSI SAS1064E controller Desai, Kashyap
2009-10-09 22:51   ` Jason White

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='ham9d4$ihu$1@ger.gmane.org' \
    --to=jason@jasonjgw.net \
    --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.