Alert Standard Format (ASF) Specification

Alert Standard Format (ASF) Specification v2.0 DMTF Document DSP0136
DSP0136 23 April 2003 Page 16 of 94
Descriptor Code Description
15h Reserved.
16h Floppy initialization.
17h Keyboard test.
18h Pointing device test
19h Primary processor initialization
1Ah to FFh Reserved for future definition by this specification.
This table describes the Specific Trap Field values for some system firmware progress events.
The Event Type sub-field for each of these traps is set to 6Fh (Sensor-specific).
Description
Event Sensor
Type
Event Offset
Event
Data 1/2
Entity
System firmware started. The
presence of this progress code
indicates that at least one CPU is
properly executing.
25h (Entity
Presence)
00h (Entity
Present)
40h/00h 34d (BIOS)
Starting memory initialization and
test.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/01h
32d (Memory
Device)
Completed memory initialization
and test.
0Fh (Firmware
Error or
Progress)
82h (System
Firmware
Progress, exit)
40h/01h
32d (Memory
Device)
Starting hard-disk initialization and
test.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/02h
4 (Disk or
Disk Bay)
Waiting for user-password entry.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/04h 34d (BIOS)
Entering BIOS setup.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/05h 34d (BIOS)
Starting system resource
configuration, e.g. performing PCI
configuration.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/07h 34d (BIOS)
Starting option ROM initialization.
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/08h
11d (Add-in
board)
Starting OS boot process (e.g.
preparing to issue Int 19h)
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/13h
0
(Unspecified)
Starting secondary processor(s)’
initialization
0Fh (Firmware
Error or
Progress)
02h (System
Firmware
Progress, entry)
40h/03h 3 (Processor)
3.1.5.4 OS Events
This table describes the Specific Trap Field values for some OS events. The variable-bindings
Entity field for each of these traps is 35d (OS) and the Event Type field for each is 6Fh (Sensor
specific). A timer-expiration event can generally be considered to indicate a hang associated with
the software that was running when the expiration occurred.