[3642] in linux-scsi channel archive
Re: BusLogic FlashPoint 930, driver 2.0.11 and SMP
daemon@ATHENA.MIT.EDU (Larry M. Augustin)
Tue Apr 7 15:22:45 1998
Date: Tue, 7 Apr 1998 12:00:20 -0700
From: "Larry M. Augustin" <lma@varesearch.com>
To: Michael Bravo <mbravo@kronverk.spb.su>
Cc: "Leonard N. Zubkoff" <lnz@dandelion.com>, linux-scsi@vger.rutgers.edu
In-Reply-To: <87iuovi5hp.fsf@spider.kronverk.spb.ru>
I'm sure there is an SMP problem in 2.0.33. I know that it's not
Buslogic specific because the problems exist on systems without
Buslogic cards. I am still occasionally seeing "black screen" hangs,
and "scheduling in interrupt" errors.
I don't have the time to track these down, but am willing to run some
tests for people or provide remote hardware access. I'll loan Leonard
a system if that will help.
Larry
Michael Bravo writes:
> >>>>> "Leonard" == Leonard N Zubkoff writes:
>
> Leonard> I have three FlashPoint LW's in my dual Pentium Pro 200 with file
> Leonard> systems striped across the controllers. I have had no SMP related
> Leonard> crashes since one of my earlier deadlock patches last summer. I
> Leonard> do not believe there is any code in the SCCB Manager which can
> Leonard> lead to an interrupt deadlock in 2.0.
>
> I'm able to consistently reproduce the lockups, and currently run on
> non-SMP kernel because of them. Would you like any aspect of my
> configuration in detail? It is completely the same except the SMP-ness of
> kernel.
>
> Here're some for starters:
>
> mbravo@spider mbravo$ cat /proc/version
> Linux version 2.0.33 (root@spider) (gcc version 2.7.2.1) #6 Fri Mar 27 16:30:46 MSK 1998
>
> mbravo@spider mbravo$ cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: SONY Model: SDT-2000 Rev: 2.08
> Type: Sequential-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 03 Lun: 00
> Vendor: PIONEER Model: CD-ROM DR-U12X Rev: 1.06
> Type: CD-ROM ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: IBM Model: DCAS-34330 Rev: S65A
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
> Vendor: IBM Model: DCAS-34330 Rev: S65A
> Type: Direct-Access ANSI SCSI revision: 02
> Host: scsi1 Channel: 00 Id: 01 Lun: 00
> Vendor: YAMAHA Model: CDR400t Rev: 1.0j
> Type: CD-ROM ANSI SCSI revision: 02
>
> mbravo@spider mbravo$ cat /proc/scsi/BusLogic/0
> ***** BusLogic SCSI Driver Version 2.0.11 of 31 January 1998 *****
> Copyright 1995 by Leonard N. Zubkoff <lnz@dandelion.com>
> Configuring BusLogic Model BT-930 PCI Ultra SCSI Host Adapter
> Firmware Version: 5.02, I/O Address: 0x6100, IRQ Channel: 5/Level
> PCI Bus: 0, Device: 17, Address: 0xE4000000, Host Adapter SCSI ID: 7
> Parity Checking: Enabled, Extended Translation: Enabled
> Synchronous Negotiation: FSFFFUU#, Wide Negotiation: Disabled
> Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
> Driver Queue Depth: 255, Scatter/Gather Limit: 128 segments
> Tagged Queue Depth: Automatic, Untagged Queue Depth: 1
> Error Recovery Strategy: Default, SCSI Bus Reset: Enabled
> SCSI Bus Termination: Enabled, SCAM: Disabled
> *** BusLogic BT-930 Initialized Successfully ***
>
> Target 1: Queue Depth 1, Synchronous at 5.00 MB/sec, offset 7
> Target 3: Queue Depth 1, Synchronous at 10.0 MB/sec, offset 15
> Target 5: Queue Depth 28, Synchronous at 20.0 MB/sec, offset 15
> Target 6: Queue Depth 28, Synchronous at 20.0 MB/sec, offset 15
>
> Current Driver Queue Depth: 255
> Currently Allocated CCBs: 63
>
>
> DATA TRANSFER STATISTICS
>
> Target Tagged Queuing Queue Depth Active Attempted Completed
> ====== ============== =========== ====== ========= =========
> 1 Not Supported 1 0 54325 54325
> 3 Not Supported 1 0 46824 46824
> 5 Active 28 0 115235 115235
> 6 Active 28 0 110257 110257
>
> Target Read Commands Write Commands Total Bytes Read Total Bytes Written
> ====== ============= ============== =================== ===================
> 1 27154 27153 889782272 889733120
> 3 46452 0 725643264 0
> 5 79195 36034 1245421568 1065181184
> 6 76662 33589 1230842880 1034665984
>
> Target Command 0-1KB 1-2KB 2-4KB 4-8KB 8-16KB
> ====== ======= ========= ========= ========= ========= =========
> 1 Read 0 0 0 0 0
> 1 Write 0 0 0 0 0
> 3 Read 0 0 500 25 3415
> 3 Write 0 0 0 0 0
> 5 Read 0 4 0 34987 10925
> 5 Write 0 0 0 16864 6743
> 6 Read 0 3 0 31733 12766
> 6 Write 0 0 0 15510 3661
>
> Target Command 16-32KB 32-64KB 64-128KB 128-256KB 256KB+
> ====== ======= ========= ========= ========= ========= =========
> 1 Read 0 27154 0 0 0
> 1 Write 1 27152 0 0 0
> 3 Read 42512 0 0 0 0
> 3 Write 0 0 0 0 0
> 5 Read 13613 19665 1 0 0
> 5 Write 1885 4394 6148 0 0
> 6 Read 12652 19508 0 0 0
> 6 Write 4574 3940 5904 0 0
>
>
> ERROR RECOVERY STATISTICS
>
> Command Aborts Bus Device Resets Host Adapter Resets
> Target Requested Completed Requested Completed Requested Completed
> ID \\\\ Attempted //// \\\\ Attempted //// \\\\ Attempted ////
> ====== ===== ===== ===== ===== ===== ===== ===== ===== =====
> 1 0 0 0 0 0 0 0 0 0
> 3 0 0 0 0 0 0 0 0 0
> 5 0 0 0 0 0 0 0 0 0
> 6 0 0 0 0 0 0 0 0 0
>
> External Host Adapter Resets: 0
> Host Adapter Internal Errors: 0
>
>
>
> It might be significant that all lockups seem to coincide with SCSI CD-ROM
> or tape activity; that is, it is perfectly possible that if I had none of
> these devices but only harddrives, there would be no lockups.
>
>
> /\/\ike
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
