From: Phil Oester <kernel@linuxace.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.7 scsi regression
Date: Thu, 17 Jun 2004 11:28:32 -0700 [thread overview]
Message-ID: <20040617182832.GA29333@linuxace.com> (raw)
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
reply other threads:[~2004-06-17 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040617182832.GA29333@linuxace.com \
--to=kernel@linuxace.com \
--cc=linux-kernel@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