* Re: Strange Diamond Fireport 20 (53c875J Rev4) problems
2002-04-30 15:13 Strange Diamond Fireport 20 (53c875J Rev4) problems Csaba Halász
@ 2002-04-30 0:39 ` Gérard Roudier
2002-05-01 16:42 ` Csaba Halász
0 siblings, 1 reply; 4+ messages in thread
From: Gérard Roudier @ 2002-04-30 0:39 UTC (permalink / raw)
To: Csaba Halász; +Cc: linux-scsi
On Tue, 30 Apr 2002, Csaba Halász wrote:
> 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.
My immediate idea is that your HBA may well be just broken.
I highly suspect the on-chip RAM to be one of the part that doesn't
function properly (at least). This let me suggest you to check that.
The following simple patch against SYM-2 will ensure that the driver will
not use the on-chip RAM of your controller for SCSI SCRIPTS.
--- sym_hipd.c.orig Sat Dec 29 22:58:58 2001
+++ sym_hipd.c Tue Apr 30 02:30:19 2002
@@ -1332,7 +1332,7 @@
,
{PCI_ID_SYM53C875_2, 0xff, "875", 6, 16, 5, 2,
FE_WIDE|FE_ULTRA|FE_DBLR|FE_CACHE0_SET|FE_BOF|FE_DFS|FE_LDSTR|FE_PFEN|
- FE_RAM|FE_DIFF|FE_VARCLK}
+ FE_DIFF|FE_VARCLK}
,
{PCI_ID_SYM53C885, 0xff, "885", 6, 16, 5, 2,
FE_WIDE|FE_ULTRA|FE_DBLR|FE_CACHE0_SET|FE_BOF|FE_DFS|FE_LDSTR|FE_PFEN|
------ < CUT HERE > --------------
Just apply it to 2.4.18/driver/scsi/sym53c8xx_2 and rebuild the driver
and/or the kernel. You may let me know if this makes any noticeable
difference.
Regards,
Gérard.
> 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.)
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* Strange Diamond Fireport 20 (53c875J Rev4) problems
@ 2002-04-30 15:13 Csaba Halász
2002-04-30 0:39 ` Gérard Roudier
0 siblings, 1 reply; 4+ messages in thread
From: Csaba Halász @ 2002-04-30 15:13 UTC (permalink / raw)
To: linux-scsi; +Cc: groudier
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.)
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Strange Diamond Fireport 20 (53c875J Rev4) problems
2002-04-30 0:39 ` Gérard Roudier
@ 2002-05-01 16:42 ` Csaba Halász
2002-05-03 0:08 ` Gérard Roudier
0 siblings, 1 reply; 4+ messages in thread
From: Csaba Halász @ 2002-05-01 16:42 UTC (permalink / raw)
To: 'Gérard Roudier'; +Cc: linux-scsi
Dear Gérard,
Thank you for your quick answer.
I indeed had to remove the FE_RAM flag just as you said to get the driver
loaded. I am using a "dd if=/dev/srx of=/dev/null bs=2048" command for
testing. If I leave the FE_PFEN flag then I get this for my cd-rom:
May 1 15:21:48 defiant kernel: sym0:5:0:internal error: cmd=11 !=
9f=(vdsp[0] >> 24)
May 1 15:21:48 defiant kernel: sym0: SCSI BUS reset detected.
May 1 15:21:48 defiant kernel: sym0: SCSI BUS has been reset.
(also with cmd=19)
For my cd writer:
May 1 16:39:12 defiant kernel: sym0:6:0:phase change 7-1 1@1b9fa778
resid=1.
May 1 16:39:12 defiant kernel: sym0: SCSI BUS reset detected.
May 1 16:39:12 defiant kernel: sym0: SCSI BUS has been reset.
If I remove the FE_PFEN flag as well, then I get this for my cd writer:
May 1 15:49:34 defiant kernel: sym0:6: No MSG IN phase after reselection.
May 1 15:50:04 defiant kernel: sym0:6:0: ABORT operation started.
May 1 15:50:09 defiant kernel: sym0:6:0: ABORT operation timed-out.
May 1 15:50:09 defiant kernel: sym0:6:0: ABORT operation started.
May 1 15:50:14 defiant kernel: sym0:6:0: ABORT operation timed-out.
May 1 15:50:14 defiant kernel: sym0:6:0: DEVICE RESET operation started.
May 1 15:50:19 defiant kernel: sym0:6:0: DEVICE RESET operation timed-out.
May 1 15:50:19 defiant kernel: sym0:6:0: BUS RESET operation started.
May 1 15:50:19 defiant kernel: sym0: SCSI BUS reset detected.
May 1 15:50:19 defiant kernel: sym0: SCSI BUS has been reset.
May 1 15:50:19 defiant kernel: sym0:6:0: BUS RESET operation complete.
May 1 15:52:21 defiant kernel: sym0:6: No IDENTIFY after reselection.
May 1 15:52:51 defiant kernel: sym0:6:0: ABORT operation started.
May 1 15:52:56 defiant kernel: sym0:6:0: ABORT operation timed-out.
May 1 15:52:56 defiant kernel: scsi: device set offline - not ready or
command retry failed after bus reset: host 0 channel 0 id 6 lun 0
May 1 15:53:06 defiant kernel: sym0:6:0: ABORT operation started.
May 1 15:53:11 defiant kernel: sym0:6:0: ABORT operation timed-out.
May 1 15:53:11 defiant kernel: scsi: device set offline - not ready or
command retry failed after bus reset: host 0 channel 0 id 6 lun 0
at which point dd returns, but rmmod locks up.
For my cd-rom:
May 1 15:58:24 defiant kernel: sym0:5: FAST-10 SCSI 10.0 MB/s ST (100.0 ns,
offset 15)
May 1 15:58:39 defiant kernel: sym0:5: No IDENTIFY after reselection.
May 1 15:59:09 defiant kernel: sym0:5:0: ABORT operation started.
May 1 15:59:14 defiant kernel: sym0:5:0: ABORT operation timed-out.
May 1 15:59:14 defiant kernel: sym0:5:0: ABORT operation started.
May 1 15:59:19 defiant kernel: sym0:5:0: ABORT operation timed-out.
May 1 15:59:19 defiant kernel: sym0:5:0: DEVICE RESET operation started.
May 1 15:59:24 defiant kernel: sym0:5:0: DEVICE RESET operation timed-out.
May 1 15:59:24 defiant kernel: sym0:5:0: BUS RESET operation started.
May 1 15:59:24 defiant kernel: sym0: SCSI BUS reset detected.
May 1 15:59:24 defiant kernel: sym0: SCSI BUS has been reset.
May 1 15:59:24 defiant kernel: sym0:5:0: BUS RESET operation complete.
May 1 15:59:32 defiant kernel: sym0:5: No IDENTIFY after reselection.
at which point the driver locks up, dd is stuck in "D" state and rmmod
says "device or resource busy".
Note that the transfer mode is synchronous, even though the SYM-1 driver
uses async mode. Just to check that possibility I used the "setsync 5 0"
sysctl, but the results were the same.
Removing FE_LDSTR I get this:
May 1 16:30:53 defiant kernel: sym0:6: ERROR (81:0) (8-0-0) (0/5/0) @
(scripta c:00000000).
May 1 16:30:53 defiant kernel: sym0: script cmd = 00000000
May 1 16:30:53 defiant kernel: sym0: regdump: da 00 40 05 47 00 06 0f 04 08
86 00 80 00 07 02 00 a0 2f 1e 02 ff ff ff.
May 1 16:30:53 defiant kernel: sym0: SCSI BUS reset detected.
May 1 16:30:53 defiant kernel: sym0: SCSI BUS has been reset.
May 1 16:31:09 defiant kernel: sym0:5: ERROR (81:0) (8-0-0) (f/35/0) @
(scripta c:00000000).
May 1 16:31:09 defiant kernel: sym0: script cmd = 00000000
May 1 16:31:09 defiant kernel: sym0: regdump: da 00 40 35 47 0f 05 0f 04 08
85 00 80 00 07 02 00 a0 2f 1e 02 ff ff ff.
May 1 16:31:09 defiant kernel: sym0: SCSI BUS reset detected.
May 1 16:31:09 defiant kernel: sym0: SCSI BUS has been reset.
The other flags do not seem to have an effect on this problem, I even went
all the way to just FE_DBLR|FE_VARCLK.
I also tried using IO mapped mode instead of memory mapped, but that didn't
help either.
Do you have any more suggestions?
Greets,
Csaba
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Strange Diamond Fireport 20 (53c875J Rev4) problems
2002-05-01 16:42 ` Csaba Halász
@ 2002-05-03 0:08 ` Gérard Roudier
0 siblings, 0 replies; 4+ messages in thread
From: Gérard Roudier @ 2002-05-03 0:08 UTC (permalink / raw)
To: Csaba Halász; +Cc: linux-scsi
On Wed, 1 May 2002, Csaba Halász wrote:
> Dear Gérard,
>
> Thank you for your quick answer.
>
> I indeed had to remove the FE_RAM flag just as you said to get the driver
> loaded. I am using a "dd if=/dev/srx of=/dev/null bs=2048" command for
> testing. If I leave the FE_PFEN flag then I get this for my cd-rom:
>
> May 1 15:21:48 defiant kernel: sym0:5:0:internal error: cmd=11 !=
> 9f=(vdsp[0] >> 24)
Never seen this one before.
It might be a driver internal error, but it also happens if the chip is
lying about the actual value of the interrupted SCRIPTS address on a
phase mismatch (i.e. DSP register value not correct).
> May 1 15:21:48 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 15:21:48 defiant kernel: sym0: SCSI BUS has been reset.
>
> (also with cmd=19)
Same as above.
> For my cd writer:
>
> May 1 16:39:12 defiant kernel: sym0:6:0:phase change 7-1 1@1b9fa778
> resid=1.
> May 1 16:39:12 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 16:39:12 defiant kernel: sym0: SCSI BUS has been reset.
>
> If I remove the FE_PFEN flag as well, then I get this for my cd writer:
>
>
> May 1 15:49:34 defiant kernel: sym0:6: No MSG IN phase after reselection.
> May 1 15:50:04 defiant kernel: sym0:6:0: ABORT operation started.
> May 1 15:50:09 defiant kernel: sym0:6:0: ABORT operation timed-out.
> May 1 15:50:09 defiant kernel: sym0:6:0: ABORT operation started.
> May 1 15:50:14 defiant kernel: sym0:6:0: ABORT operation timed-out.
> May 1 15:50:14 defiant kernel: sym0:6:0: DEVICE RESET operation started.
> May 1 15:50:19 defiant kernel: sym0:6:0: DEVICE RESET operation timed-out.
> May 1 15:50:19 defiant kernel: sym0:6:0: BUS RESET operation started.
> May 1 15:50:19 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 15:50:19 defiant kernel: sym0: SCSI BUS has been reset.
> May 1 15:50:19 defiant kernel: sym0:6:0: BUS RESET operation complete.
> May 1 15:52:21 defiant kernel: sym0:6: No IDENTIFY after reselection.
> May 1 15:52:51 defiant kernel: sym0:6:0: ABORT operation started.
> May 1 15:52:56 defiant kernel: sym0:6:0: ABORT operation timed-out.
> May 1 15:52:56 defiant kernel: scsi: device set offline - not ready or
> command retry failed after bus reset: host 0 channel 0 id 6 lun 0
> May 1 15:53:06 defiant kernel: sym0:6:0: ABORT operation started.
> May 1 15:53:11 defiant kernel: sym0:6:0: ABORT operation timed-out.
> May 1 15:53:11 defiant kernel: scsi: device set offline - not ready or
> command retry failed after bus reset: host 0 channel 0 id 6 lun 0
The PFEN flag makes the driver enable SCRIPTS intructions prefetching.
When cleared, the driver does not enable this chip feature. Normally :),
this should not affect the chip behaviour, since it is just a PCI
optimization that is enabled by default. The difference looks extremally
weird to me.
The apparent errors reported (no MSG IN phase or No IDENTIFY after
reselection) that happen for both your cdw and cd) are probably not real.
Since SCSI-2, SCSI devices are required to send an IDENTIFY message after
reselection.
> at which point dd returns, but rmmod locks up.
> For my cd-rom:
>
> May 1 15:58:24 defiant kernel: sym0:5: FAST-10 SCSI 10.0 MB/s ST (100.0 ns,
> offset 15)
> May 1 15:58:39 defiant kernel: sym0:5: No IDENTIFY after reselection.
> May 1 15:59:09 defiant kernel: sym0:5:0: ABORT operation started.
> May 1 15:59:14 defiant kernel: sym0:5:0: ABORT operation timed-out.
> May 1 15:59:14 defiant kernel: sym0:5:0: ABORT operation started.
> May 1 15:59:19 defiant kernel: sym0:5:0: ABORT operation timed-out.
> May 1 15:59:19 defiant kernel: sym0:5:0: DEVICE RESET operation started.
> May 1 15:59:24 defiant kernel: sym0:5:0: DEVICE RESET operation timed-out.
> May 1 15:59:24 defiant kernel: sym0:5:0: BUS RESET operation started.
> May 1 15:59:24 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 15:59:24 defiant kernel: sym0: SCSI BUS has been reset.
> May 1 15:59:24 defiant kernel: sym0:5:0: BUS RESET operation complete.
> May 1 15:59:32 defiant kernel: sym0:5: No IDENTIFY after reselection.
>
> at which point the driver locks up, dd is stuck in "D" state and rmmod
> says "device or resource busy".
> Note that the transfer mode is synchronous, even though the SYM-1 driver
> uses async mode. Just to check that possibility I used the "setsync 5 0"
> sysctl, but the results were the same.
>
> Removing FE_LDSTR I get this:
When both FE_LDSTR and FE_PFEN are removed, the driver is expected to use
the generic SCRIPTS instead of the LOAD/STORE based one. If only FE_LDSTR
is cleared, the driver should refuse to load your HBA. I will assume that
you removed both FE_LDSTR and FE_PFEN.
> May 1 16:30:53 defiant kernel: sym0:6: ERROR (81:0) (8-0-0) (0/5/0) @
> (scripta c:00000000).
> May 1 16:30:53 defiant kernel: sym0: script cmd = 00000000
> May 1 16:30:53 defiant kernel: sym0: regdump: da 00 40 05 47 00 06 0f 04 08
> 86 00 80 00 07 02 00 a0 2f 1e 02 ff ff ff.
> May 1 16:30:53 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 16:30:53 defiant kernel: sym0: SCSI BUS has been reset.
>
> May 1 16:31:09 defiant kernel: sym0:5: ERROR (81:0) (8-0-0) (f/35/0) @
> (scripta c:00000000).
> May 1 16:31:09 defiant kernel: sym0: script cmd = 00000000
> May 1 16:31:09 defiant kernel: sym0: regdump: da 00 40 35 47 0f 05 0f 04 08
> 85 00 80 00 07 02 00 a0 2f 1e 02 ff ff ff.
> May 1 16:31:09 defiant kernel: sym0: SCSI BUS reset detected.
> May 1 16:31:09 defiant kernel: sym0: SCSI BUS has been reset.
Still very strange errors.
The interrupted address reported by the chip is 0xc which points inside a
2 DWORDs SCRIPTS instruction. Normally, the SCRIPTS processor is supposed
to fetch at least 2 DWORDS and then try to decode.
> The other flags do not seem to have an effect on this problem, I even went
> all the way to just FE_DBLR|FE_VARCLK.
> I also tried using IO mapped mode instead of memory mapped, but that didn't
> help either.
>
> Do you have any more suggestions?
Nothing really great at the moment. Just, trying another sym53c8xx HBA, if
possible, with same hardware and software to really get 100% sure about
the peoblem being related to this particular HBA (or not).
Regards,
Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-05-03 0:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-30 15:13 Strange Diamond Fireport 20 (53c875J Rev4) problems Csaba Halász
2002-04-30 0:39 ` Gérard Roudier
2002-05-01 16:42 ` Csaba Halász
2002-05-03 0:08 ` Gérard Roudier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox