From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@kernel.org
Subject: [Bug 196543] Adaptec 6405H can not understand Queue full message from Disks.
Date: Wed, 02 Aug 2017 08:14:03 +0000 [thread overview]
Message-ID: <bug-196543-11613-zs5k6S4x3q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196543-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196543
Jack Wang (xjtuwjp@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xjtuwjp@gmail.com
--- Comment #3 from Jack Wang (xjtuwjp@gmail.com) ---
Hi Kazufumi,
Could you send out dmesg with logging_level=0xfff for scsi_host on microsemi
HBA when queue full condition happens?
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2017-08-02 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 2:26 [Bug 196543] New: Adaptec 6405H can not understand Queue full message from Disks bugzilla-daemon
2017-07-31 6:03 ` [Bug 196543] " bugzilla-daemon
2017-08-02 1:35 ` bugzilla-daemon
2017-08-02 8:14 ` bugzilla-daemon [this message]
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-196543-11613-zs5k6S4x3q@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).