Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2101426.1
Update Date:2016-03-10
Keywords:

Solution Type  Problem Resolution Sure

Solution  2101426.1 :   Sun Storage 2500-M2 Arrays: Controller Reboots due to (tNtbErrPolling): PANIC: PLX NTB  


Related Items
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: ST25xx
  •  




In this Document
Symptoms
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: oracle intent to inform partners
Created from <SR 3-11920037924>

Applies to:

Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

Sun Storage 2500-M2 Arrays running firmware version 07.84.47.10 or above can panic with an error similar to the one below. The excLogShow output of stateCaptureData.dmp file shows the following PANIC string:

(tNtbErrPolling): PANIC: PLX NTB Port 4 reg 0x00004a20 changed, original val 0x00001880, current val 0x00000880

Cause

The NTB panic was due to a correctable single bit PCI error. The firmware periodically scans the PCI registers to detect the bit flips. The single bit PCI error points to a hardware problem on the PCI switch of the controller. If a bit flip is detected, the respective controller will be rebooted with the below PANIC:

Executing excLogShow(0,0,0,0,0,0,0,0,0,0) on controller A:

================= EXCEPTION LOG =================
Serial number: SV22524408
Entry count: 3
Wrap-arounds: 0
First entry time:
Current date/time: DEC-24-2015 09:18:02 PM

---- Log Entry #1 DEC-23-2015 11:05:30 PM ----
12/23/15-23:07:11 (tNtbErrPolling): PANIC: PLX NTB Port 4 reg 0x00004a20 changed, original val 0x00001880, current val 0x00000880

Stack Trace for tNtbErrPolling:
0x0025ffac vxTaskEntry +0x5c : vkiTask (0x11000308)
0x0016844c vkiTask +0xec : ntbErrPolling ()
0x00143c20 ntbErrPolling+0x2a0: ntbRegCompare (0x4, 0xd80e68)
0x00143000 ntbRegCompare+0x100: _vkiCmnErr ()
0x00163544 _vkiCmnErr +0x104: 0x00163780 (0x585580, 0x4f8be0, 0xd7cb90)
0x00163b04 vkiLogShow +0x544: psvJobAdd (0x1648a0, 0xd7ccf0, 0, 0)
0x00148c04 psvJobAdd +0x64 : msgQSend ()
0x00402714 msgQSend +0x61c: taskUnlock ()

Also the following major events will be seen as shown below:

A:Thu Dec 24 08:06:24 JST 2015 : 7795 : 0/0/0 : 2606 : Notification : Controller : Tray.99.Controller.A : Start-of-day routine begun
A:Thu Dec 24 08:07:00 JST 2015 : 7825 : 0/0/0 : 2605 : Notification : Controller : Tray.99.Controller.A : Start-of-day routine completed

Solution

This PANIC string points to a hardware issue on the PCI switch of the controller. There is no firmware fix for this as it is a hardware issue.

  • No need to replace any hardware if this is the first occurrence.
  • If this issue continues to occur even if it is correctable, the controller should be replaced.

 

References

<BUG:22670068> - CONTROLLER REBOOTS DUE TO : PANIC: PLX NTB

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback