what was your solution to this problem?
I have identical symptons on a high-end Intel dual-pentium-pro server
that appears to have three NCR scsi chips on the motherboard (RAID?) and
Symbios bios.
On Fri, Apr 09, 1999 at 01:16:32PM -0700, Matthew Jacob wrote:
> > > + It might be nice to have NCR_SCSI_MYADDR actually be a patchable
> > > variable for modprobe- Most of these cards have BIOS/NVRAM, but
> > > a lot don't and it'd be nice to be able to change the default
> > > initiator ID w/o recompiling.
> >
> > Recompiling is the only way to be sure you are actually running the
> > program you want to run. :-)
>
> Not if you explicitly want to change it w/o recompiles.
>
> >
> > > + The driver's a bit chatty about Queue Full conditions- I get a
> > > stream of:
> > >
>
> We all know Quantum F/W if flakey..
>
> I put the latest (d01) patches and and used the sym driver instead and
> did 64 tags for the linux side and put a much heavier load on both sides.
>
> What I get now at least once was:
>
> scsi : aborting command due to timeout : pid 112110, scsi1, channel 0, id
> 4, lun 0 Read (10) 00 00 89 58 da 00 00 52 00
> sym53c8xx_abort: pid=112110 serial_number=112157
> serial_number_at_timeout=112157
> scsi : aborting command due to timeout : pid 112111, scsi1, channel 0, id
> 4, lun 0 Read (10) 00 00 89 59 ac 00 00 46 00
> sym53c8xx_abort: pid=112111 serial_number=112158
> serial_number_at_timeout=112158
> sym53c895-0: abort ccb=c325f000 (cancel)
> scsi : aborting command due to timeout : pid 112109, scsi1, channel 0, id
> 4, lun 0 Read (10) 00 00 89 58 d2 00 00 08 00
> sym53c8xx_abort: pid=112109 serial_number=112159
> serial_number_at_timeout=112159
> sym53c895-0: abort ccb=c2fc2000 (cancel)
> SCSI host 1 abort (pid 112109) timed out - resetting
> SCSI bus is being reset for host 1 channel 0.
> sym53c8xx_reset: pid=112109 reset_flags=2 serial_number=112159
> serial_number_at_timeout=112159
> sym53c895-0: restart (scsi reset).
> sym53c895-0: Downloading SCSI SCRIPTS.
> sym53c895-0-<4,*>: FAST-40 WIDE SCSI 80.0 MB/s (25 ns, offset 31)
>
>
> The other side (still Solaris) sees:
>
> WARNING: /pci@1f,4000/scsi@4/sd@4,0 (sd162):
> SCSI transport failed: reason 'reset': retrying command
>
> I don't see a gap in transfers from the Solaris side. It's also now true
> in this configuration that the Solaris side has lower priority (at ID 6).
>
> >
> > PS: Could you give a shot with the sym53c8xx driver and let me know if
> > it works on the Linux/Sparc. (Btw, it is ok for x86).
>
> Next on my list... I'm running wads of tests right now. When the
> complete, I'll rehook the UltraLinux.
>
> -matt
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
