Просмотр новости

Найдите то, что Вас интересует

Re: Integrity RX2800 i6 MCA Reboot after Panic

Дата публикации: 25-06-2026 19:20:20

Hi,
The MCA files are not very conclusive and we were able to decode only that its a "External Bus error" that triggered all the MCA's.
Earliest timestamp: 2026/06/19 18:57:08Latest timestamp: 2026/06/19 18:57:08Time Span: 0 day(s), 00 hour(s), 00 minute(s), 00 second(s)
Preliminary error log consistency check completed
------------------------------------------------------------------------------Auxiliary Platform Information------------------------------------------------------------------------------
PRODUCT_NAME Integrity rx2800 i6SERIAL_NUMBER SGH219X8WYSAL_REVISION 0x00020070 (0002.0070)PAL_REVISION 0x05020502 (PAL_A 05.02, PAL_B 05.02)MEM_RANK_SIZE 0x0000000000000000 (Invalid)IO_BACKPLANE_TYPE 0x000000000000000a (Party/Party combo)CPU_CORES_PER_PROCESSOR 0x0000000000000004 (4 Cores/processor)PROC_HEADER_TYPE 0x0000000000000000 (standard type)GLOBAL_MCA 0x01 (MCA is Global)
Logical CPU Status
Socket 0 | 1Core 0 1 2 3 4 5 6 7 | 0 1 2 3 4 5 6 7Thread 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 | 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1------------------------------- | -------------------------------- - - - r r r r - - - - r r r r | - - - - r r r r - - - - r r r r
r = responding, n = non-responding, d = deconfigured, - = not present...----- Decoding BUS_CHECK[0] MOD_CHECK_INFO -----------------------------------
MOD_CHECK_INFO 0x0080000002000040[63] = 0x0 pi - Precise IP (not logged)[62] = 0x0 rp - Responder ID (not logged)[61] = 0x0 rq - Requestor ID (not logged)[60] = 0x0 tv - Target ID (not logged)[59] = 0x0 mcc - Machine Check Corrected (not corrected)[58] = 0x0 pv - Privilege Level (pl) Field (invalid)[57:56] = 0x0 pl[1:0] - Privilege Level (0)[55] = 0x1 iv - Instruction Set (is) Field (valid)[54] = 0x0 is - Instruction Set (IPF)[31:24] = 0x02 bsi[7:0] - Bus Error Status (Logic Reset (ERROR[1]_N))[23] = 0x0 dp - Uncorrectable Error / Data Poisoned (not detected)[22:21] = 0x0 hier[1:0] - Bus level (1st)[20:16] = 0x00 sev[4:0] - Bus Error Severity[15:8] = 0x00 type[7:0] - Transaction Type (unknown)[7] = 0x0 cc - Cache To Cache Transfer Error (did not occur)[6] = 0x1 eb - External Bus Error (occurred)                                       >>>>>>>[5] = 0x0 ib - Internal Bus Error (did not occur)[4:0] = 0x00 size[4:0] - Transaction Size (0 bytes)
External bus errorcore incoming - Logic Reset (ERROR[1]_N)
----- Analyzing Logical CPU 12(12) BUS_CHECK[0] MOD_CHECK_INFO ---------------
Event:Logical CPU 12(12): Skt 0, Core 6, Thread 0: BUS_CHECK[0]: An external buserror (Logic Reset (ERROR[1]_N)) was detected. This indicates that an errorwas detected outside the processor core. Review the analysis of the uncore,I/O subsystem and CEC to determine the source of the external error.
// You would need to focus on I/O subsystem (IO cards) and see if any of those are causing the reset (isolate one by one and observe system stability).// If still issue persists, then please log a support case with HPE Support Team for further assistance.
Thanks.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Re: Integrity RX2800 i6 MCA Reboot after Panic0626-06-2026
2Re: Integrity RX2800 i6 MCA Reboot after Panic0524-06-2026
3Re: Integrity RX2800 i6 MCA Reboot after Panic0526-06-2026
4Re: Integrity RX2800 i6 MCA Reboot after Panic0224-06-2026
5Re: Integrity RX2800 i6 MCA Reboot after Panic0325-06-2026
6Ynt: To solve Superdome2 Firmware mismatch0527-06-2026
7Opera 134 developer-3626-06-2026
8Re: After Power and Openreach Outage, half my devices can't connect to the internet0528-06-2026
9Linux 内核新补丁可提升大型 RAID5 阵列性能,最高增益 17%5727-06-2026
10Оператор Yota восстановил работу после сбоя0011-07-2019

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 5. Источник: community.hpe.com.