DOCSLIB.ORG

Decstation 5000 Model 100 Series Maintenance Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Decstation 5000 Model 100 Series Maintenance Guide EK-PM32G-MG-003 DECstation 5000 Model 100 Series Maintenance Guide digital equipment corporation maynard, massachusetts First printing, May 1991 Second printing, January 1992 Third printing, April 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Digital Equipment Corporation assumes no responsibility for the use or reliability of its software on equipment that is not supplied by Digital or its affiliated companies. © Digital Equipment Corporation 1993. All Rights Reserved Printed in U.S.A. USA This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXBI DECnet ThinWire VAXcluster DECstation TURBOchannel VAXstation DECsystem ULTRIX VMS DECUS ULTRIX-32 VT MicroVAX UNIBUS MicroVMS VAX dt Contents About This Guide .......................................... xxi 1 A Look at DECstation 5000 Model 100 Series Hardware System Hardware Configurations . .................... 1–1 Basic System Hardware............................... 1–3 System Unit . .................................... 1–3 System Unit Controls and Indicators ................. 1–5 System Unit Connectors ............................ 1–6 Hardware Options .................................... 1–8 CPU Modules . .................................... 1–9 Additional Memory Modules ........................ 1–9 Optional TURBOchannel Modules ................... 1–9 Drives ........................................... 1–9 Monitors and Terminals ............................ 1–10 Keyboard, Mouse, and Other Pointing Devices ......... 1–10 For Further Information . ............................ 1–11 2 Service Operations Using an Antistatic Kit . ............................ 2–2 Using an Alternate Terminal ........................... 2–3 Removing and Installing the System Unit Cover .......... 2–5 How to Remove the System Unit Cover . ........... 2–6 How to Install the System Unit Cover ................ 2–6 Removing and Installing Loopback Connectors and Terminators ......................................... 2–6 How to Remove a ThickWire Loopback Connector . 2–7 iii How to Install a ThickWire Loopback Connector ....... 2–7 How to Remove a Communications Loopback Connector ........................................ 2–8 How to Install a Communications Loopback Connector ........................................ 2–8 How to Remove a SCSI Chain Terminator . ........... 2–9 How to Install a SCSI Chain Terminator . ........... 2–9 How to Remove a Communications Line Adapter . 2–11 How to Install a Communications Line Adapter ....... 2–11 How to Remove a SCSI Controller Terminator ......... 2–12 How to Install a SCSI Controller Terminator .......... 2–12 Entering Console and Operating Modes ................. 2–13 How to Enter Console Mode ........................ 2–14 How to Enter Operating Mode . .................... 2–14 Using Console Command Passwords .................... 2–15 To Set or Change a Password . .................... 2–15 To Remove a Requirement for a Password . ........... 2–15 To Erase a Password You Do Not Know . ........... 2–16 Inserting and removing a clear-NVR jumper . 2–17 Booting the System Software .......................... 2–18 Setting System Boot ROM Switches .................... 2–18 Shutting Down the System Software .................... 2–20 3 Troubleshooting Tools Using Tests ......................................... 3–2 Using Slot Numbers in Test Commands and Error Messages ........................................ 3–2 Running Power-Up Self-Tests .......................... 3–4 Running Subtests .................................... 3–5 How to Run Individual Tests ........................ 3–5 How to Run Test Scripts ........................... 3–6 How to Display Lists of Available Tests............... 3–6 Displaying a list of available test scripts ....... 3–7 Displaying the contents of a test script ......... 3–7 How to Create Test Scripts ......................... 3–8 Interpreting Test Error Messages . .................... 3–9 Using ULTRIX Error Logs . ............................ 3–10 Examining Error Logs . ............................ 3–10 Error Log Format ................................. 3–10 Error log example ........................... 3–11 Event Types . .................................... 3–12 Using Memory Error Logs .......................... 3–13 Analyzing the Memory Error Example ......... 3–14 iv Using Error and Status Register Error Logs .......... 3–15 Example 1: Error and status register error log . 3–15 Analysis of Example 1 . .................... 3–17 Example 2: Error and status register error log . 3–18 Analysis of Example 2 . .................... 3–20 Physical address space . .................... 3–21 For Further Information . ............................ 3–22 4 Identifying Failed FRUs Troubleshooting Process . ............................ 4–2 Troubleshooting When the Power-Up Self-Test Does Not Complete ........................................... 4–4 How to Troubleshoot When the Diagnostic LED Display Is 0011 1011, 0010 1011, 0001 1011, or 0000 1011 . 4–10 Troubleshooting when the right diagnostic LED display is 1011 and the system has a graphics module .................................... 4–10 Troubleshooting when the right diagnostic LED display is 1011 and the system has no graphics module .................................... 4–11 Troubleshooting When the Monitor Has No Display ....... 4–12 Troubleshooting When an Error Message Appears on the Monitor ............................................. 4–14 How to Troubleshoot When an Error or Exception Occurs During a Test . .................................... 4–14 How to Troubleshoot When a Test Reports an Error . 4–15 How to Troubleshoot When a Console Exception Occurs ........................................... 4–19 Example: R4000 Console exception message . 4–19 Example: R3000 Console exception message . 4–20 Troubleshooting When Hardware Does Not Appear in the cnfg Display ......................................... 4–22 Troubleshooting the Memory Modules ................... 4–24 To Interpret Memory Test Error Messages . ........... 4–26 Example: Memory test error message .......... 4–26 Troubleshooting SCSI Controllers and Devices . ........... 4–27 HowtoUsethesdiagTest.......................... 4–29 Troubleshooting an Ethernet Controller ................. 4–30 How to Use the External Loopback Test . ........... 4–32 Example: External loopback test error messages .................................. 4–32 Troubleshooting a Printer, Modem, or Other Serial Line Device . ............................................. 4–33 v How to Use the Transmit and Receive Test ........... 4–35 Example: SCC transmit and receive test error messages .................................. 4–36 How to Use the Pins Test .......................... 4–37 Example: Pins test error messages . ........... 4–37 Troubleshooting the Power Supply . .................... 4–38 Troubleshooting If the System Unit Overheats ........... 4–39 Troubleshooting the Keyboard and Mouse ................ 4–42 Troubleshooting When ULTRIX Is Running but the Monitor Has No Display . .................................... 4–44 Troubleshooting with ULTRIX Error Logs ............... 4–47 To Interpret Error Log Event Types .................. 4–47 To Interpret Physical Address Registers . ........... 4–48 For Further Information . ............................ 4–50 Troubleshoot Daughter Card LEDs . .................... 4–50 5 Base System FRUs System Module . .................................... 5–2 System Module HardwareDescription ................ 5–2 Removing and Installing a System Module . ........... 5–3 How to remove the system module . ........... 5–4 How to install a system module ............... 5–6 Removing and Installing an ESAR Chip on the System Module .......................................... 5–7 How to remove and install an ESAR chip ....... 5–8 CPU Module ........................................ 5–9 CPU Module Hardware Description .................. 5–9 Removing and Installing a CPU Module . ........... 5–13 How to remove a CPU module ................ 5–14 How to install a CPU module ................. 5–14 Memory Modules . .................................... 5–15 Memory Module Hardware Description ............... 5–15 Removing and Installing Memory Modules . ........... 5–21 How to remove a memory module . ........... 5–22 How to install a memory module . ........... 5–24 Power Supply ........................................ 5–26 Power Supply Hardware Description ................. 5–26 Removing and Installing the Power Supply ........... 5–28 How to remove the power supply . ........... 5–29 How to install the power supply ............... 5–29 vi Removing and Installing the Power
Load more

