From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Thomas Georgiou <tageorgiou@gmail.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: QLA2200 causes kernel bug
Date: Thu, 6 Aug 2009 09:49:25 -0700 [thread overview]
Message-ID: <20090806164925.GO2453@plap4-2.local> (raw)
In-Reply-To: <6e4c20e70908060828xd4a6a8fh801e1d456c39a5f@mail.gmail.com>
On Thu, 06 Aug 2009, Thomas Georgiou wrote:
> Whenever I have the qla2xxx module loaded, some kernel problem
> eventually occurs. Sometimes its an oops, a bug, or once, a crash.
> The same thing has been seen to happen on 3 different machines all
> with qla2200 cards in them.
>
> Here is the latest backtrace:
> [42151.610011] kernel BUG at drivers/scsi/scsi_transport_fc.c:3022!
> [42151.610011] invalid opcode: 0000 [#1] SMP
This looks similar to:
http://thread.gmane.org/gmane.linux.scsi/49853/focus=50297
with a proposed (though not-liked) solution here:
http://article.gmane.org/gmane.linux.scsi/50297
Could someone refresh my memory, why was there an issue with re-adding
rports after dev-loss-tmo triggered?
Thomas, could you forward the full messages file? I'm interested in
seeing what series of events led up to the BUG_ON(). The snippets
here and in the bugzilla only document the failing point BUG_ON().
Also, could you get a test run with the driver error-logging enabled
as well:
$ modprobe -v qla2xxx ql2xextended_error_logging=1
-- av
next prev parent reply other threads:[~2009-08-06 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 15:28 QLA2200 causes kernel bug Thomas Georgiou
2009-08-06 16:49 ` Andrew Vasquez [this message]
2009-08-06 17:12 ` Thomas Georgiou
2009-08-07 3:40 ` Thomas Georgiou
2009-08-07 7:01 ` Andrew Vasquez
2009-08-07 19:19 ` Thomas Georgiou
2009-08-07 21:11 ` Andrew Vasquez
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=20090806164925.GO2453@plap4-2.local \
--to=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tageorgiou@gmail.com \
/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