User`s guide
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Introduction
- Getting Started
- 2.1 Overview
- 2.2 System Requirements
- 2.3 Configuring Your System
- 2.4 Updating the Debug Monitor Firmware
- 2.4.1 Updating Firmware in a Flash ROM
- 2.4.2 Updating the Flash ROM from the AlphaBIOS S...
- 2.4.3 Updating the Flash ROM from the Windows NT ...
- 2.4.4 Updating the Flash ROM from the Debug Monit...
- 2.4.5 Updating the Flash ROM from the Alpha SRM C...
- 2.4.6 Running Firmware Update
- 2.4.7 Updating Firmware in a UVPROM
- 2.5 Switching to the Debug Monitor Firmware on Fl...
- 2.6 Debug Monitor Memory Map
- 2.7 Downloading Files
- 2.8 Execution Commands
- 2.9 Resetting the Debug Monitor
- Remote Debugging
- User Commands
- 4.1 Overview
- 4.2 Using the Commands
- 4.3 User Commands Quick Reference
- 4.4 User Commands
- apropos
- arpshow
- bcoff
- bcon
- beep
- boot
- bootadr
- bootopt
- bpstat
- cb
- cfreg
- cl
- compare
- cont
- copy
- cq
- creg
- cw
- date
- delete
- dis
- dml
- dmq
- ebuff
- edevice
- edmp
- einit
- eml
- emq
- eprom
- ereg
- eshow
- estat
- estop
- fill
- flash
- flasherase
- flboot
- flcd
- flcopy
- fldir
- flload
- flread
- flsave
- flwrite
- fwupdate
- go
- help
- iack
- ident
- init
- jtopal
- ladebug
- load
- mces
- mcheck
- memtest
- mrb
- mrl
- mrw
- mwb
- mwl
- mww
- netboot
- netload
- next
- pb
- pcishow
- pfreg
- pl
- pq
- prb
- preg
- prl
- prw
- pw
- pwb
- pwl
- pww
- rabox
- rb
- rbcfg
- rbctl
- rbiu
- riccsr
- rl
- rmode
- romboot
- romlist
- romload
- romverify
- rsys
- rw
- sb
- setbaud
- setty
- sl
- sq
- step
- stop
- sum
- sw
- swpipl
- sysshow
- tip
- version
- wabox
- wb
- wbcfg
- wbctl
- wbiu
- wiccsr
- wl
- wrfen
- wsys
- ww
- Support, Products, and Documentation
- Index
User Commands 4–89
User Commands
memtest
While conducting the memory test, correctable read data errors may be encountered,
indicating memory integrity problems. However, if hardware error reporting is
disabled, the CPU corrects the correctable errors without reporting them. To alleviate
this problem, the mcheck parameter must specify the machine check conditions
while running the memory test.
Device drivers that use main memory for DMA access while the memory test is
running may cause unpredictable results. To prevent the memory test from
conflicting with the device drivers, the stop_drivers parameter must be set to a
nonzero value.
Example
EB64> memtest 2 8000000 8ffffff 4 on 1