Recommended publications
  • The Design and Verification of the Alphastation 600 5-Series Workstation by John H
    The Design and Verification of the AlphaStation 600 5-series Workstation by John H. Zurawski, John E. Murray, and Paul J. Lemmon ABSTRACT The AlphaStation 600 5-series workstation is a high-performance, uniprocessor design based on the Alpha 21164 microprocessor and on the PCI bus. Six CMOS ASICs provide high-bandwidth, low-latency interconnects between the CPU, the main memory, and the I/O subsystem. The verification effort used directed, pseudorandom testing on a VERILOG software model. A hardware-based verification technique provided a test throughput that resulted in a significant improvement over software tests. This technique currently involves the use of graphics cards to emulate generic DMA devices. A PCI hardware demon is under development to further enhance the capability of the hardware-based verification. INTRODUCTION The high-performance AlphaStation 600 5-series workstation is based on the fastest Alpha microprocessor to date -- the Alpha 21164.[1] The I/O subsystem uses the 64-bit version of the Peripheral Component Interconnect (PCI) and the Extended Industry Standard Architecture (EISA) bus. The AlphaStation 600 supports three operating systems: Digital UNIX (formerly DEC OSF/1), OpenVMS, and Microsoft's Windows NT. This workstation series uses the DECchip 21171 chip set designed and built by Digital. These chips provide high-bandwidth, low-latency interconnects between the CPU, the main memory, and the PCI bus. This paper describes the architecture and features of the AlphaStation 600 5-series workstation and the DECchip 21171 chip set. The system overview is first presented, followed by a detailed discussion of the chip set. The paper then describes the cache and memory designs, detailing how the memory design evolved from the workstation's requirements.
    [Show full text]
  • A Machine-Independent DMA Framework for Netbsd
    AMachine-Independent DMA Framework for NetBSD Jason R. Thorpe1 Numerical Aerospace Simulation Facility NASA Ames Research Center Abstract 1.1. Host platform details One of the challenges in implementing a portable In the example platforms listed above,there are at kernel is finding good abstractions for semantically- least three different mechanisms used to perform DMA. similar operations which often have very machine- The first is used by the i386 platform. This mechanism dependent implementations. This is especially impor- can be described as "what you see is what you get": the tant on modern machines which share common archi- address that the device uses to perform the DMA trans- tectural features, e.g. the PCI bus. fer is the same address that the host CPU uses to access This paper describes whyamachine-independent the memory location in question. DMA mapping abstraction is needed, the design consid- DMA address Host address erations for such an abstraction, and the implementation of this abstraction in the NetBSD/alpha and NetBSD/i386 kernels. 1. Introduction NetBSD is a portable, modern UNIX-likeoperat- ing system which currently runs on eighteen platforms covering nine processor architectures. Some of these platforms, including the Alpha and i3862,share the PCI busasacommon architectural feature. In order to share device drivers for PCI devices between different platforms, abstractions that hide the details of bus access must be invented. The details that must be hid- den can be broken down into twoclasses: CPU access Figure 1 - WYSIWYG DMA to devices on the bus (bus_space)and device access to host memory (bus_dma). Here we will discuss the lat- The second mechanism, employed by the Alpha, ter; bus_space is a complicated topic in and of itself, is very similar to the first; the address the host CPU and is beyond the scope of this paper.
    [Show full text]
  • Alpha and VAX Comparison Based on Industry-Standard Benchmark
    Alpha and VAX Comparison based on Industry-standard Benchmark Results Digital Equipment Corporation December 1994 EC-N3909-10 Version 3.0 December 1994 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1 )(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227 7013. Copyright© 1994 Digital Equipment Corporation All rights reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, AlphaGeneration, DEC, OpenVMS, VMS, ULTRIX, and the DIGITAL logo. The following are third-party trademarks: MIPS is a trademark of MIPS Computer Systems, Inc. TPC-A is a trademark of the Transaction Processing Performance Council. INFORMIX is a registered trademark of lnformix Software, Inc. OSF/1 is a registered trademark of the Open Software Foundation, Inc. ORACLE is a registered trademark of Oracle Corporation. SPEC, SPECfp92, and SPECratio are trademarks of Standard Performance Evaluation Corporation. MIPS is a trademark of MIPS Computer Systems, Inc. All other trademarks and registered
    [Show full text]
  • Personal Decstation 5000 User's Guide
    Personal DECstation 5000 User’s Guide Order Number: EK–PM30E–RB.003 Digital Equipment Corporation Maynard, Massachusetts Second Printing, Sept, 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. All rights reserved. Printed in U.S.A. © Digital Equipment Corporation 1992. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC, DECconnect, DECnet, DECstation, DECsystem, DECUS, DESTA, ThinWire, Turbochannel, ULTRIX, ULTRIX-32, and the DIGITAL logo. Motif is a trademark of the Open Software Foundation, Inc. MS–DOS is a registered trademark of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems, Inc. VELCRO is a trademark of VELCRO USA, Inc. FCC NOTICE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.
    [Show full text]
  • Computer Architectures an Overview
    Computer Architectures An Overview PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 25 Feb 2012 22:35:32 UTC Contents Articles Microarchitecture 1 x86 7 PowerPC 23 IBM POWER 33 MIPS architecture 39 SPARC 57 ARM architecture 65 DEC Alpha 80 AlphaStation 92 AlphaServer 95 Very long instruction word 103 Instruction-level parallelism 107 Explicitly parallel instruction computing 108 References Article Sources and Contributors 111 Image Sources, Licenses and Contributors 113 Article Licenses License 114 Microarchitecture 1 Microarchitecture In computer engineering, microarchitecture (sometimes abbreviated to µarch or uarch), also called computer organization, is the way a given instruction set architecture (ISA) is implemented on a processor. A given ISA may be implemented with different microarchitectures.[1] Implementations might vary due to different goals of a given design or due to shifts in technology.[2] Computer architecture is the combination of microarchitecture and instruction set design. Relation to instruction set architecture The ISA is roughly the same as the programming model of a processor as seen by an assembly language programmer or compiler writer. The ISA includes the execution model, processor registers, address and data formats among other things. The Intel Core microarchitecture microarchitecture includes the constituent parts of the processor and how these interconnect and interoperate to implement the ISA. The microarchitecture of a machine is usually represented as (more or less detailed) diagrams that describe the interconnections of the various microarchitectural elements of the machine, which may be everything from single gates and registers, to complete arithmetic logic units (ALU)s and even larger elements.
    [Show full text]
  • PMAZ-AA Turbochannel SCSI Module Functional Specification
    -- -- PMAZ-AA TURBOchannel SCSI Module Functional Specification Revision 1.2 Workstation Systems Engineering Digital Equipment Corporation 100 Hamilton Avenue Palo Alto, CA 94301 August 27, 1990 August 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibilty for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Digital Equipment Coporation assumes no responsibility for the use or reliability of its software on equip- ment that is not supplied by Digital or its af®liated companies. Digital Equipment Corporation 1990. All Rights reserved Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC DECnet DECstation DECsystem DECUS MicroVAX MicroVMS PDP TURBOchannel ULTRIX ULTRIX-32 UNIBUS VAX VAXBI VAXcluster VAXstation VMS VT i -- -- Blank Page ii -- -- Table of Contents 1. PMAZ-AA SCSI Module 2. Address Map 3. Interrupts 4. Power Estimates 5. External Interface 6. Functional Description 6.1. 53C94 ............................................................................................................................... 4 6.2. SCSI Buffer ..................................................................................................................... 4 6.3. DMA Address Register ..................................................................................................
    [Show full text]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein.
    [Show full text]
  • Decstation/Decsystem 5000 Model 200 Series Maintenance Guide
    EK-PM38C-MG-002 DECstation/DECsystem 5000 Model 200 Series Maintenance Guide digital equipment corporation maynard, massachusetts First printing, January 1992 Second printing, April 1993 © Digital Equipment Corporation 1993. USA This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. The following are trademarks of Digital Equipment Corporation: DEC PDP VAXBI DECnet ThinWire VAXcluster DECstation TURBOchannel VAXstation DECsystem ULTRIX VMS DECUS ULTRIX-32 VT MicroVAX UNIBUS MicroVMS VAX dt Contents About This Guide .......................................... xix Part I Hardware 1 System Overview System Hardware Configurations . .................... 1–2 System Unit ......................................... 1–4 Controls and Indicators ............................ 1–6 External System Unit Connectors ................... 1–8 Internal Base System Module Connectors . ........... 1–10 Hardware Options and Peripherals . .................... 1–12 CPU Module Description ........................... 1–13 System Boot ROM ................................. 1–13 Memory Modules .................................
    [Show full text]
  • Software Product Description
    Software Product Description PRODUCT NAME: DECnet-ULTRIX, Version 4.0 for RISC and VAX SPD 26.83.08 ULTRIX Network Software (End-node Only) DESCRIPTION functions. The DECnet products and functions avail­ able to users on mixed networks can be determined by DECnet-ULTRIX, Version 4.0 is a Phase IV end­ comparison of the SPDs for the appropriate products. node implementation of Digital Network Architecture (DNA) for the ULTRIX Operating System and ULTRIX Note that incoming connections from all Phase III sys­ Worksystem Software (UWS) for VAX and RISC sys­ tems to DECnet-ULTRIX systems are supported. SUI>­ tems. port for outgoing connections Is limited to the following Phase I II systems: DECnet-VAX and DECnet-RT. In The DECnet-ULTRIX software enables communication addition, DECnet-ULTRIX only supports the connec­ among different networked Digital systems that use the tion of Phase IV routers/routing nodes on the point-to­ DNA Phase IIIIIV· protocols. At the same time, users point lines. and user programs can communicate with non-Digital systems that use the Internet (TCP/IP-based) proto­ Phase IV End Node cols. DECnet-ULTRIX offers the following capabilities: task-to-task communications, network virtual terminal, DECnet-ULTRIX is a Phase IV end-node only imple­ remote file transfer, mail, coexistence with the Internet mentation of DNA and as such, can communicate di­ protocols (TCPIIP-based), and network-wide resource rectly with any other Phase IV node on the Ethernet sharing and management as defined by the DNA pro­ or with any other Phase III/IV· node in the network via tocols.
    [Show full text]
  • Personal Decstation Series Technical Overview
    Personal DECstation Series Technical Overview • Personal DECstation 5000/20 • Personal DECstation 5000/25 TM Nameplate d i g i t a l WSMXS001 Worksystems Base Product Marketing Digital Equipment Corporation Palo Alto, California Version 1.0 December, 1991 Digital believes the information in this publication is accurate as of its publication date; such information is subject to change without notice. Digital is not responsible for any errors in the information given in this publication. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not sup- plied by Digital Equipment Corporation or its affiliated companies. The following are trademarks of Digital Equipment Corporation: DEC, DECstation, DEC Ada, DEC FUSE, DEC GKS, DEC PHIGS, DEC VUIT, DECnet, DECwindows, DECsystem, the DIGITAL Logo, PATHWORKS, PixelStamp, TURBOchannel, ULTRIX, VAX, VAXstation, VMS, and XUI. PostScript is a registered trademark of Adobe Systems, Inc. AT&T and System V are regis- tered trademarks of American Telephone and Telegraph Company. Apple and Macintosh are registered trademarks of Apple Computer, Inc. Network Computing System is a trademark of Hewlett-Packard Company. Intel is a trademark of Intel Corporation. PC/AT is a trademark and IBM and OS/2 are registered trademarks of International Business Machines Corporation. Lotus is a registered trademark of Lotus Development Corporation. MIPS is a registered trade- mark of MIPS Computer Systems, Inc. MS-DOS is a registered trademark of Microsoft Corpo- ration. NFS is a trademark of Sun Microsystems, Inc.
    [Show full text]
  • Digital Technical Journal, Volume 3, Number 3: Availability in Vaxcluster
    • Availability in VAXcluster Systems • Network Performance and Adapters Digital Technical Journal Digital Equipment Corporation Volume 3 Number 3 Summer 1991 Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Leon Descoteaux, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Mildred R. Rosenzweig, Production Editor Margaret Burdine, Typographer Peter Woodbury, illustrator Advisory Board Samuel H. Fuller, Chairman Richard W. Beane Robert M. Glorioso Richard]. Hollingsworth John W. McCredie Alan G. Nemeth Mahendra R. Patel E Grant Saviers Victor A. Vyssotsky Gayn B. Winters The Digital Technicaljournal is published quarterly by Digital Equipment Corporation, 146 Main Street ML01-3/B68, Maynard, Massachusetts 01754-2571. Subscriptions to the journal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electri­ cal engineering and computer science fields receive complimen­ tary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital Technical journal at the published-by address. Inquiries can also be sent electronically to DTJ®CRL.DEC.COM. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 12 Crosby Drive, Bedford, MA 01730-1493. Digital employees may send subscription orders on the ENET to RDVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. Allemployees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address.
    [Show full text]
  • Proceedings of the FREENIX Track: 2003 USENIX Annual Technical Conference
    USENIX Association Proceedings of the FREENIX Track: 2003 USENIX Annual Technical Conference San Antonio, Texas, USA June 9-14, 2003 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2003 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. An Implementation of User-level Restartable Atomic Sequences on the NetBSD Operating System Gregory McGarry [email protected] Abstract system[1]. While the kernel component of the model controls the switching of execution contexts, the user- This paper outlines an implementation of restartable level component is responsible for scheduling threads atomic sequences on the NetBSD operating system onto the available execution contexts. The user-level as a mechanism for implementing atomic operations component contains a complete scheduler implementa- in a mutual-exclusion facility on uniprocessor sys- tion with shared scheduling data which must be pro- tems. Kernel-level and user-level interfaces are dis- tected by the mutual-exclusion facility. Consequently, cussed along with implementation details. Issues as- the mutual-exclusion facility is a critical component of sociated with protecting restartable atomic sequences the scheduler activations threading model. from violation are considered. The performance of The basic building block for any mutual-exclusion fa- restartable atomic sequences is demonstrated to out- cility, whether it be a blocking or busy-wait construct, is perform syscall-based and emulation-based atomic op- the fetch-modify-write operation[5].
    [Show full text]