From: "Csaba Halász" <hcs@ics2.ics.tvnet.hu>
To: linux-scsi@vger.kernel.org
Cc: groudier@free.fr
Subject: Strange Diamond Fireport 20 (53c875J Rev4) problems
Date: Tue, 30 Apr 2002 17:13:17 +0200 [thread overview]
Message-ID: <000101c1f059$8ef1a040$0700a8c0@JESTER> (raw)
Hi!
I am experiencing strange behaviour with my scsi card.
With SYM-1 I have to use the specf:0 option, otherwise the driver
gets into an endless loop while downloading scsi scripts during
initialization. (interrupted script address not found)
With 2.2.20 and SYM-1, when I run the the command
dd if=/dev/sr0 of=/dev/null bs=x count=1000
the following happens:
if x <= 54k then everything is OK
if 54k < x <= 56k then I get scsi timeout
if 56k < x then I get interrupted script address not found
With 2.4.18 and SYM-1, I get the interrupted script address message
for all values of x.
With 2.4.18 and SYM-2 none of my devices are detected.
The errors occur both with a MSI K7T Turbo (VIA KT133A chipset)
and an ASUS A7N-266C (nVidia nForce 420) motherboard, using AMD
Thunderbird 850 and Athlon XP 1700+ respectively. The IRQ is not
shared.
The only thing I have been able to figure out is that the error
code indicates an illegal instruction. I have tried to disable
some chip features in the source code, but without any success.
Any help would be appreciated.
Thanks,
Csaba Halasz
Here are some syslog snippets:
2.4.18 SYM-1:
Apr 25 02:34:22 defiant kernel: sym53c8xx: at PCI bus 1, device 7, function
0
Apr 25 02:34:22 defiant kernel: sym53c8xx: 53c875J detected with Symbios
NVRAM
Apr 25 02:34:22 defiant kernel: sym53c875J-0: rev 0x4 on pci bus 1 device 7
function 0 irq 5
Apr 25 02:34:22 defiant kernel: sym53c875J-0: Symbios format NVRAM, ID 7,
Fast-20, Parity Checking
Apr 25 02:34:22 defiant kernel: sym53c875J-0: restart (scsi reset).
Apr 25 02:34:22 defiant kernel: scsi0 : sym53c8xx-1.7.3c-20010512
Apr 25 02:34:24 defiant kernel: Vendor: SANKYO Model: CP525
Rev: 6.64
Apr 25 02:34:24 defiant kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Apr 25 02:34:24 defiant kernel: Vendor: MATSHITA Model: CD-ROM CR-506
Rev: 8S05
Apr 25 02:34:24 defiant kernel: Type: CD-ROM
ANSI SCSI revision: 02
Apr 25 02:34:24 defiant kernel: Vendor: YAMAHA Model: CRW4260
Rev: 1.0q
Apr 25 02:34:24 defiant kernel: Type: CD-ROM
ANSI SCSI revision: 02
Apr 25 02:34:24 defiant kernel: Attached scsi CD-ROM sr0 at scsi0, channel
0, id 5, lun 0
Apr 25 02:34:24 defiant kernel: Attached scsi CD-ROM sr1 at scsi0, channel
0, id 6, lun 0
Apr 25 02:34:24 defiant kernel: sym53c875J-0-<5,*>: asynchronous.
Apr 25 02:34:24 defiant kernel: sr0: scsi-1 drive
Apr 25 02:34:24 defiant kernel: sym53c875J-0-<6,*>: target did not report
SYNC.
Apr 25 02:34:24 defiant kernel: sym53c875J-0-<6,*>: target did not report
SYNC.
Apr 25 02:34:24 defiant kernel: sr1: scsi3-mmc drive: 6x/6x writer cd/rw
xa/form2 cdda tray
Apr 25 02:34:43 defiant kernel: sym53c875J-0-<6,*>: target did not report
SYNC.
Apr 25 02:34:43 defiant kernel: sym53c875J-0-<6,*>: target did not report
SYNC.
Apr 25 02:34:56 defiant kernel: sym53c875J-0: interrupted SCRIPT address not
found.
Apr 25 02:34:56 defiant kernel: sym53c875J-0: restart (scsi reset).
Apr 25 02:34:58 defiant kernel: sym53c875J-0-<6,*>: target did not report
SYNC.
Apr 25 02:34:58 defiant kernel: I/O error: dev 0b:01, sector 102460
Apr 25 02:34:58 defiant kernel: I/O error: dev 0b:01, sector 102460
Apr 25 02:34:58 defiant kernel: I/O error: dev 0b:01, sector 102712
2.4.18 SYM-2:
Apr 25 23:21:23 defiant kernel: sym0: <875> rev 0x4 on pci bus 1 device 7
function 0 irq 5
Apr 25 23:21:23 defiant kernel: sym0: Symbios NVRAM, ID 7, Fast-20, SE,
parity checking
Apr 25 23:21:23 defiant kernel: sym0: open drain IRQ line driver, using
on-chip SRAM
Apr 25 23:21:23 defiant kernel: sym0: using LOAD/STORE-based firmware.
Apr 25 23:21:23 defiant kernel: sym0: SCAN AT BOOT disabled for targets 0 1
2 4 8 9 10 11 12 13 14 15.
Apr 25 23:21:23 defiant kernel: sym0: SCAN FOR LUNS disabled for targets 0 1
2 3 4 5 6 8 9 10 11 12 13 14 15.
Apr 25 23:21:23 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:21:26 defiant kernel: sym0:3: ERROR (81:0) (8-28-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:21:26 defiant kernel: sym0: regdump: da 10 80 05 47 00 03 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:21:26 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:21:26 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:21:29 defiant kernel: sym0:3: ERROR (81:0) (8-28-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:21:29 defiant kernel: sym0: regdump: da 10 80 05 47 00 03 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:21:29 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:21:29 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:21:29 defiant kernel: sym0:3:0: DEVICE RESET operation started.
Apr 25 23:21:29 defiant kernel: sym0:3:0: DEVICE RESET operation failed.
Apr 25 23:21:29 defiant kernel: sym0:3:0: BUS RESET operation started.
Apr 25 23:21:29 defiant kernel: sym0:3:0: BUS RESET operation failed.
Apr 25 23:21:34 defiant kernel: sym0:3:0: HOST RESET operation started.
Apr 25 23:21:34 defiant kernel: sym0:3:0: HOST RESET operation failed.
Apr 25 23:21:44 defiant kernel: sym0:5: ERROR (81:0) (8-ae-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:21:44 defiant kernel: sym0: regdump: da 10 80 05 47 00 05 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:21:44 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:21:44 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:21:48 defiant kernel: sym0:5: ERROR (81:0) (8-ae-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:21:48 defiant kernel: sym0: regdump: da 10 80 05 47 00 05 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:21:48 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:21:48 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:21:48 defiant kernel: sym0:5:0: DEVICE RESET operation started.
Apr 25 23:21:48 defiant kernel: sym0:5:0: DEVICE RESET operation failed.
Apr 25 23:21:48 defiant kernel: sym0:5:0: BUS RESET operation started.
Apr 25 23:21:48 defiant kernel: sym0:5:0: BUS RESET operation failed.
Apr 25 23:21:53 defiant kernel: sym0:5:0: HOST RESET operation started.
Apr 25 23:21:53 defiant kernel: sym0:5:0: HOST RESET operation failed.
Apr 25 23:22:03 defiant kernel: sym0:6: ERROR (81:0) (8-28-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:22:03 defiant kernel: sym0: regdump: da 10 80 05 47 00 06 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:22:03 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:22:03 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:22:06 defiant kernel: sym0:6: ERROR (81:0) (8-28-0) (0/5/0) @ (mem
8c0068:ffffbfff).
Apr 25 23:22:06 defiant kernel: sym0: regdump: da 10 80 05 47 00 06 0e 00 08
00 ae 80 00 0e 02 00 cc 8c 1a 08 ff ff ff.
Apr 25 23:22:06 defiant kernel: sym0: SCSI BUS reset detected.
Apr 25 23:22:06 defiant kernel: sym0: SCSI BUS has been reset.
Apr 25 23:22:06 defiant kernel: sym0:6:0: DEVICE RESET operation started.
Apr 25 23:22:06 defiant kernel: sym0:6:0: DEVICE RESET operation failed.
Apr 25 23:22:06 defiant kernel: sym0:6:0: BUS RESET operation started.
Apr 25 23:22:06 defiant kernel: sym0:6:0: BUS RESET operation failed.
Apr 25 23:22:11 defiant kernel: sym0:6:0: HOST RESET operation started.
Apr 25 23:22:11 defiant kernel: sym0:6:0: HOST RESET operation failed.
(The memory locations vary, I don't remember seeing the same twice.)
next reply other threads:[~2002-04-30 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 15:13 Csaba Halász [this message]
2002-04-30 0:39 ` Strange Diamond Fireport 20 (53c875J Rev4) problems Gérard Roudier
2002-05-01 16:42 ` Csaba Halász
2002-05-03 0:08 ` Gérard Roudier
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='000101c1f059$8ef1a040$0700a8c0@JESTER' \
--to=hcs@ics2.ics.tvnet.hu \
--cc=groudier@free.fr \
--cc=linux-scsi@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