Re: phase change messages cusing slowdown with sym53c8xx_2 driver

[James Bottomley <James.Bottomley@SteelEye.com>]

On Wed, 2004-12-01 at 11:56, Jose R. Santos wrote:
> > Nov 28 23:05:12 orb kernel: sym0: <896> rev 0x5 at pci 0000:00:0c.0 irq 20
> > Nov 28 23:05:12 orb kernel: sym0: No NVRAM, ID 7, Fast-40, SE, parity checking
> > Nov 28 23:05:12 orb kernel: sym0: SCSI BUS has been reset.
> > Nov 28 23:05:12 orb kernel: scsi0 : sym-2.1.18m
> > Nov 28 23:05:12 orb kernel: sym0:1: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
> > Nov 28 23:05:12 orb kernel:   Vendor: IBM       Model: DGHS09U	Rev: 03E0
> > Nov 28 23:05:12 orb kernel:   Type:   Direct-Access		ANSI SCSI revision: 03
> > Nov 28 23:05:12 orb kernel:  target0:0:1: Beginning Domain Validation
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@10050390 resid=6.
> > Nov 28 23:05:12 orb last message repeated 10 times
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@1005039c resid=6.
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@10050390 resid=6.
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@10050390 resid=6.
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@1005039c resid=6.
> > Nov 28 23:05:12 orb kernel:  target0:0:1: Domain Validation skipping write tests
> > Nov 28 23:05:12 orb kernel:  target0:0:1: Ending Domain Validation
> > Nov 28 23:05:12 orb kernel: sym0:1:0:phase change 6-7 9@10050390 resid=6.
> > 
> > When these errors show up, the maximum performance I can get out of the disk is
> > about 1.3MB/s.  After several hours, the adapters seems to receive some ABORT 
> > operations and the messages stop showing.  Once this happens, performance for 
> > the disk goes back to 15MB/s.
> 
> I manage to get access to another PPC64 box that has uses this same
> driver and was unable to reproduce this problem here, but I was able to
> reproduce it on another same model machine.  Seem like there could be
> something at initialization that only affects this revision of the SCSI
> adapter.  Since the problem seems to disappear after a BUS RESET I assume
> that something was left out when the driver was initializing the adapter.

Matthew,

does this look like the "drive won't respond properly to PPR if the bus
is SE" problem again?

James