linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 74011] New: strange observation, the queue depth is (64) meanwhile fw queue depth (65)
Date: Mon, 14 Apr 2014 08:48:51 +0000	[thread overview]
Message-ID: <bug-74011-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=74011

            Bug ID: 74011
           Summary: strange observation, the queue depth is (64) meanwhile
                    fw queue depth (65)
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 3.2 to 3.14.0
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: rblists@gmail.com
        Regression: No

Created attachment 132121
  --> https://bugzilla.kernel.org/attachment.cgi?id=132121&action=edit
System information

I get this error on the disk containing the root partition
This happens on recent kernels, but not on the 2.6.32.61 kernel.
The code generating these messages is however identical in 2.6.32.61 and newer
kernels.
This doesn't especially happen when the system is under high load.

This happens on both our production and stand-by server. Production server was
switched back to 2.6.32.61.

Attached file contains system information of the stand-by server running kernel
3.14.0 (cpuinfo.txt  lspci.txt  meminfo.txt  proc_scsi_scsi.txt 
ver_linux.txt).

I can provide more info and perform tests if needed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2014-04-14  8:48 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=bug-74011-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).