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

Conference wrksys::alphastation

Title:Alpha Workstation Conference
Notice:See note 1.* for conference notices
Moderator:WRKSYS::HOUSE
Created:Wed Sep 07 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1996
Total number of notes:9122

1857.0. "reboot hangs on AS255/233" by UTOPIE::OETTL (hide bug until worst time) Fri Feb 14 1997 18:50

I have 10 Alphastation255/233 installed at a customer site and three of them
are having problems when being rebooted.
The problem does appear at random, but always occurs after LOADING SIOP: is 
printed to the console. The messages differ; a sample one is below.

When this happens, the system is crashing (but cannot write a dump) and 
rebooting until it is power-cycled. Then the boot is always ok. The printout
below is an exception, the boot continued...

I did set BOOT_RESET to on and for two days the problem disappeared.

Any suggestions?

�tzi

-------------------------------------------------------------------------------

ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.....ea.e9.e8.e7.e6.e5.
V6.3-4, built on Nov 20 1996 at 09:41:23

CPU 0 booting

(boot dka0.0.0.6.0 -flags a)
block 0 of dka0.0.0.6.0 is a valid boot block
reading 32 blocks from dka0.0.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 4000
initializing HWRPB at 2000
initializing page table at 1e4000
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 <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>

Sizes:
text = 3397056
data = 510176
bss  = 825440
Starting at 0xfffffc000045a270

Alpha boot: available memory from 0x8d6000 to 0x7ffe000
Digital UNIX V4.0B  (Rev. 564); Mon Jan 27 09:45:56 MET 1997 
physical memory = 128.00 megabytes.
available memory = 119.17 megabytes.
using 484 buffers containing 3.78 megabytes of memory
AlphaStation 255/233 system
DECchip 21071 
82378IB (SIO) PCI/ISA Bridge 
Firmware revision: 6.3
PALcode: OSF version 1.46
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 800200, reg 82018000, data 4060c160
scsi0 at psiop0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0) (DEC     RZ28D    (C) DEC 0010)
rz4 at scsi0 target 4 lun 0 (LID=1) (DEC     RRD45   (C) DEC  0436)
isa0 at pci0
gpc0 at isa0
ace0 at isa0
ace1 at isa0
lp0 at isa0
fdi0 at isa0
fta0 DEC DEFPA FDDI Module, Hardware Revision 0
fta0 at pci0 slot 12
fta0: DMA Available.
fta0: DEC DEFPA (PDQ) FDDI Interface, Hardware address: 00-00-F8-4A-81-85
fta0: Firmware rev: 2.46
tga0 at pci0 slot 13
tga0: depth 32, map size 16MB, 1280x1024
tga0: ZLXp2-E, Revision: 34
tu0: DECchip 21040-AA: Revision: 2.4
tu0 at pci0 slot 14
tu0: DEC TULIP Ethernet Interface, hardware address: 00-00-F8-22-D1-C2
tu0: console mode: selecting 10BaseT (UTP) port: half duplex: no link
kernel console: ace0
dli: configured
ADVFS: using 1152 buffers containing 9.00 megabytes of memory
Checking local filesystems
/sbin/ufs_fsck -p
Mounting / (root)
user_cfg_pt: reconfigured
Mounting local filesystems
exec: /sbin/mount_advfs -F 81920 root_domain#root /
root_domain#root on / type advfs (rw)
/proc on /proc type procfs (rw)
exec: /sbin/mount_advfs -F 16384 usr_domain#usr /usr
usr_domain#usr on /usr type advfs (rw)
Feb 11 12:31:16 update: started

The system is coming up. Please wait...
Checking for crash dumps
Initializing paging space
Mounting Memory filesystems
Streams autopushes configured
Configuring network
hostname: tkap7.lvak.bmlv.gv.at
fta0: Link Unavailable.
Loading LMF licenses
fta0: Link Available.
System error logger started
Binary error logger started
Setting kernel timezone variable
ONC portmap service started
NFS IO service started
Mounting NFS filesystems
Preserving editor files
security configuration set to default (BASE).
Successful SIA initialization

Clearing temporary files
Unlocking ptys
3 aliases, longest (MAILER-DAEMON) 19 bytes, 53 bytes total
SMTP Mail Service started
Extensible SNMP master agent started
Base O/S sub-agent started
Using snmp service entry port 161.
Internet services provided.
Cron service started
SuperLAT. Copyright 1994 Meridian Technology Corp. All rights reserved.
LAT started.
LSM vold not started
Printer service started
The system is ready.






Digital UNIX Version V4.0 (tkap7.lvak.bmlv.gv.at) console




login: 



*****************************************************************************

*

* Starting Desktop Login on display :0...

*

* Wait for the Desktop Login screen before logging in.

*

*****************************************************************************








Digital UNIX Version V4.0 (tkap7.lvak.bmlv.gv.at) console




login: root

Password:
Last login: Tue Feb 11 12:27:42 on :0

Digital UNIX V4.0B  (Rev. 564); Mon Jan 27 09:45:56 MET 1997 

The installation software has successfully installed your system.


There are logfiles that contain a record of your installation.
These are:

        /var/adm/smlogs/install.cdf     - configuration description file
        /var/adm/smlogs/install.log     - general log file
        /var/adm/smlogs/install.FS.log  - file system creation logs
        /var/adm/smlogs/setld.log       - log for the setld(8) utility
        /var/adm/smlogs/fverify.log     - verification log file


# shutdown -h now
Shutdown at 12:32 (in 0 minutes) [pid 481]





        *** FINAL System shutdown message from [email protected] ***


System going down IMMEDIATELY


        ...



System shutdown time has arrived
# syncing disks... done
CPU 0: Halting... (transferring to monitor)


halted CPU 0

halt code = 5
HALT instruction executed
PC = fffffc000045bce0
>>>b
(boot dka0.0.0.6.0 -flags a)
block 0 of dka0.0.0.6.0 is a valid boot block
reading 32 blocks from dka0.0.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 4000
initializing HWRPB at 2000
initializing page table at 1e4000
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 <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>

Sizes:
text = 3397056
data = 510176
bss  = 825440
Starting at 0xfffffc000045a270

Alpha boot: available memory from 0x8d6000 to 0x7ffe000
Digital UNIX V4.0B  (Rev. 564); Mon Jan 27 09:45:56 MET 1997 
physical memory = 128.00 megabytes.
available memory = 119.17 megabytes.
using 484 buffers containing 3.78 megabytes of memory
AlphaStation 255/233 system
DECchip 21071 
82378IB (SIO) PCI/ISA Bridge 
Firmware revision: 6.3
PALcode: OSF version 1.46
pci0 at nexus
psiop0 at pci0 slot 6
Loading SIOP: script 800200, reg 82018000, data 4060c160
cam_logger: CAM_ERROR packet
cam_logger: No associated bus target lun
psiop_intr
siopintr: interrupt for non-initialized controller
cam_logger: CAM_ERROR packet
cam_logger: No associated bus target lun
->
->    repeated ca. 75 times
->
->
psiop_intr
siopintr: interrupt for non-initialized controller
scsi0 at psiop0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0) (DEC     RZ28D    (C) DEC 0010)
rz4 at scsi0 target 4 lun 0 (LID=1) (DEC     RRD45   (C) DEC  0436)
isa0 at pci0
gpc0 at isa0
ace0 at isa0
ace1 at isa0
lp0 at isa0
fdi0 at isa0
fta0 DEC DEFPA FDDI Module, Hardware Revision 0
fta0 at pci0 slot 12
fta0: DMA Available.
fta0: DEC DEFPA (PDQ) FDDI Interface, Hardware address: 00-00-F8-4A-81-85
fta0: Firmware rev: 2.46
tga0 at pci0 slot 13
tga0: depth 32, map size 16MB, 1280x1024
tga0: ZLXp2-E, Revision: 34
tu0: DECchip 21040-AA: Revision: 2.4
tu0 at pci0 slot 14
tu0: DEC TULIP Ethernet Interface, hardware address: 00-00-F8-22-D1-C2
tu0: console mode: selecting 10BaseT (UTP) port: half duplex: no link
kernel console: ace0
dli: configured
ADVFS: using 1152 buffers containing 9.00 megabytes of memory
Checking local filesystems
/sbin/ufs_fsck -p
Mounting / (root)
user_cfg_pt: reconfigured
Mounting local filesystems
exec: /sbin/mount_advfs -F 81920 root_domain#root /
root_domain#root on / type advfs (rw)
/proc on /proc type procfs (rw)
exec: /sbin/mount_advfs -F 16384 usr_domain#usr /usr
usr_domain#usr on /usr type advfs (rw)
Feb 11 12:33:59 update: started

The system is coming up. Please wait...
Checking for crash dumps
Initializing paging space
Mounting Memory filesystems
Streams autopushes configured
Configuring network
hostname: tkap7.lvak.bmlv.gv.at
fta0: Link Unavailable.
Loading LMF licenses
fta0: Link Available.
System error logger started
Binary error logger started
Setting kernel timezone variable
ONC portmap service started
NFS IO service started
Mounting NFS filesystems
Preserving editor files
security configuration set to default (BASE).
Successful SIA initialization

Clearing temporary files
Unlocking ptys
3 aliases, longest (MAILER-DAEMON) 19 bytes, 53 bytes total
SMTP Mail Service started
Extensible SNMP master agent started
Base O/S sub-agent started
Using snmp service entry port 161.
Internet services provided.
Cron service started
SuperLAT. Copyright 1994 Meridian Technology Corp. All rights reserved.
LAT started.
LSM vold not started
Printer service started
The system is ready.






Digital UNIX Version V4.0 (tkap7.lvak.bmlv.gv.at) console




login: 

T.RTitleUserPersonal
Name
DateLines
1857.1UTOPIE::OETTLhide bug until worst timeFri Feb 21 1997 14:229
Next step will be a firmware upgrade to V7_5.

Still my question: Has anybody else seen this?
Could it possibly be a bug in Digital Unix V4.0B?

thanks in advance,

�tzi
1857.2solved nowUTOPIE::OETTLhide bug until worst timeThu Apr 24 1997 13:155
Firmware upgrade did not solve the problem.

We got a new cam_psiop.mod via an IPMT and it seems to have solved this problem.

�tzi
1857.3IPMT??TLAV02::KAMOLCHANOKFri Apr 25 1997 05:067
    Hello, 
    
    	What's the IPMT? How to get that? How to fix that?
    
    Thanks,
    dear
    
1857.4STAR::KLEINSORGEFred Kleinsorge, OpenVMS EngineeringFri Apr 25 1997 10:495
    An IPMT is a bug report generated by a customer problem.  Usually this
    end in the generation of a TIMA kit.  As an intermediate step, many
    times the corrected image is available online from a CSC site.