From: Grant Grundler <grundler@parisc-linux.org>
To: Andrew Vasquez <praka@users.sourceforge.net>,
linux-scsi@vger.kernel.org,
Grant Grundler <grundler@parisc-linux.org>
Subject: Re: [BUG] modprobe qla2300 doesn't complete
Date: Fri, 5 Mar 2004 08:57:17 -0700 [thread overview]
Message-ID: <20040305155717.GA17305@colo.lackof.org> (raw)
In-Reply-To: <20040305071721.GA9684@praka.local.home>
On Thu, Mar 04, 2004 at 11:17:21PM -0800, Andrew Vasquez wrote:
> I've seen this behaviour before, I thought we fixed this :(
oh - bummer. :^(
> > I can make the system remotely available if someone wants to
> > debug this some more.
>
> That may be useful.
Yes. :^)
(I've debugged a fair number of issues like this in the past)
Andrew, I need preferred login, public ssh key (eg id_rsa.pub),
and telephone number where I reach in case of urgent admin issues.
I can then setup an account and explain how to access.
> In the interim, could you just enable a couple of
> debug settings in the driver and rerun against the volitile fabric
yes - np.
> (just a short period, say 30 seconds), then send the /var/log/messages
> file. I believe I know the problem, I just need to be sure the
> stimulus coming from the fabric is what I would expect.
>
> o Set DEBUG_QLA2100 to 1 in qla_settings.h
>
> o Define QL_DEBUG_LEVEL_2 in qla_dbg.h.
I'll include output in my next reply.
thanks,
grant
>
> Regards,
> Andrew Vasquez
> QLogic Corporation
next prev parent reply other threads:[~2004-03-05 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 4:18 [BUG] modprobe qla2300 doesn't complete Grant Grundler
2004-03-05 7:17 ` Andrew Vasquez
2004-03-05 15:57 ` Grant Grundler [this message]
2004-03-05 17:21 ` Grant Grundler
2004-03-09 16:40 ` Andrew Vasquez
2004-03-10 22:12 ` Grant Grundler
2004-03-12 6:11 ` Andrew Vasquez
2004-03-12 12:30 ` Lincoln Dale
2004-03-15 5:06 ` Andrew Vasquez
2004-03-12 18:32 ` Grant Grundler
2004-03-14 6:33 ` Grant Grundler
2004-12-27 18:59 ` Grant Grundler
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=20040305155717.GA17305@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-scsi@vger.kernel.org \
--cc=praka@users.sourceforge.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