USB faults seen on T3 or T4 platforms during boot of Operating System
(Doc ID 1566851.1)
Last updated on FEBRUARY 26, 2021
Applies to:
SPARC T3-1 - Version All Versions and laterSPARC T4-1B - Version All Versions and later
SPARC T4-1 - Version All Versions and later
SPARC T3-1B - Version All Versions and later
SPARC T4-4 - Version All Versions and later
Information in this document applies to any platform.
Symptoms
To understand if your system hit this issue the following should be verified:
1. In /var/adm/messages file and in the ILOM event log:
- /var/adm/messages file:
...
Aug 21 13:32:58 xxxx mac: [ID 736570 kern.info] NOTICE: usbecm0 unregistered
Aug 21 13:32:58 xxxx genunix: [ID 408114 kern.info] /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/communications@3 (usbecm0) removed <<--!!
...
- ILOM event log:
...
1445 Wed Aug 21 13:33:25 2013 Audit Log minor host_root : Close Session : object = "/SP/session/type" : value = "shell" : success
1444 Wed Aug 21 13:33:23 2013 Audit Log minor root : Open Session : object = "/SP/session/type" : value = "shell" : success
1443 Wed Aug 21 13:33:02 2013 Fault Fault critical Fault detected at time = Wed Aug 21 13:33:01 2013. The suspect component:
/SYS/MB has fault.io.pciex.device-invreq with probability=10. Refer to http://www.sun.com/msg/FMD-8000-11 for details.
1442 Wed Aug 21 13:33:02 2013 Audit Log minor host_root : Close Session : object = "/SP/session/type" : value = "shell" : success
1441 Wed Aug 21 13:33:00 2013 Audit Log minor host_root : Set : object = "/SP/network/interconnect/state" : value = "disabled" : success
1440 Wed Aug 21 13:32:59 2013 Audit Log minor host_root : Set : object = "/SP/network/interconnect/state" : value = "disabled" : success <<--!!
...
- Often the interconnect later comes online again on its own (as in this example):
- messages file:
...
Aug 21 13:33:49 xxxx mac: [ID 469746 kern.info] NOTICE: usbecm0 registered
Aug 21 13:33:49 xxxx usba: [ID 912658 kern.info] USB 2.0 device (usb430,a4a2) operating at hi speed (USB 2.x) on USB 2.0 external hub: communications@3, usbecm0 at bus address 7
Aug 21 13:33:49 xxxx usba: [ID 349649 kern.info] SunMicro Virtual Eth Device
Aug 21 13:33:49 xxxx genunix: [ID 936769 kern.info] usbecm0 is /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/communications@3
Aug 21 13:33:49 xxxx genunix: [ID 408114 kern.info] /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/communications@3 (usbecm0) online <<--!!
...
ILOM event log:
...
1455 Wed Aug 21 13:33:40 2013 Audit Log minor host_root : Set : object = "/SP/network/interconnect/state" : value = "enabled" : success
...
- Check its status:
# /usr/sbin/ilomconfig list interconnect
Interconnect
============
State: enabled <----- enabled again
Type: USB Ethernet
SP Interconnect IP Address: 169.254.182.76
Host Interconnect IP Address: 169.254.182.77
Interconnect Netmask: 255.255.255.0
SP Interconnect MAC Address: 02:21:28:xx:xx:xx
Host Interconnect MAC Address: 02:21:28:xx:xx:xx
2.a. Solaris "#fmadm faulty" will show a PCIEX-8000-5Y Event
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
May 14 13:59:25 522a9f0f-2604-6185-ec77-f9d56ad78e5d PCIEX-8000-5Y Major
Problem Status : solved
Diag Engine : eft / 1.16
System
Manufacturer : unknown
Name : ORCL,SPARC-T4-4
Part_Number : unknown
Serial_Number : 1307AAA51A
Host_ID : 1237f298
----------------------------------------
Suspect 1 of 4 :
Fault class : fault.io.pci.device-invreq
Certainty : 25%
Affects : dev:////pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,2
Status : faulted but still in service
FRU
Location : "/SYS/MB"
Manufacturer : unknown
Name : unknown
Part_Number : 7048938
Revision : 02
Serial_Number : 465769T+1246H70A88
Chassis
Manufacturer : unknown
Name : ORCL,SPARC-T4-4
Part_Number : 31664288+1+1
Serial_Number : 9999ABC99A
Status : faulty
----------------------------------------
Suspect 2 of 4 :
Fault class : fault.io.pci.device-invreq
Certainty : 25%
Affects : dev:////pci@400/pci@1/pci@0/pci@7/pci@0/display@0
Status : faulted but still in service
FRU
Location : "/SYS/MB"
Manufacturer : unknown
Name : unknown
Part_Number : 7048938
Revision : 02
Serial_Number : 465769T+1246H70A88
Chassis
Manufacturer : unknown
Name : ORCL,SPARC-T4-4
Part_Number : 31664288+1+1
Serial_Number : 9999ABC99A
Status : faulty
----------------------------------------
Suspect 3 of 4 :
Fault class : fault.io.pci.device-invreq
Certainty : 25%
Affects : dev:////pci@400/pci@1/pci@0/pci@8/pci@0/usb@0
Status : faulted and taken out of service
FRU
Location : "/SYS/MB"
Manufacturer : unknown
Name : unknown
Part_Number : 7048938
Revision : 02
Serial_Number : 465769T+1246H70A88
Chassis
Manufacturer : unknown
Name : ORCL,SPARC-T4-4
Part_Number : 31664288+1+1
Serial_Number : 9999ABC99A
Status : faulty
----------------------------------------
Suspect 4 of 4 :
Fault class : fault.io.pci.device-invreq
Certainty : 25%
Affects : dev:////pci@400/pci@1/pci@0/pci@8/pci@0/usb@0,1
Status : faulted and taken out of service
FRU
Location : "/SYS/MB"
Manufacturer : unknown
Name : unknown
Part_Number : 7048938
Revision : 02
Serial_Number : 465769T+1246H70A88
Chassis
Manufacturer : unknown
Name : ORCL,SPARC-T4-4
Part_Number : 31664288+1+1
Serial_Number : 9999ABC99A
Status : faulty
2.b. In some cases, a FMD-8000-11 Event has been seen in the output of "#fmadm faulty"
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
May 14 13:59:25 <UUID> FMD-8000-11 Minor
Host : <hostname>
Platform : ORCL,SPARC-T4-4 Chassis_id :
Product_sn :
Fault class : fault.io.pciex.device-invreq max 10%
fault.io.pci.device-invreq max 10%
Affects : dev:////pci@400/pci@2/pci@0/pci@7/network@0,1
dev:////pci@400/pci@2/pci@0/pci@0/pci@0/display@0
dev:////pci@400/pci@2/pci@0/pci@f/pci@0/usb@0
dev:////pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,1
dev:////pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2
dev:////pci@400/pci@1/pci@0/pci@4/scsi@0
dev:////pci@400/pci@2/pci@0/pci@4/scsi@0
dev:////pci@400/pci@2/pci@0/pci@6/network@0
dev:////pci@400/pci@2/pci@0/pci@6/network@0,1
dev:////pci@400/pci@2/pci@0/pci@7/network@0
faulted but still in service
FRU : "/SYS/MB" (hc://:product-id=ORCL,SPARC-T4-4:product-sn=<Serial>:server-id=www01:chassis-id=<Serial>:serial=465769T+1242BW0LAD:part=7041481:revision=02/chassis=0/motherboard=0)
faulty
Description : A Solaris Fault Manager component generated a diagnosis for which
no message summary exists. Refer to
http://sun.com/msg/FMD-8000-11 for more information.
Response : The diagnosis has been saved in the fault log for examination by
Sun.
Impact : The fault log will need to be manually examined using fmdump(1M)
in order to determine if any human response is required.
Action : Use fmdump -v -u <EVENT-ID> to view the diagnosis result. Run
pkgchk -n SUNWfmd to ensure that fault management software is
installed properly.
Changes
These errors have been first observed after the upgrade of the System Firmware to 8.2.x or later, but they also can occur upon each boot of the Operating System,
also during the first boot after the installation of the Operating System. Also, these errors have been observed during normal operation of the OS.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |