[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9344.0. "? Known SCSI problem with V4.0B?" by GREGOR::OPP () Tue Apr 01 1997 10:20

    	Is the SCSI configuration problem described in the attached 
    note a known problem with a known solution?  In a sentence, V4.0
    configures the second SCSI bus on a P2SE PCI adapter, whereas,
    V4.0B does not.  Thank you.
    
    Greg
    
    
            <<< RICKS::SYS$SYSDEVICE:[NOTES$LIBRARY]APC164.NOTE;1 >>>
                                -< AlphaPC164 >-
================================================================================
Note 75.0        QAR 038: UNIX V4.0B SCSI configuration problem       No replies
GREGOR::OPP                                         371 lines  31-MAR-1997 14:26
--------------------------------------------------------------------------------

     System Type:  PC164             QAR Number: 038
     Entered by:  Greg Opp           Date Entered:  31-MAR-1997
     Software: UNIX V4.0B            First Observed:  24-MAR-1997
     Firmware: SRM V4.5-15           System:  SANKA, 400 MHz, 128 MB
             ` upgraded to V4.8
     Hardware: Motherboard Rev. C01, #KA632RMPKE (partially obscured)
     Reproducible:  Yes, eminently
                                           

     Problem Summary

        Repeated efforts to update DKB0 from UNIX V4.0 to V4.0B fail.  In-
     stalling V4.0B on SCSI disk DKA0 reports errors regarding "isp1", but
     once kernel is built on DKA0, any device connected to the second SCSI
     port of the P2SE is "invisible".  If UNIX V4.0 is installed on DKA0,
     it can "see" devices on second SCSI bus.  UNIX V4.0 also successfully
     installs on DKB0, whereas V4.0B does not.  Finally, executing the com-
     mand "isp1020_edit -sd" from the console does successfully update the
     firmware (what appears to be the checksum), but the problem remains.
     While this may be a new "feature" of Digital UNIX V4.0B, from my per-
     spective, it's a bug, and and non-benign one at that. 
 

     Error Sample

        The observed errors during system initialization (booting) typically
     look something like:

        isp1: QLOGIC ISP1020A
        cam_logger: CAM_ERROR packet
        cam_logger: bus 1 
        isp_probe
        NVRAM parameters invalid, using driver Fast10 defaults
        isp1: Firmware revision 2.10 (loaded by console)
        ~    ~    ~    ~
        Common init failure - Failing probe
        isp1: Not probed.
        isp in slot 2 not configured.


     Related Problem

        While I was struggling with this installation problem on SANKA, Jay
     Lory also reported difficulty installing UNIX V4.0B on a PC164 system
     with a P1SE and Trio S3 graphics adapter installed.  After many tries,
     Jay found that if the P1SE were installed in the first 64-bit PCI slot
     and the Trio S3 graphics adapter was installed in the second slot, the
     installation succeeded.  In all other configurations tried, it failed.


     Attachments
     
        Two log files are attached.  The first shows the errors logged to 
     the screen when trying to boot V4.0B from DKB0.  The second shows that
     V4.0 correctly configures the second SCSI bus.  Additional information
     from error logs, etc. can be supplied upon request.



Attachment 1. - Console log showing attempted V4.0B failure to boot.

show config
                        Digital AlphaPC 164 400 MHz

SRM Console V4.8-1         	VMS PALcode V1.19-9, OSF PALcode V1.21-8
            ^^^^^^ installed 26-MAR-1997

SROM Revision: 2.2
DECchip (tm) 21164A-1
DECchip (tm) 21172 CIA ASIC Pass 3

MEMORY
128 Meg of system memory


PCI Bus 
     Bus 00  Slot 06: Digital TGA2 Graphics Controller
     Bus 00  Slot 07: DECchip 21050 PCI to PCI Bridge
     Bus 00  Slot 08: Intel 82378IB PCI to ISA Bridge
     Bus 00  Slot 11: CMD PCI0646 IDE Controller
                                   dqa.0.0.11.0                              
                                   dqa0.0.0.11.0          QUANTUM FIREBALL640A
     Bus 01  Slot 00: DECchip 21040 Network Controller
                                   ewa0.0.0.1000.0       00-00-F8-21-A0-D8   
     Bus 01  Slot 01: QLogic ISP1020 Scsi Controller
                                   pka0.7.0.1001.0       SCSI Bus ID 7       
                           --->    dka0.0.0.1001.0        SEAGATE ST32550W    
                                   dka400.4.0.1001.0      SONY CD-ROM CDU-76S 
     Bus 01  Slot 02: QLogic ISP1020 Scsi Controller
                                   pkb0.7.0.1002.0       SCSI Bus ID 7       
                           --->    dkb0.0.0.1002.0        SEAGATE ST31230N    

ISA
Slot	Device	Name		Type	     Enabled  BaseAddr	IRQ	DMA
0
	0	MOUSE		Embedded	Yes	60	12	
	1	KBD		Embedded	Yes	60	1	
	2	COM1		Embedded	Yes	3f8	4	
	3	COM2		Embedded	Yes	2f8	3	
	4	LPT1		Embedded	Yes	3bc	7	
	5	FLOPPY		Embedded	Yes	3f0	6	2

>>>
>>>show device
dka0.0.0.1001.0            DKA0               SEAGATE ST32550W  0016
dka400.4.0.1001.0          DKA400          SONY CD-ROM CDU-76S  1.1c
dkb0.0.0.1002.0            DKB0               SEAGATE ST31230N  0640
dqa0.0.0.11.0              DQA0           QUANTUM FIREBALL640A  A63.0E00
dva0.0.0.0.1               DVA0                               
ewa0.0.0.1000.0            EWA0              00-00-F8-21-A0-D8
pka0.7.0.1001.0            PKA0                  SCSI Bus ID 7  2.10
pkb0.7.0.1002.0            PKB0                  SCSI Bus ID 7  2.10
>>>




>>>boot dkb0
device a is ambiguous
(boot dkb0.0.0.1002.0 -flags A)
block 0 of dkb0.0.0.1002.0 is a valid boot block
reading 16 blocks from dkb0.0.0.1002.0
bootstrap code read in
base = 176000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 168000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

Digital UNIX boot - Fri Nov 15 21:24:46 EST 1996

Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x1000900010113>
Switching to OSF PALcode Succeeded
New PAL Revision <0x1000800020115>

Sizes:
text = 5279040
data = 1337936
bss  = 3398512
Starting at 0xfffffc000045efc0

Alpha boot: available memory from 0xdd2000 to 0x7f16000
Digital UNIX V4.0B  (Rev. 564); Fri Nov 15 23:52:36 EST 1996 
physical memory = 128.00 megabytes.
available memory = 113.66 megabytes.
using 482 buffers containing 3.76 megabytes of memory
Digital AlphaPC 164 400 MHz system
Firmware revision: 4.8
Digital UNIX PALcode version 1.21
Module 1095:646 not in pci option table, can't configure it
pci0 at nexus
tga0 at pci0 slot 6
tga0: depth 8, map size 2MB, 1024x768
tga0: ZLXp2-E, Revision: 34
pci1000 at pci0 slot 7
tu0: DECchip 21040-AA: Revision: 2.4
tu0 at pci1000 slot 0
tu0: DEC TULIP Ethernet Interface, hardware address: 00-00-F8-21-A0-D8
tu0: console mode: selecting 10BaseT (UTP) port: half duplex
isp0 at pci1000 slot 1
isp0: QLOGIC ISP1020A
cam_logger: CAM_ERROR packet                    <--- errors begin here
cam_logger: bus 0                               

! isp1020_edit -sd had not yet been executed.

isp_probe
NVRAM parameters invalid, using driver Fast10 defaults
isp0: Firmware revision 2.10 (loaded by console)
scsi0 at isp0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0) (SEAGATE ST32550W         0016) (Wide16)
rz4 at scsi0 target 4 lun 0 (LID=1) (SONY    CD-ROM CDU-76S   1.1c)
isp1 at pci1000 slot 2
isp1: QLOGIC ISP1020A
cam_logger: CAM_ERROR packet
cam_logger: bus 1 
isp_probe
NVRAM parameters invalid, using driver Fast10 defaults
isp1: Firmware revision 2.10 (loaded by console)
cam_logger: CAM_ERROR packet
cam_logger: bus 1 
isp_get_console_image
Unable to map console firmware into a contiguous block
cam_logger: CAM_ERROR packet
cam_logger: bus 1 
isp_init
Unable to read back firmware from chip
cam_logger: CAM_ERROR packet
cam_logger: bus 1 
isp_probe
Common init failure - Failing probe
isp1: Not probed.
isp in slot 2 not configured.
isa0 at pci0
gpc0 at isa0
ace0 at isa0
ace1 at isa0
lp0 at isa0
fdi0 at isa0
fd0 at fdi0 unit 0
lvm0: configured.
lvm1: configured.
lvm2: configured.
kernel console: ace0
bootdevice_parser: unknown protocol name 'SCSI'
setconf: Bootdevice parser failed to translate bootdevice SCSI 0 1002 0 0 0 0 0.
panic (cpu 0): setconf: bootdevice_parser failed

DUMP: No primary swap, no explicit dumpdev.
      Nowhere to put header, giving up.

! System fails to boot UNIX V4.0B from DKB0

CP - SAVE_TERM routine to be called
CP - SAVE_TERM exited with hlt_req = 1, r0 = 00000000.00000000

halted CPU 0

halt code = 5
HALT instruction executed
PC = fffffc0000460a30
>>>



Attachment 2. - Console log showing V4.0 successfully recognizing DKB0 (rz8).

>>>#
>>># back to original configuration.
>>># Boot DKA400 and install V4.0 to DKB0, rz8
>>>
>>>boot dka400
(boot dka400.4.0.1001.0)
block 0 of dka400.4.0.1001.0 is a valid boot block
reading 16 blocks from dka400.4.0.1001.0
bootstrap code read in
base = 176000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 168000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

Digital UNIX boot - Sun May 19 23:29:33 EDT 1996

Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x1000900010113>
Switching to OSF PALcode Succeeded
New PAL Revision <0x1000800020115>

Sizes:
text = 4461104
data = 1133872
bss  = 2476448
Starting at 0xfffffc0000402e10

Alpha boot: available memory from 0xc18000 to 0x7f16000
Digital UNIX V4.0 (Rev. 386); Mon May 20 04:41:58 EDT 1996 
physical memory = 128.00 megabytes.
available memory = 115.34 megabytes.
using 160 buffers containing 1.25 megabytes of memory
Digital AlphaPC 164 400 MHz system
Firmware revision: 4.8
Digital UNIX PALcode version 0.00
Module 1095:646 not in pci option table, can't configure it
pci0 at nexus
tga0 at pci0 slot 6
tga0: depth 8, map size 2MB, 1024x768
tga0: ZLXp2-E, Revision: 34
pci1000 at pci0 slot 7
tu0: DECchip 21040-AA: Revision: 2.4
tu0 at pci1000 slot 0
tu0: DEC TULIP Ethernet Interface, hardware address: 00-00-F8-21-A0-D8
tu0: console mode: selecting UTP (10BaseT) port
isp0 at pci1000 slot 1
isp0: QLOGIC ISP1020A
isp0: INFO: NVRAM parameters invalid, using driver defaults
isp0: Firmware revision 2.10 (loaded by console)
isp0: StorageWorks signal reporting enabled
isp0: StorageWorks SHELF_OK signal transition reported
scsi0 at isp0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0) (SEAGATE ST32550W         0016) (Wide16)
rz4 at scsi0 target 4 lun 0 (LID=1) (SONY    CD-ROM CDU-76S   1.1c)
isp1 at pci1000 slot 2
isp1: QLOGIC ISP1020A
isp1: INFO: NVRAM parameters invalid, using driver defaults
isp1: Firmware revision 2.10 (loaded by console)
isp1: StorageWorks signal reporting enabled
isp1: StorageWorks SHELF_OK signal transition reported
scsi1 at isp1 slot 0
rz8 at scsi1 target 0 lun 0 (LID=2) (SEAGATE ST31230N         0640)

! Notice that V4.0 has correctly configured the second SCSI bus, isp1.

isa0 at pci0
gpc0 at isa0
ace0 at isa0
kernel console: ace0
vm_swap_init: warning /sbin/swapdefault swap device not found
vm_swap_init: swap is set to lazy (over commitment) mode

INIT: SINGLE-USER MODE


Initializing system for Digital UNIX installation.  Please wait...


*** Performing CDROM Installation

Loading installation process and scanning system hardware.

       Welcome to the Digital UNIX Installation Procedure

This procedure installs Digital UNIX onto your system.  You will
be asked a series of system configuration questions.  Until you
answer all questions, your system is not changed in any way.

During the question and answer session, you can go back to any
previous question and change your answer by entering:  history
You can get more information about a question by entering:  help

There are two types of installations:

o  The Default Installation installs a mandatory set of
   software subsets on a predetermined file system layout.

o  The Custom Installation installs a mandatory set of
   software subsets plus optional software subsets that you
   select.  You can customize the file system layout.

The UNIX Shell option puts your system in single-user mode with
superuser privileges.  This option is provided for experienced
UNIX system administrators who want to perform file system or
<Press RETURN for more>: 
disk maintenance tasks before the installation.

The Installation Guide contains more information about installing
Digital UNIX.

1) Default Installation
2) Custom Installation
3) UNIX Shell

Enter your choice: 2


Choose a hostname for this system.  The hostname identifies the
system on the network.  The hostname must start with a letter,
and may include letters, numbers, periods and hyphens.

Enter the hostname for this system: SANKA

[ intervening UNIX installation messages deleted.]

Continuing installation...

 *** Creating the root file system on device rz8a ***


 *** Creating the usr file system on device rz8g ***


 *** Creating the swap1 file system on device rz8b ***


 *** Loading the operating system software subsets ***
T.RTitleUserPersonal
Name
DateLines