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

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

353.0. "Page read error when trying to bring up DECWindows" by GEORGI::CRAWFORD () Wed Mar 08 1989 09:36

    Yesterday, I installed Decwindows (DECW051) on a vms 5.1 system
    running VWS.  The first installation attempt failed.  I tried again,
    and received no notification that the installation had any problems.
    
    I shutdown the system.  Then did b/1 and set the window system to
    1.
    
    The system booted on up with apparently no problems...it did an
    autogen to reset the parameters and rebooted itself.
    
    The system came up and created the process to start decwindows,
    but it gives this error message:
    
     Page read error, reason mask=00, virtual address=000E7E60,
    pc=00061c57, psl=03c00000
    
    Decwindows will never start after this.  I can log into the system
    through the opcom window.  If I try to start decwindows manually,
    I get the same error.
    
    Does anyone know what may have caused this.  Can it be recovered.
    
    Would reinstallation of Decwindows work.
    
    Thanks for any info.
    
    Pam

T.R	Title	User	Personal Name	Date	Lines
353.1	Some ideas	RWCVAX::COULSON	Roger Coulson DTN 223-6158	`Wed Mar 08 1989 10:35`	12
	RE:.0 I would check the installation guide and the release notes to see if some system parameter is not set correctly. In particular have you checked to see if you have enough global pages and sections left before you start DECwindows? Are your process quotas correct? In particular do you have enough pagefilequota? Do you have anything in MODPARAMS.DAT which would effect DECwindows operation? /s/ Roger
353.2	thanks for reply...but	GEORGI::CRAWFORD		`Wed Mar 08 1989 11:56`	66
	I checked the things you suggested and can find nothing that seems out of kilter. However, I'm not too well oriented with decwindows yet. Does anything look amiss below. I recently did the same install on another system very similar to the problem system, I did not have this problem at all. I also set the pipeline quota in NCP to be 10000. Summary of GBLSECTION and GBLPAGE usage. ---------------------------------------- Used Free Max allowed ---- ---- ----------- GBLSECTIONS 144 156 300 GBLPAGES 9644 11056 20700 Username: SYSTEM Owner: SYSTEM MANAGER Account: SYSTEM UIC: [1,4] ([SYSTEM]) CLI: DCL Tables: DCLTABLES Default: SYS$SYSROOT:[SYSMGR] LGICMD: LOGIN Login Flags: Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun No access restrictions Expiration: (none) Pwdminimum: 8 Login Fails: 0 Pwdlifetime: 30 00:00 Pwdchange: 1-MAR-1989 11:40 Last Login: 8-MAR-1989 11:52 (interactive), 8-MAR-1989 11:33 (non-interactive) Maxjobs: 0 Fillm: 40 Bytlm: 32768 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 18 JTquota: 1024 Prclm: 10 DIOlm: 18 WSdef: 256 Prio: 4 ASTlm: 24 WSquo: 512 Queprio: 0 TQElm: 20 WSextent: 2048 CPU: (none) Enqlm: 200 Pgflquo: 20480 Authorized Privileges: CMKRNL CMEXEC SYSNAM GRPNAM ALLSPOOL DETACH DIAGNOSE LOG_IO GROUP ACNT PRMCEB PRMMBX PSWAPM ALTPRI SETPRV TMPMBX WORLD OPER EXQUOTA NETMBX VOLPRO PHY_IO BUGCHK PRMGBL SYSGBL MOUNT PFNMAP SHMEM SYSPRV BYPASS SYSLCK SHARE GRPPRV READALL SECURITY Default Privileges: CMKRNL CMEXEC SYSNAM GRPNAM ALLSPOOL DETACH DIAGNOSE LOG_IO GROUP ACNT PRMCEB PRMMBX PSWAPM ALTPRI SETPRV TMPMBX WORLD OPER EXQUOTA NETMBX VOLPRO PHY_IO BUGCHK PRMGBL SYSGBL MOUNT PFNMAP SHMEM SYSPRV BYPASS SYSLCK SHARE GRPPRV READALL SECURITY Modparams.dat SCSSYSTEMID=27843 SCSNODE="dsgn02" VAXCLUSTER=0 PAGEFILE = 0 SWAPFILE = 0 DUMPFILE = 0 NPAGEDYN=1500000 PAGEDYN=2000000 IRPCOUNT=1300 SRPCOUNT=1800
353.3	error messages sometimes mean what they say, you know!	MU::PORTER	what's in a name?	`Wed Mar 08 1989 14:11`	10
	This may seem a little obvious, but why don't you believe the message? "Page read error" could mean just that -- a hardware error on the disk. Chances are that the bad block is in the middle of an important DECwindows image. The system messages manual suggests checking the disk with ANAL/DISK/READ_CHECK. It may just be a bad spot on the disk. In which case, once the block is recorded as "bad", reinstalling DECwindows will fix up your problems.