symbios i kernel 2.2.20

Marcin Bohosiewicz marcus w kernel.pl
Śro, 27 Lut 2002, 19:33:13 CET 

On Wed, 27 Feb 2002, Blues wrote:

> Wziąłem się dzisiaj za update jednej zapomnianej maszyny z naszego
> kernelka 2.2.19-26 przy okazji zaniku dłuuuuugiego prądu. Jest on
> wyposażony w kontroler Tekram'a. Na tym jajku zgłasza się on następująco:
> 
> sym53c8xx: at PCI bus 0, device 9, function 1
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: 53c1010-33 detected with Symbios NVRAM
> sym53c8xx: at PCI bus 0, device 9, function 0
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: 53c1010-33 detected with Symbios NVRAM
> sym53c1010-33-0: rev 0x1 on pci bus 0 device 9 function 1 irq 10
> sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
> sym53c1010-33-0: on-chip RAM at 0xebfec000
> sym53c1010-33-0: restart (scsi reset).
> sym53c1010-33-0: handling phase mismatch from SCRIPTS.
> sym53c1010-33-0: Downloading SCSI SCRIPTS.
> sym53c1010-33-1: rev 0x1 on pci bus 0 device 9 function 0 irq 10
> sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
> sym53c1010-33-1: on-chip RAM at 0xebfea000
> sym53c1010-33-1: restart (scsi reset).
> sym53c1010-33-1: handling phase mismatch from SCRIPTS.
> sym53c1010-33-1: Downloading SCSI SCRIPTS.
> scsi0 : sym53c8xx-1.7.3c-20010512
> scsi1 : sym53c8xx-1.7.3c-20010512
> scsi : 2 hosts.
>   Vendor: QUANTUM   Model: FIREBALL_TM3200S  Rev: 300X
>   Type:   Direct-Access                      ANSI SCSI revision: 02
>   Vendor: QUANTUM   Model: FIREBALL ST3.2S   Rev: 0F0C
>   Type:   Direct-Access                      ANSI SCSI revision: 02
>   Vendor: IBM       Model: DDYS-T18350N      Rev: S93E
>   Type:   Direct-Access                      ANSI SCSI revision: 03
> Detected scsi disk sda at scsi0, channel 0, id 5, lun 0
> Detected scsi disk sdb at scsi0, channel 0, id 6, lun 0
> Detected scsi disk sdc at scsi1, channel 0, id 5, lun 0
> sym53c1010-33-0-<5,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 15)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 6281856 [3067 MB] [3.1 GB] sda: sda1
> sym53c1010-33-0-<6,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 15)
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 6328861 [3090 MB] [3.1 GB] sdb: sdb1 sdb2
> sym53c1010-33-1-<5,*>: FAST-80 WIDE SCSI 160.0 MB/s (12.5 ns, offset 62)
> SCSI device sdc: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB] sdc: sdc1 sdc2 sdc3

Mozesz na 2.2.19-26 sprawdzic wartosc parametru "tagged command queue" ?
Cos mi sie kolacze, ze wtedy wynosil 8.
Tak samo w BIOSie kontrolera zobacz czy jest cos o tej opcji.

