From: Josip Rodin <joy@entuzijast.net>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: sparclinux@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: kernel 2.6.26.3 qla2xxx oopsing on Fire 280R
Date: Thu, 11 Sep 2008 13:37:27 +0200 [thread overview]
Message-ID: <20080911113727.GA24487@orion.carnet.hr> (raw)
In-Reply-To: <20080909143932.GA27117@orion.carnet.hr>
On Tue, Sep 09, 2008 at 04:39:32PM +0200, Josip Rodin wrote:
> On Mon, Sep 08, 2008 at 07:01:02PM -0700, Andrew Vasquez wrote:
> > Yes, please do try the patch. Could you also enable error-logging via
> > the ql2xextended_error_logging module parameter:
> >
> > # insmod qla2xxx.ko ql2xextended_error_logging=1
> >
> > And send the kernel messages... Thanks, AV
>
> OK, I reset the bisection, pulled the latest updates, applied your patch
> and added the parameter to the initrd module setup, rebuilt after an
> all-enter make oldconfig. After rebooting, it failed to load the firmware:
>
> scsi(0): **** Load RISC code ****
> firmware: requesting ql2200_fw.bin
> scsi(0): Failed to load firmware image (ql2200_fw.bin).
> qla2xxx 0001:00:04.0: Firmware image unavailable.
OK, so I did git reset --hard bed475c4cde5d12f537f445bdd0a5a3bb5684481
to get back to the point which the bisection said was the problem, and
yet that version of 2.6.27-rc2 also exhibited the firmware problem.
Then I went back up to git reset --hard bf6583b5831d3195c45f98ec3016499389cbe18f
to see if it'll do that again, and that 2.6.26 *also* did the same.
So I reviewed my steps and concluded that the only other thing different was
adding ql2xextended_error_logging=1. I undid that change, rebuilt the
initramfs image, and then the machine booted fine!
So, um, please fix the debugging code so that it doesn't cause more bugs... :/
In the meantime, I'll go back up to bed475c4cde5d12f537f445bdd0a5a3bb5684481
and see how it does with the debugging patch.
--
2. That which causes joy or happiness.
next prev parent reply other threads:[~2008-09-11 11:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 9:39 kernel 2.6.26.3 qla2xxx oopsing on Fire 280R Josip Rodin
2008-09-08 21:13 ` Andrew Vasquez
2008-09-08 21:23 ` David Miller
2008-09-08 21:49 ` Andrew Vasquez
2008-09-08 23:08 ` David Miller
2008-09-08 23:42 ` Josip Rodin
2008-09-09 1:35 ` Andrew Vasquez
2008-09-09 1:49 ` Josip Rodin
2008-09-09 1:53 ` Josip Rodin
2008-09-09 2:01 ` Andrew Vasquez
2008-09-09 14:39 ` Josip Rodin
2008-09-09 15:00 ` Josip Rodin
2008-09-09 21:30 ` David Miller
2008-09-09 22:00 ` Josip Rodin
2008-09-09 22:57 ` David Miller
2008-09-09 22:59 ` David Miller
2008-09-10 0:05 ` Josip Rodin
2008-09-10 0:30 ` David Miller
2008-09-11 11:37 ` Josip Rodin [this message]
2008-09-11 21:57 ` Josip Rodin
2008-09-11 22:01 ` David Miller
2008-09-11 22:15 ` Andrew Vasquez
2008-09-12 5:19 ` [PATCH scsi-rc-fixes] qla2xxx: Defer enablement of RISC interrupts until ISP initialization completes 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=20080911113727.GA24487@orion.carnet.hr \
--to=joy@entuzijast.net \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sparclinux@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