Home > Articles

Like this article? We recommend

Like this article? We recommend

Migrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX MigrationsMigrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX Migrations

Learn More Buy

Like this article? We recommend

Like this article? We recommend

Migrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX MigrationsMigrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX Migrations

Learn More Buy

Page Retirement

Solaris maintains a list of pages not being used. This list of pages is known as the freelist. When a new page is needed, one is taken off the freelist. To remove a page from use permanently, it is sufficient to ensure that when it is no longer being used by the system, it is not returned to the freelist. Essentially, it will remain unused until the system is rebooted and the OS starts over with a new freelist. When a page is no longer being used, the OS calls the function page_free() on that page.

This section discusses some of the reasons for page retirement, and how faulty pages are handled.

Page Retirement for Correctable DIMM Errors

Page Retirement is implemented via bug IDs 4484338, 4504686, and 4880360. A memory DIMM which is experiencing repeated correctable (single-bit) errors has an increased probability of experiencing an uncorrectable (multi-bit) error. Likewise, the probability of a memory error condition which could result in system downtime also increases.

To help address this, new features have been implemented for both UltraSPARC II-based and UltraSPARC III-based systems. These features attempt to proactively predict which system memory components (DIMMs) have an increased probability of experiencing an uncorrectable error, and subsequently remove this memory from future use when it is no longer used by the kernel or any processes. Limits are placed on the number of memory pages which can be retired from use.

A CPU receives notification that a correctable memory error has occurred via the trap mechanism. This initiates the following sequence of events:

  1. The correctable error (CE) is scrubbed from the system using a sequence of address space identifier (ASI) memory accesses, cache line flushes, and so on.

    2. NOTE

    The operations to clear an error are CPU type specific.

    The CE can fall into one of three categories:

    • A CE is considered intermittent if the error is not detected upon a reread of the affected memory word. An intermittent CE is often referred to as a transient soft error.

    • A CE is considered persistent if the error is detected upon reread, but the scrubbing operation corrected it. A persistent CE is often referred to as a temporary soft error.

    • A CE is considered sticky if after scrubbing, the error is still present. A sticky CE is often referred to as a stuck-at hard error.

  2. The physical address that caused the CE is read from the asynchronous fault address register (AFAR). From this, the DIMM that contains the affected memory cell is determined.

  3. The "Leaky Bucket" SERD algorithm is invoked on this DIMM. This monitors the frequency and interval of CE occurrences on a system component. If these exceed a certain threshold, the system decides this component is "deteriorating," and pages mapped to it should be removed from use. The algorithm ignores intermittent CE occurrences but counts persistent CE occurrences. Sticky CE occurrences cause the DIMM on which the CE occurs to be immediately marked as deteriorating. Until the threshold of acceptable CE occurrences on a DIMM has been exceeded, no pages on that DIMM are retired. After the threshold is exceeded, every subsequent CE on that DIMM causes a page retire operation.

  4. When the DIMM is marked as deteriorating, Solaris also marks the physical page containing the physical address as deteriorating.

    5. NOTE

    At this point both the physical DIMM (identified by its UNUM string) and the physical page frame are marked deteriorating.

  5. The physical page is now retired from use, if possible, and the system continues normal operations.

Because of memory interleaving, every DIMM in the system has multiple pages associated with it. Conversely, a single physical page consists of portions of physical memory from multiple DIMMs.

Toxic vs. Failing Pages

The OS distinguishes between pages that have correctable or uncorrectable errors. A page with an uncorrectable error which might be able to be cleared is marked as toxic. Pages that are mapped to a DIMM that has experienced multiple correctable errors are marked as failing. Recall earlier that DIMMs could be marked as deteriorating. A deteriorating DIMM contains pages that are either toxic or failing.

If a page is marked toxic, the OS attempts to clean any errors from the page using a scrubbing algorithm when page_free() is invoked on that page. If it can verify that there are no errors on the page after it does its scrubbing, it allows that page to be returned to the freelist. This ensures that a single error does not cause a page to be removed from the system. If the scrubbing is unsuccessful, the page is marked as failing. Further, if it is no longer in use by other threads, the page is immediately retired.

If a page is marked failing, no attempt is made to clean the page via scrubbing. It is immediately retired if it is no longer in use by other threads.

The sequence of operations is as follows:

  1. When the page is deemed to be failing, a flag is set on that page, PAGE_IS_FAILING.

  2. When the page is no longer in use, page_free() is invoked on that page.

  3. If the PAGE_IS_FAILING flag is set, page_free() moves the page to a special retired pages vnode, and the amount of available free memory in the system is decremented. The page is not returned to the freelist, and so will not be used again until reboot.

Page Retirement and DR

Page Retirement does not utilize DR. Automatic DR of an entire system board or its subcomponents is not attempted due to one or more pages being retired on a board. If a system administrator manually performs DR on a system board containing retired pages out of a domain and into the same or another domain, the pages will be active again if the POST process is successful.

There is currently no mechanism to inform POST/OBP of deteriorating DIMMs. For this reason, there exists no method to remove a page from use permanently across reboots. The end result is that pages retired during one OS run become available again at the next boot.

NOTE

Solaris 8 Kernel Update patches prior to 108528-24 and Solaris 9 Kernel Update patches 112233-08 and earlier provide a rudimentary implementation of page retirement, but it is disabled by default. You will find it possible to enable the feature via the /etc/system file. However, due to bug IDs 4401262 and 4854496, which are present in those releases, it is not recommended to do so. The following two paragraphs describe these bug IDs in more detail.

Bug ID 4401262 describes a hang condition during dynamic reconfiguration. If a system board with DIMMs containing retired pages is subsequently dynamically reconfigured from the system, the DR operation hangs during the DR unconfigure stage. Note that you might also encounter a memory error during DR which invokes the page retirement algorithms during the DR operation. This is expected to result in the same hang condition; however, test cases have not proven this. The message to understand regarding Solaris 8 Kernel Update patches prior to 108528-24 and Solaris 9 Kernel Update patches 112233-08 and earlier is that DR should not be used on a system board containing known retired pages. Service to the DIMM should be postponed until such time as the OS can be taken down.

Bug ID 4854496 describes a panic condition that results from dereferencing a pointer which resides on a page already zeroed by page retirement. While no customers have experienced this panic condition outside of artificially created conditions, it is theoretically possible for it to occur.

While it is not recommended, armed with this knowledge you can understand the DR interaction and potential panic conditions, and enable page retirement on those systems which need to utilize this feature but which cannot run Solaris 8 Kernel Update patch 108528-24.

Tunables

The following /etc/system variables and their possible values are listed here for reference only. Changing the values to other than their defaults should only be done under the guidance of an authorized Sun Microsystems service provider.

TABLE 2 Page Retirement Variables and Values

Variables

Values

set ce_verbose_memory=[0/1/2]

set ce_verbose_other=[0/1/2]

A value of 0 indicates no logging. A value of 1 indicates that the messages are sent to the log file, but not the console. A value of 2 indicates that the messages are sent to the console and the log file. The default value is 1.

set automatic_page_removal=[0/1]

A value of 0 disables the page retirement feature. A value of 1 enables the page retirement feature. The default value depends upon the kernel patch release and is discussed in a prior section.

set ecc_softerr_interval=1440

set ecc_softerr_limit=2

The interval measured in minutes and number of acceptable CEs within this interval. Used by the Leaky Bucket algorithm to determine when to begin page retirement. It is acceptable to have ecc_softerr_limit CEs within ecc_softerr_interval minutes. Beyond this threshold, begin page retirement. These values are the defaults.

set max_pages_retired_bps=10

Limits the number of physical memory pages which can be retired. This number is a percentage of physical memory stored as basis points, where 100 basis points is 1%. The default is 10, or.1% of physical memory.

Example Messaging

The following is a sequential extract of messages from the system log of a system which experienced multiple errors on two DIMMs.

  1. CE on Memory Module Board 4 J3401 (First DIMM, First Error)

    2. Jan 7 04:13:29 pyre SUNW,UltraSPARC-II: [ID 194692 kern.notice] [AFT0] Corrected Memory Error detected by CPU12, errID 0x0000003b.24cd6aea
