From: Andrew Morton <akpm@osdl.org>
To: linux-scsi@vger.kernel.org, Matthew Wilcox <willy@debian.org>
Subject: sym2 probs in bk-scsi tree
Date: Wed, 7 Apr 2004 23:18:20 -0700 [thread overview]
Message-ID: <20040407231820.66dd76cd.akpm@osdl.org> (raw)
This is on the power4 machine, which has previously worked quite happily.
During boot the system spends maybe one minute dicking with the SCSI
controller and emitting scary new reset and abort messages.
scsi(0:0:10:0): Beginning Domain Validation
sym0:10: wide asynchronous.
sym0:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(0:0:10:0): Ending Domain Validation
Vendor: IBM Model: IC35L036UCD210-0 Rev: S5BS
Type: Direct-Access ANSI SCSI revision: 03
sym0:11:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:11:0): Beginning Domain Validation
sym0:11: wide asynchronous.
sym0:11: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(0:0:11:0): Ending Domain Validation
Vendor: IBM Model: HSBPD4E PU3SCSI Rev: 0013
Type: Enclosure ANSI SCSI revision: 02
scsi(0:0:15:0): Beginning Domain Validation
sym0:15:0:phase change 6-7 6@28050390 resid=4.
sym0:15:0:phase change 6-7 5@28050390 resid=3.
sym0:15:0:phase change 6-7 9@28050390 resid=7.
sym0:15:0:phase change 6-7 6@28050390 resid=4.
sym0:15:0: DEVICE RESET operation started.
sym0:15:0: DEVICE RESET operation complete.
sym0:15:control msgout: c.
sym0: TARGET 15 has been reset.
sym0:15:0: ABORT operation started.
sym0:15:0: ABORT operation complete.
sym0:15:0: BUS RESET operation started.
sym0:15:0: BUS RESET operation complete.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0:15:0: DEVICE RESET operation started.
sym0:15:0: DEVICE RESET operation complete.
sym0:15:control msgout: c.
sym0: TARGET 15 has been reset.
sym0:15:0: ABORT operation started.
sym0:15:0: ABORT operation complete.
sym0:15:0: BUS RESET operation started.
sym0:15:0: BUS RESET operation complete.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
sym0:15:0: DEVICE RESET operation started.
sym0:15:0: DEVICE RESET operation complete.
sym0:15:control msgout: c.
sym0: TARGET 15 has been reset.
sym0:15:0: ABORT operation started.
sym0:15:0: ABORT operation complete.
sym0:15:0: BUS RESET operation started.
sym0:15:0: BUS RESET operation complete.
sym0: SCSI BUS reset detected.
sym0: SCSI BUS has been reset.
scsi(0:0:15:0): Domain Validation skipping write tests
scsi(0:0:15:0): Ending Domain Validation
sym1: <1010-66> rev 0x1 at pci 0000:41:01.1 irq 104
sym1: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18j
sym2: <875> rev 0x3 at pci 0001:21:01.0 irq 117
sym2: No NVRAM, ID 7, Fast-20, SE, parity checking
sym2: SCSI BUS has been reset.
scsi2 : sym-2.1.18j
st: Version 20040318, fixed bufsize 32768, s/g segs 256
SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2 sda3 sda4 < sda5 >
next reply other threads:[~2004-04-08 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 6:18 Andrew Morton [this message]
2004-04-08 14:57 ` sym2 probs in bk-scsi tree Matthew Wilcox
2004-04-08 15:16 ` Brian King
2004-04-08 15:40 ` Matthew Wilcox
2004-04-08 15:51 ` Brian King
2004-04-08 16:03 ` James Bottomley
2004-04-08 16:59 ` James Bottomley
2004-04-08 20:35 ` Andrew Morton
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=20040407231820.66dd76cd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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