| Title: | TurboLaser Notesfile - AlphaServer 8200 and 8400 systems |
| Notice: | Welcome to WONDER::TURBOLASER in it's new home shortly |
| Moderator: | LANDO::DROBNER |
| Created: | Tue Dec 20 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1218 |
| Total number of notes: | 4645 |
Has anyone an idea how I could to associate pages on the bad page list
to the failing hardware. This bad pages start to show up during the
day, where their number varies between 4 and 8. They gradually disappear at
the end of the day. All this bad pages are process pages with the modify
bit set.
I think we can exclude memory, as this pages are scattered all around the
6GB of memory.
Operating system is OpenVMS V6.2-1H3
Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (6144.00Mb) 786432 284793 437205 64434
Bad Pages Total Dynamic I/O Errors Static
8 0 8 0
Virtual I/O Cache (Kbytes): Total Free In Use
Cache Memory 3200 0 3200
Granularity Hint Regions (pages): Total Free In Use Released
Execlet code region 1024 0 523 501
Execlet data region 128 0 104 24
VMS exec data region 22613 0 22613 0
Resident image code region 1536 0 810 726
Slot Usage (slots): Total Free Resident Swapped
Process Entry Slots 1200 633 567 0
Balance Set Slots 781 216 565 0
Dynamic Memory Usage (bytes): Total Free In Use Largest
Nonpaged Dynamic Memory 173858816 4086976 169771840 27712
Paged Dynamic Memory 10158080 5853792 4304288 5830208
Paging File Usage (blocks): Free Reservable Total
DISK$SUPRA1_PF1:[PAGEFILES]SUPRA1$PAGEFILE01.SYS;1
816800 -1034896 2599936
DISK$SUPRA1_PF2:[PAGEFILES]SUPRA1$PAGEFILE02.SYS;1
832352 -1036544 2599936
DISK$SUPRA1_PF3:[PAGEFILES]SUPRA1$PAGEFILE03.SYS;1
865920 -1038144 2599936
DISK$SUPRA1_PF4:[PAGEFILES]SUPRA1$PAGEFILE04.SYS;1
901008 -1034640 2599936
Bad page list
-------------
Count: 8
Lolimit: -1
High limit: 1073741824
ADDRESS PFN PTE ADDR BAK REFCNT FLINK BLINK PAGTYP LOC SWPPG/ FLAGS
BO REF
-------- -------- -------- ----------------- ------ ------ ------ ------- ------- ------ -------------------------------
81B48280 00039D14 E28A71A0 0501F571 00000000 0 038B6D 000000 PROCESS BADLIST ---- modify
81B24DA0 00038B6D E28A7080 0501F530 00000000 0 05E5FE 039D14 PROCESS BADLIST ---- modify
81FD9FC0 0005E5FE B83D7E10 0501F539 00000000 0 086695 038B6D PROCESS BADLIST ---- modify
824DB2A0 00086695 C9A899C0 0521F561 00000000 0 07B4FF 05E5FE PROCESS BADLIST ---- modify
82377FE0 0007B4FF D342BB60 0511F551 00000000 0 079550 086695 PROCESS BADLIST ---- modify
82338A00 00079550 E3DF9D40 0521F549 00000000 0 0A44FC 07B4FF PROCESS BADLIST ---- modify
82897F80 000A44FC DB8529C8 0511F559 00000000 0 07C790 079550 PROCESS BADLIST ---- modify
8239D200 0007C790 E3DF9D48 0521F569 00000000 0 000000 0A44FC PROCESS BADLIST ---- modify
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1083.1 | PROXY::HELLEN | Thu Feb 06 1997 09:26 | 9 | ||
The only time I've seen bad pages has been memory. When self test
finds an error the console tells the OS to map out the appropriate
page. On the running system you can try the following to find out
of correctable errors have occurred.
ANAL/SYS
SDA>exam @exe$ar_crd_feet;200
If this is non zero then it describes memory correctable errors.
| |||||
| 1083.2 | ZIMBRA::BERNARDO | Dave Bernardo, VMS Engineering | Thu Feb 06 1997 09:49 | 4 | |
Certain kinds of IO errors can also result in pages being put
on the bad list. Are you having any disk/tape problems?
d.
| |||||
| 1083.3 | solved | LEMAN::NEUWEILER | Thu Feb 06 1997 10:33 | 5 | |
The 4 RZ28's holding the pagefiles have been replaced, and the errors
disappeard. There were no errors logged for any of this disk.
Joerg
| |||||