From: Chris Worley <cworley@lnxi.com>
To: linux-scsi@vger.kernel.org
Subject: Qlogic driver hang
Date: 02 Oct 2003 09:45:31 -0600 [thread overview]
Message-ID: <1065109530.24236.6127.camel@localhost.localdomain> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B060ED34@AVEXCH02.qlogic.org>
In using the 6.06.00 version of the qlogic driver, the module load gets
to:
Verifying chip...
And hangs the system. The older driver would print out:
Firmware version: 3.01.13, Driver version 6.01.00
at this point. Any ideas what I'm doing wrong?
Thanks,
Chris
On Tue, 2003-09-30 at 16:25, Andrew Vasquez wrote:
> Chris
>
> > The tarball from Qlogic was labeled:
> >
> > qla2x00-v6.01.00-dist.tgz
> >
> > It's the full-height, PCI-X, 133MHz, single port, 2340 (I think).
> >
> >
>
> Ouch, that's a really old driver (with some known [error handling]
> problems). Would it be possible to start with something a bit more
> recent, 6.06.00 has been posted to QLogic's website:
>
> http://www.qlogic.com/support/product_resources.asp?id=253
> http://download.qlogic.com/drivers/13591/qla2x00-v6.06.00-dist.tgz
>
> I'd suggest we start from there. If you are still experiencing
> problems, forward the /var/log/messages file after you enable
> 'Extended Error Logging' from the BIOS utility. If you feel
> comfortable changing some lines in the driver source, more descript
> (helpful) logs can be obtained with the following three changes:
>
> o In the qla_settings.h file change the following line from:
>
> #define DEBUG_QLA2100 0 /* For Debug of qla2x00 */
> to
> #define DEBUG_QLA2100 1 /* For Debug of qla2x00 */
>
> o In the qla2x00.h file change the following line from:
>
> /* #define QL_DEBUG_LEVEL_2 */ /* Output error msgs to COM1 */
> to
> #define QL_DEBUG_LEVEL_2 /* Output error msgs to COM1 */
>
> o In the qla2x00.c file change the following line from:
>
> static int extended_error_logging = 0; /* 0 = off, 1 = log errors */
> to
> static int extended_error_logging = 1; /* 0 = off, 1 = log errors */
>
> Recompile & load the driver.
>
> Regards,
> Andrew Vasquez
next parent reply other threads:[~2003-10-02 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B179AE41C1147041AA1121F44614F0B060ED34@AVEXCH02.qlogic.org>
2003-10-02 15:45 ` Chris Worley [this message]
2003-10-02 18:16 ` Qlogic driver hang Steven Dake
2003-10-02 18:25 ` Mark Bellon
2003-10-02 19:24 ` Tim Pepper
2003-10-02 19:43 ` Mark Bellon
2003-10-03 5:53 ` Andrew Vasquez
2003-10-03 18:15 ` 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=1065109530.24236.6127.camel@localhost.localdomain \
--to=cworley@lnxi.com \
--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