what is SBE

[唐贤勇]

what can cause Single bit error (SBE)?and it seems that it has some relationship with 'PDT full' event.How can I deal with it.
Thank you very much.

tang

[James Murtagh · Accepted solution]

Hi Tang,

Continuous single bit memory errors are normally indicative that a memory dimm is due to fail. The PDT is the page deallocation table, where pages that reported the bit errors are effectively quarantined and can no longer be used by the OS. If you have a hardware support contract log a case to have the dimm identified and replaced. You can use STM to identify this yourself if you want to.

Cheers,

James.

[唐贤勇]

so,It may be a hardware problem,isn't it?How can I monitor the situation?
Thank you.

tang

[James Murtagh]

Yup. Well, you already seem to be monitoring it? I assume the messages are being passed to the kernel message buffer so you can use dmesg to read this. If you use :

# dmesg -

this will report anything since the last time it was run. Your monitoring may quickly come to an end if there is a double bit error though - the system will crash.

- jm

[Con O'Kelly]

Hi

As James said you can use STM.
For example:
# cstm
cstm> map
cstm> sel dev
cstm>info
cstm>infolog

This will give you information about memory on your system. You will see a section on PDT. If you have a number of entries in the PDT table then contact your HP support Engineer.

Cheers
Con

[唐贤勇]

# dmesg

Feb 20 11:40
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
0 sba
0/0 lba
0/0/0/0 btlan
0/0/1/0 c720
0/0/1/0.1 tgt
0/0/1/0.1.0 stape
0/0/1/0.7 tgt
0/0/1/0.7.0 sctl
0/0/1/1 c720
0/0/1/1.2 tgt
0/0/1/1.2.0 sdisk
0/0/1/1.7 tgt
0/0/1/1.7.0 sctl
0/0/2/0 c720
0/0/2/0.2 tgt
0/0/2/0.2.0 sdisk
0/0/2/0.7 tgt
0/0/2/0.7.0 sctl
0/0/2/1 c720
0/0/2/1.2 tgt
0/0/2/1.2.0 sdisk
0/0/2/1.7 tgt
0/0/2/1.7.0 sctl
0/0/4/0 func0
0/0/4/1 asio0
0/1 lba
0/2 lba
0/3 lba
0/4 lba
0/5 lba
0/8 lba
0/8/0/0 btlan
0/9 lba
0/9/0/0 btlan
0/10 lba
0/10/0/0 td
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/10/0/0
0/10/0/0.8 fcp
0/10/0/0.8.0.110.0 fcparray
0/10/0/0.8.0.110.0.0 tgt
0/10/0/0.8.0.110.0.0.0 sdisk
0/10/0/0.8.0.110.0.0.1 sdisk
0/10/0/0.8.0.110.0.0.2 sdisk
0/10/0/0.8.0.110.0.0.3 sdisk
0/10/0/0.8.0.110.0.0.4 sdisk
0/10/0/0.8.0.110.0.0.5 sdisk
0/10/0/0.8.0.110.0.0.6 sdisk
0/10/0/0.8.0.110.0.0.7 sdisk
0/10/0/0.8.0.110.0.1 tgt
0/10/0/0.8.0.110.0.1.0 sdisk
0/10/0/0.8.0.110.0.1.1 sdisk
0/10/0/0.8.0.255.6 fcpdev
0/10/0/0.8.0.255.6.14 tgt
0/10/0/0.8.0.255.6.14.0 sctl
0/12 lba
0/12/0/0 td
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/12/0/0
0/12/0/0.8 fcp
0/12/0/0.8.0.108.0 fcparray
0/12/0/0.8.0.108.0.0 tgt
0/12/0/0.8.0.108.0.0.0 sdisk
0/12/0/0.8.0.108.0.0.1 sdisk
0/12/0/0.8.0.108.0.0.2 sdisk
0/12/0/0.8.0.108.0.0.3 sdisk
0/12/0/0.8.0.108.0.0.4 sdisk
0/12/0/0.8.0.108.0.0.5 sdisk
0/12/0/0.8.0.108.0.0.6 sdisk
0/12/0/0.8.0.108.0.0.7 sdisk
0/12/0/0.8.0.108.0.1 tgt
0/12/0/0.8.0.108.0.1.0 sdisk
0/12/0/0.8.0.108.0.1.1 sdisk
0/12/0/0.8.0.255.6 fcpdev
0/12/0/0.8.0.255.6.12 tgt
0/12/0/0.8.0.255.6.12.0 sctl
32 pbc
33 processor
96 pbc
97 processor
192 memory
btlan: Initializing 10/100BASE-TX card at 0/0/0/0....

System Console is on the Built-In Serial Interface
btlan: Initializing 10/100BASE-TX card at 0/8/0/0....
btlan: Initializing 10/100BASE-TX card at 0/9/0/0....
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x12000; start = 310112, size = 4194304
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2097152 Kbytes, lockable: 1856860 Kbytes, available: 1809600 Kbytes


Above is the result of the 'dmesg' command,I can't find the just information.

tang

[James Murtagh]

This information from dmesg is the system initialisation messages. If the system was rebooted recently use "dmesg -" to monitor for any new messages. If not then just monitor where you found the errors in the first place?

- jm.

[唐贤勇]

I found the information in the mails sent to the root user.So,it may be the information,isn't it?How can I make sure of it?
Thank you.

tang