From: Marc Duponcheel <mduponch@cisco.com>
To: ultralinux@vger.kernel.org
Subject: kernel: scsi : aborting command due to timeout
Date: Tue, 11 Aug 1998 00:31:54 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90280886808916@msgid-missing> (raw)
Hello,
Running UltraPenguin 1.0.9 with CVS kernel 2.1.115 on a Sparc 5 (110Mhz)
Exabyte attached to a 2nd scsi controller scsi ID 6.
When writing to tape the disk on the 2nd scsi controller scsi ID 5 reports
timeout problems (both with tar and dump) and system crashes (I don't find
an Oops but I recall I could see one).
Here is the kernel log (from linux/drivers/scsi/scsi_obsolete.c)
Aug 11 00:45:40 sparc-brew kernel: scsi : aborting command due to timeout: pid 12261, scsi1, channel 0, id 5, lun 0 0x0a 15 c0 22 0 2 00
Aug 11 00:45:40 sparc-brew kernel: esp1: Aborting command
Aug 11 00:45:40 sparc-brew kernel: esp1: dumping state
Aug 11 00:45:40 sparc-brew kernel: esp1: dma -- cond_reg<40040010> addr<f27b2440>
Aug 11 00:45:40 sparc-brew kernel: esp1: SW [sreg<00> sstep<04> ireg<20>]
Aug 11 00:45:40 sparc-brew kernel: esp1: HW reread [sreg<00> sstep<cc> ireg<00>]
Aug 11 00:45:40 sparc-brew kernel:
Aug 11 00:45:40 sparc-brew kernel: esp1: disconnected [tgt<06> lun<00> pphase<FREEING> cphase<FREEING>]
Aug 11 00:45:40 sparc-brew kernel: SCSI disk error : host 1 channel 0 id 5 lun 0 return code = 50000
Aug 11 00:45:40 sparc-brew kernel: scsidisk I/O error: dev 08:51, sector 1425442
Note that:
- this happened when I had less disks attached as well
(running some 2.1.xxx kernels a while back).
[which is why I no longer used the tape steamer but I now tried again]
- With the 2.0.3x kernels the tape steamer worked fine.
(latest 2.0.3x one I used was 2.0.30 in fact)
- the disks work just fine as long as I don't use the tape.
Question(s):
- maybe there is some parameters I can set in order to avoid
timeouts?
- anybody else using an Exabyte successfully on UltraPenguin?
PS: I'll make a kernel with verbose scsi reporting ...
marc@sparc-brew:~ $ [bash] cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: QUANTUM Model: FB1080J SUN1.05 Rev: 630D
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: SEAGATE Model: ST410800N Rev: 0018
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST11200N SUN1.05 Rev: 9500
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST11200N SUN1.05 Rev: 9500
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST11200N SUN1.05 Rev: 9500
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: SEAGATE Model: ST11200N SUN1.05 Rev: 9500
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: EXABYTE Model: EXB-8500SMBANXH1 Rev: 0458
Type: Sequential-Access ANSI SCSI revision: 02
marc@sparc-brew:~ $ [bash] cat /proc/scsi/esp/0
Sparc ESP Host Adapter:
PROM node ffd3d20c
PROM name esp
ESP Model FAS100A
DMA Revision Rev 2
Live Targets [ 3 6 ]
Target # config3 Sync Capabilities Disconnect
Wide
3 00000003 [28,04] yes no
6 00000003 [28,04] yes no
marc@sparc-brew:~ $ [bash] cat /proc/scsi/esp/1
Sparc ESP Host Adapter:
PROM node ffd427e8
PROM name esp
ESP Model FAS236
DMA Revision ESC Rev 1
Live Targets [ 0 1 2 5 6 ]
Target # config3 Sync Capabilities Disconnect
Wide
0 00000018 [6f,04] yes no
1 00000018 [6f,04] yes no
2 00000018 [6f,04] yes no
5 00000018 [6f,04] yes no
6 00000008 [6f,04] yes no
-- Marc Duponcheel.
[work] mduponch@cisco.com
[home] marc@offline.be
reply other threads:[~1998-08-11 0: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=marc-linux-ultrasparc-90280886808916@msgid-missing \
--to=mduponch@cisco.com \
--cc=ultralinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.