James Bottomley wrote:
> I got this one again over the weekend:
>
> aic94xx: max_scbs:512, max_ddbs:128
> aic94xx: setting phy0 addr to 50000d100001cae0
> aic94xx: setting phy1 addr to 50000d100001cae0
> aic94xx: setting phy2 addr to 50000d100001cae0
> aic94xx: setting phy3 addr to 50000d100001cae0
> aic94xx: setting phy4 addr to 50000d100001cae0
> aic94xx: setting phy5 addr to 50000d100001cae0
> aic94xx: setting phy6 addr to 50000d100001cae0
> aic94xx: setting phy7 addr to 50000d100001cae0
> aic94xx: num_edbs:21
> aic94xx: num_escbs:3
> aic94xx: using sequencer Razor_10a1
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.
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)
My card needed [a] to stabilize the POST and device scan
that the 48300 does prior to the OS loading. Once the
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.
Doug Gilbert
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