Jan 7 04:13:29 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.2db18000
Jan 7 04:13:29 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330400
Jan 7 04:13:29 pyre  UDBH Syndrome 0x64 Memory Module Board 4 J3401
Jan 7 04:13:29 pyre SUNW,UltraSPARC-II: [ID 898376 kern.notice] [AFT0] errID 0x0000003b.24cd6aea Corrected Memory Error on Board 4 J3401 is Persistent
Jan 7 04:13:29 pyre SUNW,UltraSPARC-II: [ID 906141
kern.notice] [AFT0] errID 0x0000003b.24cd6aea ECC Data Bit 7 was in error and corrected

  2. CE on Memory Module Board 4 J3801 (Second DIMM, First Error)

    3. Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 338670 kern.notice] [AFT0] Corrected Memory Error detected by CPU5, errID 0x00000043.f7fb26ef
Jan 7 04:14:07 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.2bf6c000
Jan 7 04:14:07 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:07 pyre  UDBH Syndrome 0xf2 Memory Module Board 4 J3801
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 282000 kern.notice] [AFT0] errID 0x00000043.f7fb26ef Corrected Memory Error on Board 4 J3801 is Persistent
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 339990 kern.notice] [AFT0] errID 0x00000043.f7fb26ef ECC Data Bit 9 was in error and corrected
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c000, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c008, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c010, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c018, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c020, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c028, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c030, Data 0x0eccf00d.ff250000, ECC 0xd5

  3. CE on Memory Module Board 4 J3801 (Second DIMM, Second Error)

    4. Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 492729 kern.notice] [AFT0] Corrected Memory Error detected by CPU5, errID 0x00000043.f9761088
Jan 7 04:14:07 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.2bf6c040
Jan 7 04:14:07 pyre  AFSR.PSYND 0x0000(Score 05)
AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:07 pyre  UDBH Syndrome 0xf2 Memory Module Board 4 J3801
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 203173 kern.notice] [AFT0] errID 0x00000043.f9761088 Corrected Memory Error on Board 4 J3801 is Persistent
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 429558 kern.notice] [AFT0] errID 0x00000043.f9761088 ECC Data Bit 9 was in error and corrected
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c040, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c048, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c050, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c058, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c060, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c068, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c070, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c078, Data 0x0eccf00d.ff250040, ECC 0x5c

  4. CE on Memory Module Board 4 J3801 (Second DIMM, Third Error)

    5. Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 313390 kern.notice] [AFT0] Corrected Memory Error detected by CPU5, errID 0x00000043.faed89ef
Jan 7 04:14:07 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.2bf6c080
Jan 7 04:14:07 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:07 pyre  UDBH Syndrome 0xf2 Memory Module Board 4 J3801
Jan 7 04:14:07 pyre unix: [ID 596940 kern.warning] WARNING: [AFT0] 3 soft errors in less than 24:00 (hh:mm) detected from Memory Module Board 4 J3801

  5. CE count on J3801 has exceeded maximum acceptable; page removal is attempted

    6. Jan 7 04:14:07 pyre unix: [ID 618185 kern.notice] NOTICE: Scheduling removal of page 0x00000001.2bf6c000
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 873457 kern.notice] [AFT0] errID 0x00000043.faed89ef Corrected Memory Error on Board 4 J3801 is Persistent
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 185728 kern.notice] [AFT0] errID 0x00000043.faed89ef ECC Data Bit 9 was in error and corrected
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c080, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c088, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c090, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c098, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0a0, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0a8, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0b0, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0b8, Data 0x0eccf00d.ff250080, ECC 0xb1

  6. CE on Memory Module Board 4 J3801 (Second DIMM, Fourth Error)

    7. Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 958426 kern.notice] [AFT0] Corrected Memory Error detected by CPU5, errID 0x00000043.fc6c8d68
