From: "Robert Tarte" <robt@PacificCodeWorks.com>
To: dougg@torque.net, linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: aic94xx panic on module insertion
Date: Tue, 11 Jul 2006 01:05:06 -0700 [thread overview]
Message-ID: <16C8363E16D7234AB844FDB52D4AEA650C2DB5@ntserv.PacificCodeWorks.local> (raw)
> These comments have no direct bearing on the panic that
> James is reporting, but ... that sequencer version:
> "Razor_10a1" is old and should be updated.
[Tarte, Robert] I apologize for posting from this account, but my VPN
access is down. There is patch available the updates the sequencer in
aic94xx to the latest version. It is fairly ugly, because it is full of
sequencer hex. I don't believe that this is related to James' problem.
Mike and Alexis have tried it out and it seems to running fine. Doug,
Are you just developing on Luben's kernel, or would you like me to send
you the patch?
>
> With a 48300 adapter I needed to do two things:
> [a] update the board's BIOS firmware from build 1618
> to 1705 (20060421) [See adaptec's site]
> [b] update the linux driver's copy of the sequencer
> code (in my case from Razor_10c2 to Razor_10c5b)
>
next reply other threads:[~2006-07-11 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 8:05 Robert Tarte [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=16C8363E16D7234AB844FDB52D4AEA650C2DB5@ntserv.PacificCodeWorks.local \
--to=robt@pacificcodeworks.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