Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261606AbUFQSbA (ORCPT ); Thu, 17 Jun 2004 14:31:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261605AbUFQS3P (ORCPT ); Thu, 17 Jun 2004 14:29:15 -0400 Received: from adsl-67-120-171-161.dsl.lsan03.pacbell.net ([67.120.171.161]:27264 "HELO home.linuxace.com") by vger.kernel.org with SMTP id S261426AbUFQS2f (ORCPT ); Thu, 17 Jun 2004 14:28:35 -0400 Date: Thu, 17 Jun 2004 11:28:32 -0700 From: Phil Oester To: linux-kernel@vger.kernel.org Subject: 2.6.7 scsi regression Message-ID: <20040617182832.GA29333@linuxace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3365 Lines: 85 2.6.7 won't boot on a box with a sym53c896 scsi controller, but boots fine on 2.6.6. Dmesg output below. 2.6.6: sym0: <896> rev 0x5 at pci 0000:00:0b.0 irq 17 sym0: using 64 bit DMA addressing sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Using anticipatory io scheduler Vendor: IBM Model: DDYS-T09170N Rev: S80D Type: Direct-Access ANSI SCSI revision: 03 sym0:0:0: tagged command queuing enabled, command queue depth 16. scsi(0:0:0:0): Beginning Domain Validation sym0:0: wide asynchronous. sym0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31) scsi(0:0:0:0): Domain Validation skipping write tests scsi(0:0:0:0): Ending Domain Validation 2.6.7: sym0: <896> rev 0x5 at pci 0000:00:0b.0 irq 17 sym0: using 64 bit DMA addressing sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCSI BUS has been reset. scsi0 : sym-2.1.18j Using anticipatory io scheduler Vendor: IBM Model: DDYS-T09170N Rev: S80D Type: Direct-Access ANSI SCSI revision: 03 sym0:0:0: tagged command queuing enabled, command queue depth 16. scsi(0:0:0:0): Beginning Domain Validation sym0:0: wide asynchronous. sym0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31) scsi(0:0:0:0): Echo buffer size 6552 is too big, trimming to 4096 scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-20 WIDE SCSI 38.5 MB/s ST (52.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-20 WIDE SCSI 26.3 MB/s ST (76.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-10 WIDE SCSI 17.9 MB/s ST (112.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-10 WIDE SCSI 11.9 MB/s ST (168.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: FAST-5 WIDE SCSI 7.9 MB/s ST (252.0 ns, offset 31) scsi(0:0:0:0): Write Buffer failure 8000002 scsi(0:0:0:0): Domain Validation detected failure, dropping back sym0:0: wide asynchronous. sym0:0:0:M_REJECT to send for : 1-3-1-5e-1f. scsi(0:0:0:0): Write Buffer failure 8000002 .... This goes on forever - goes through all different speeds, then starts over. Difference seems to be in 2.6.6, it says: scsi(0:0:0:0): Domain Validation skipping write tests but does not skip these tests in 2.6.7. Ideas? Phil Oester - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/