Jan 7 04:14:07 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.2bf6c0c0
Jan 7 04:14:07 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:07 pyre  UDBH Syndrome 0xf2 Memory Module Board 4 J3801
Jan 7 04:14:07 pyre unix: [ID 596940 kern.warning] WARNING: [AFT0] 4 soft errors in less than 24:00 (hh:mm) detected from Memory Module Board 4 J3801

  7. CE count on J3801 still in excess of maximum acceptable; page removal is attempted (Note: this is the same page as before, which could not be removed because it was still in use. This is the second attempt)

    8. Jan 7 04:14:07 pyre unix: [ID 618185 kern.notice] NOTICE: Scheduling removal of page 0x00000001.2bf6c000
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 716816 kern.notice] [AFT0] errID 0x00000043.fc6c8d68 Corrected Memory Error on Board 4 J3801 is Persistent
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 236389 kern.notice] [AFT0] errID 0x00000043.fc6c8d68 ECC Data Bit 9 was in error and corrected
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0c0, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0c8, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0d0, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0d8, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0e0, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0e8, Data 0x0eccf00d.ff2500c0, ECC 0x38
Jan 7 04:14:07 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x12bf6c0f0, Data 0x0eccf00d.ff2500c0, ECC 0x38

  8. Page on Memory Module Board 4 J3801 is removed

    9. Jan 7 04:14:12 pyre unix: [ID 693633 kern.notice] NOTICE: Page 0x00000001.2bf6c000 removed from service

  9. CE on Memory Module Board 6 J3801 (Third DIMM, First Error)

    10. Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 298492 kern.notice] [AFT0] Corrected Memory Error detected by CPU15, errID 0x00000046.fd74b4e8
Jan 7 04:14:20 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.35bf4000
Jan 7 04:14:20 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:20 pyre  UDBH Syndrome 0xf2 Memory Module Board 6 J3801
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 686754 kern.notice] [AFT0] errID 0x00000046.fd74b4e8 Corrected Memory Error on Board 6 J3801 is Persistent
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 542367 kern.notice] [AFT0] errID 0x00000046.fd74b4e8 ECC Data Bit 9 was in error and corrected
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4000, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4008, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4010, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4018, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4020, Data 0x0eccf00d.ff250000, ECC 0xd5
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4028, Data 0x0eccf00d.ff250000, ECC 0xd5

  10. CE on Memory Module Board 6 J3801 (Third DIMM, Second Error)

    11. Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 565072 kern.notice] [AFT0] Corrected Memory Error detected by CPU15, errID 0x00000046.fef0581a
Jan 7 04:14:20 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.35bf4040
Jan 7 04:14:20 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:20 pyre  UDBH Syndrome 0xf2 Memory Module Board 6 J3801
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 190951 kern.notice] [AFT0] errID 0x00000046.fef0581a Corrected Memory Error on Board 6 J3801 is Persistent
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 744456 kern.notice] [AFT0] errID 0x00000046.fef0581a ECC Data Bit 9 was in error and corrected
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4040, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4048, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4050, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4058, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4060, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4068, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4070, Data 0x0eccf00d.ff250040, ECC 0x5c
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4078, Data 0x0eccf00d.ff250040, ECC 0x5c

  11. CE on Memory Module Board 6 J3801 (Third DIMM, Third Error)

    12. Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 372229 kern.notice] [AFT0] Corrected Memory Error detected by CPU15, errID 0x00000047.005d5687
Jan 7 04:14:20 pyre  AFSR 0x00000000.00100000<CE> AFAR 0x00000001.35bf4080
Jan 7 04:14:20 pyre  AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x78330be0
Jan 7 04:14:20 pyre  UDBH Syndrome 0xf2 Memory Module Board 6 J3801
Jan 7 04:14:20 pyre unix: [ID 596940 kern.warning] WARNING: [AFT0] 3 soft errors in less than 24:00 (hh:mm) detected from Memory Module Board 6 J3801

  12. CE count on J3801 has exceeded maximum acceptable; page removal is attempted

    13. Jan 7 04:14:20 pyre unix: [ID 618185 kern.notice] NOTICE: Scheduling removal of page 0x00000001.35bf4000
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 834227 kern.notice] [AFT0] errID 0x00000047.005d5687 Corrected
Memory Error on Board 6 J3801 is Persistent
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 745085 kern.notice] [AFT0] errID 0x00000047.005d5687 ECC Data Bit 9 was in error and corrected
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4080, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4088, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4090, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf4098, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf40a0, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf40a8, Data 0x0eccf00d.ff250080, ECC 0xb1
Jan 7 04:14:20 pyre SUNW,UltraSPARC-II: [ID 832828 kern.notice] [AFT0] Paddr 0x135bf40b0, Data 0x0eccf00d.ff250080, ECC 0xb1

  13. Page for Memory Module Board 6 J3801 is removed

    14. Jan 7 04:14:25 pyre unix: [ID 693633 kern.notice] NOTICE: Page 0x00000001.35bf4000 removed from service

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020