Conference turris::digital_unix

9566.0. "SCSI problem with Scanner, V3.2D and V4.0B" by ALFAM7::STREPPEL () Mon Apr 21 1997 13:09

    A customer is reporting the following problem with a - yes I know -
    unsupported scanner that is connected via SCSI to Digital UNIX. It used
    to work without any problems on an AlphaStation 200 and DU 3.2D and
    does not work any more - i.e. finally panics the system due to severe
    SCSI problems - on an AS 255 with DU 4.0B. Maybe someone can tell us
    what's wrong in the SCSI part and why the behaviour has changed between 
    the DU releases.I understand why the OS panics; it's only the SCSI 
    messages that are of interest here:
    
    Apr  9 15:04:48 wrzx77 vmunix: Alpha boot: available memory from
    0x88a000 to 0x7ffe000
    Apr  9 15:04:48 wrzx77 vmunix: Digital UNIX V4.0B  (Rev. 564); Wed Apr 
    9 15:00:38 MET DST 1997 
    Apr  9 15:04:48 wrzx77 vmunix: physical memory = 128.00 megabytes.
    Apr  9 15:04:48 wrzx77 vmunix: available memory = 119.47 megabytes.
    Apr  9 15:04:48 wrzx77 vmunix: using 484 buffers containing 3.78
    megabytes of memory
    Apr  9 15:04:48 wrzx77 vmunix: AlphaStation 255/233 system
    Apr  9 15:04:49 wrzx77 vmunix: DECchip 21071 
    Apr  9 15:04:49 wrzx77 vmunix: 82378IB (SIO) PCI/ISA Bridge 
    Apr  9 15:04:49 wrzx77 vmunix: Firmware revision: 6.3
    Apr  9 15:04:49 wrzx77 vmunix: PALcode: OSF version 1.46
    Apr  9 15:04:49 wrzx77 vmunix: pci0 at nexus
    Apr  9 15:04:49 wrzx77 vmunix: psiop0 at pci0 slot 6
    Apr  9 15:04:49 wrzx77 vmunix: Loading SIOP: script 800900, reg
    82080000, data 405d68a0
    !> Apr  9 15:04:49 wrzx77 vmunix: SIOP 0 ILLEGAL INSTRUCTION:[0/t/l]
    siop_printop: PC = 0xe14 (0x801714) - 0x0 0x48000000 0x0
    !> Apr  9 15:04:49 wrzx77 vmunix: cam_logger: CAM_ERROR packet
    !> Apr  9 15:04:49 wrzx77 vmunix: cam_logger: bus 0 target 5 lun 1 
    !> Apr  9 15:04:49 wrzx77 vmunix: psiop_hardintr
    !> Apr  9 15:04:49 wrzx77 vmunix: psiop_hardintr: illegal instruction
    Apr  9 15:04:49 wrzx77 vmunix: Loading SIOP: script 800900, reg
    82080000, data 405d68a0
    Apr  9 15:04:49 wrzx77 vmunix: scsi0 at psiop0 slot 0
    Apr  9 15:04:49 wrzx77 vmunix: rz0 at scsi0 target 0 lun 0 (LID=0) (DEC    
    RZ29B    (C) DEC 0014)
    Apr  9 15:04:49 wrzx77 vmunix: rz4 at scsi0 target 4 lun 0 (LID=1) (DEC    
    RRD45   (C) DEC  0436)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 0 (LID=2)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 2 (LID=3)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 3 (LID=4)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 4 (LID=5)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 5 (LID=6)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 6 (LID=7)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: scanner at scsi0 target 5 lun 7 (LID=8)
    (SHARP   JX610 SCSI       101J)
    Apr  9 15:04:49 wrzx77 vmunix: isa0 at pci0
    ...
    Apr  9 15:04:49 wrzx77 vmunix: ADVFS: using 1152 buffers containing
    9.00 megabytes of memory
    Apr 10 11:05:05 wrzx77 vmunix: cam_logger: CAM_ERROR packet
    Apr 10 11:05:05 wrzx77 vmunix: cam_logger: bus 0 target 5 lun 0 
    Apr 10 11:05:05 wrzx77 vmunix: ss_abort_done
    Apr 10 11:05:05 wrzx77 vmunix: SCSI abort has been performed
    Apr 10 11:05:06 wrzx77 vmunix: cam_logger: CAM_ERROR packet
    Apr 10 11:05:06 wrzx77 vmunix: cam_logger: bus 0 target 0 lun 0 
    Apr 10 11:05:06 wrzx77 vmunix: cdisk_cleanup_rec_err
    Apr 10 11:05:06 wrzx77 vmunix: Recovery failed
    Apr 10 11:05:06 wrzx77 vmunix: Hard Error Detected
    Apr 10 11:05:06 wrzx77 vmunix: DEC     RZ29B    (C) DEC^ORZ29B
    Apr 10 11:05:06 wrzx77 vmunix: AdvFS I/O error:
    Apr 10 11:05:06 wrzx77 vmunix:     Volume: /dev/rz0g
    Apr 10 11:05:06 wrzx77 vmunix:     Tag: 0xfffffff7.0000
    Apr 10 11:05:06 wrzx77 vmunix:     Page: 321
    Apr 10 11:05:06 wrzx77 vmunix:     Block: 6208
    Apr 10 11:05:06 wrzx77 vmunix:     Block count: 64
    Apr 10 11:05:06 wrzx77 vmunix:     Type of operation: Write
    Apr 10 11:05:06 wrzx77 vmunix:     Error: 5
    Apr 10 11:05:06 wrzx77 vmunix: 
    Apr 10 11:05:06 wrzx77 vmunix: bs_osf_complete: metadata write failed
    Apr 10 11:05:06 wrzx77 vmunix: AdvFS Domain Panic; Domain usr_domain Id
    0x3338e4fc.00025690
    
    	Regards
    		Hartmut
       

I think you may have a SCSI ID conflict.
Get to a console prompt. Remove the Scanner and show dev check that the ID
that
you scanner is on is not already used.

	Cheers
		Mark :)
[Posted by WWW Notes gateway]