> 
> 
> Wszystko działa jak należy, bez żadnych zgrzytów
> 
> 
> Natomiast na naszym jajku 2.2.20-12 wygląda to tak:
> 
> sym53c8xx: at PCI bus 0, device 9, function 1
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: 53c1010-33 detected with Symbios NVRAM
> sym53c8xx: at PCI bus 0, device 9, function 0
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: 53c1010-33 detected with Symbios NVRAM
> sym53c1010-33-0: rev 0x1 on pci bus 0 device 9 function 1 irq 10
> sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
> sym53c1010-33-0: on-chip RAM at 0xebfec000
> sym53c1010-33-0: restart (scsi reset).
> sym53c1010-33-0: handling phase mismatch from SCRIPTS.
> sym53c1010-33-0: Downloading SCSI SCRIPTS.
> sym53c1010-33-1: rev 0x1 on pci bus 0 device 9 function 0 irq 10
> sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
> sym53c1010-33-1: on-chip RAM at 0xebfea000
> sym53c1010-33-1: restart (scsi reset).
> sym53c1010-33-1: handling phase mismatch from SCRIPTS.
> sym53c1010-33-1: Downloading SCSI SCRIPTS.
> scsi0 : sym53c8xx-1.7.3c-20010512
> scsi1 : sym53c8xx-1.7.3c-20010512
> scsi : 2 hosts.
>    Vendor: QUANTUM   Model: FIREBALL_TM3200S  Rev: 300X
>    Type:   Direct-Access                      ANSI SCSI revision: 02
>    Vendor: QUANTUM   Model: FIREBALL ST3.2S   Rev: 0F0C
>    Type:   Direct-Access                      ANSI SCSI revision: 02
> sym53c1010-33-0-<5,0>: tagged command queue depth set to 16
> sym53c1010-33-0-<6,0>: tagged command queue depth set to 16
>    Vendor: IBM       Model: DDYS-T18350N      Rev: S93E
>    Type:   Direct-Access                      ANSI SCSI revision: 03
> sym53c1010-33-1-<5,0>: tagged command queue depth set to 16
> Detected scsi disk sda at scsi0, channel 0, id 5, lun 0
> Detected scsi disk sdb at scsi0, channel 0, id 6, lun 0
> Detected scsi disk sdc at scsi1, channel 0, id 5, lun 0
> sym53c1010-33-0-<5,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 15)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 6281856 [3067 MB] [3.1 GB]
>  sda: sda1
> sym53c1010-33-0-<6,*>: FAST-20 SCSI 20.0 MB/s (50.0 ns, offset 15)
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 6328861 [3090 MB] [3.1 GB]
>  sdb: sdb1 sdb2
> sym53c1010-33-1-<5,*>: FAST-80 WIDE SCSI 160.0 MB/s (12.5 ns, offset 62)
> SCSI device sdc: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB]
>  sdc: sdc1 sdc2 sdc3
> 
> 
> Niby wygląda ok, prawda? Ale tak nie jest.
> 
> Przy pierszych operacjach na dysku dostaję:
> 
> sym53c1010-33-0-<5,0>: tagged command queue depth set to 16
> sym53c1010-33-0-<5,0>: QUEUE FULL! 16 busy, 15 disconnected CCBs
> sym53c1010-33-0-<5,0>: tagged command queue depth set to 15
> sym53c1010-33-0-<5,0>: tagged command queue depth set to 16
Czyli wyglada ze sie nie miesci.
Jest readme do sterownika 53c8xx, ktore opisuje:
8. Control commands

Control commands can be sent to the driver with write operations to
the proc SCSI file system. The generic command syntax is the
following:

      echo "<verb> <parameters>" >/proc/scsi/sym53c8xx/0
      (assumes controller number is 0)

Using "all" for "<target>" parameter with the commands below will
apply to all targets of the SCSI chain (except the controller).

Available commands:
[..]
8.3 Set maximum number of concurrent tagged commands

    settags <target> <tags>

    target:    target number
    tags:      number of concurrent tagged commands
               must not be greater than SCSI_NCR_MAX_TAGS (default: 8)

8.4 Set order type for tagged command

    setorder <order>

    order:     3 possible values:
               simple: use SIMPLE TAG for all operations (read and write)
               ordered: use ORDERED TAG for all operations
               default: use default tag type,
                        SIMPLE  TAG for read  operations
                        ORDERED TAG for write operations

Testowales?

M.

-- 
-| == Marcin Bohosiewicz - MB8042-RIPE - marcus w kernel.pl	== |-
-| == tel. +48 601 485097 - PLD Team   - marcus w pld.org.pl      == |-
-| == http://www.kernel.pl/ -          ftp://ftp.kernel.pl/     == |-
-| == PLUG - Sad Kolezenski  -         http://www.linux.org.pl/ == |-

Więcej informacji o liście dyskusyjnej pld-kernel