From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: "Oliver M. Bolzer" <oliver@fakeroot.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: qla2xxx: frequent total lockups (2.6.8, 2.6.9-rc{1-mm5,2})
Date: Thu, 16 Sep 2004 09:30:29 -0700 [thread overview]
Message-ID: <20040916163029.GA14441@praka.san.rr.com> (raw)
In-Reply-To: <20040915231657.GA2005@magi.fakeroot.net>
On Thu, 16 Sep 2004, Oliver M. Bolzer wrote:
> I'm currently setting up a new Dual Opteron box (Tyan Transport
> GX28) equipped with a QLogic QLA2340 fibre channel HBA.
>
> As soon as there is I/O load on the HBA, I start seeing
>
Could you provide some details on the type of I/O load?
> I've tested and reproduced the error on the following kernels, all
> compiled for x86_64.
> 2.6.8.1
> 2.6.9-rc1-mm5 (with dma_fixups patch posted by Andrew Vasquez on 13.9)
> 2.6.9-rc2
>
For another datapoint, did you have any problems with earlier driver
versions (pre b21)? 2.6.8.1 had b14k...
> Without any I/O on the HBA (nothing mounted), I have yet to capture a
> crash, but the driver still ocasionally reports
> qla2300 0000:01:03.0: cmd_timeout: LOST command state = 0x6
>
> Any help would be greatly appreciated. If there are any tests I could
> run, just let me know.
>
Hmm, could you enable some additional debug settings in the driver:
in qla_settings.h:
modify the following line:
#define DEBUG_QLA2100 0 /* For Debug of qla2x00 */
to read as:
#define DEBUG_QLA2100 1 /* For Debug of qla2x00 */
and in qla_dbg.h
modify the following line:
/* #define QL_DEBUG_LEVEL_2 */ /* Output error msgs to COM1 */
to read as:
#define QL_DEBUG_LEVEL_2 /* Output error msgs to COM1 */
Rerun your test, then forward over the log.
Regards,
Andrew Vasquez
next prev parent reply other threads:[~2004-09-16 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 23:16 qla2xxx: frequent total lockups (2.6.8, 2.6.9-rc{1-mm5,2}) Oliver M. Bolzer
2004-09-16 16:30 ` Andrew Vasquez [this message]
2004-09-18 8:20 ` Oliver M. Bolzer
2004-09-24 14:26 ` Oliver M. Bolzer
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=20040916163029.GA14441@praka.san.rr.com \
--to=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@fakeroot.net \
/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