public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: dougg@torque.net, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: aic94xx panic on module insertion
Date: Mon, 10 Jul 2006 10:08:15 -0700	[thread overview]
Message-ID: <20060710170815.GD30179@us.ibm.com> (raw)
In-Reply-To: <1152549628.7275.24.camel@mulgrave.il.steeleye.com>

James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Mon, 2006-07-10 at 12:25 -0400, Douglas Gilbert wrote:
> > aic94xx driver is loaded, it replaces the running version
> > of the sequencer code with its own copy. If the reader
> > sees numerous "tmf timeout" messages in their log then
> > there is a good chance old sequencer code is the cause.
> 
> And really, this driver needs to use the firmware loader, so this
> no-longer becomes an issue.

Well as I mentioned before it would be good if the distro support was more
widespread before we cutoff the old method. I received a lot of questions
recently from qla2xxx users who where use to doing kernel testing with not
the latest distro version. They ran into issues when trying
linux-2.6.18-rc1 (or git tree versions) along with trying to get the
firmware loading support to work on there distro. 

-andmike
--
Michael Anderson
andmike@us.ibm.com

  reply	other threads:[~2006-07-10 17:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 14:22 aic94xx panic on module insertion James Bottomley
2006-07-10 16:25 ` Douglas Gilbert
2006-07-10 16:40   ` James Bottomley
2006-07-10 17:08     ` Mike Anderson [this message]
2006-07-10 21:18       ` James Bottomley
2006-07-10 17:29 ` Mike Anderson
2006-07-10 21:07   ` James Bottomley
2006-07-11  4:52     ` Mike Anderson
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11  8:05 Robert Tarte

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=20060710170815.GD30179@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dougg@torque.net \
    --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