On Fri, Jul 25, 2025 at 10:28 AM Jeremy Leonard <
[email protected]> wrote:
On Fri, Jul 25, 2025 at 7:21 AM John Paul Adrian Glaubitz < [email protected]> wrote:
Hi Jeremy,
On Fri, 2025-07-25 at 06:42 -0400, Jeremy Leonard wrote:
I was attempting a bare-metal install.
Could you test whether Solaris 11.4 CBE works fine on your T5240?
See:
https://www.oracle.com/de/solaris/solaris11/downloads/solaris-downloads.html >>
It's free for non-commercial use.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
I've downloaded 11.3 I'll work to install 11.3 this evening and report
back.
I think I may have hardware issues.
The install failed to boot completely for Solaris 11.3. I received an error:
SUNW-MSG-ID: SUNOS-8000-J0, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Sat Jul 26 01:33:17 UTC 2025
PLATFORM: SUNW,T5240, CSN: 11223344, HOSTNAME: solaris
SOURCE: eft, REV: 1.16
EVENT-ID: 63482a2a-4716-43c2-9a7a-b3fb99198607
DESC: The diagnosis engine encountered telemetry from the listed devices
for which it was unable to perform a diagnosis - no valid path to component
was found in ereport.io.pciex.tl.ptlp.
AUTO-RESPONSE: Error reports have been logged for examination.
IMPACT: Automated diagnosis and response for these events will not occur. REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this
event. Use 'fmdump -epV -u 63482a2a-4716-43c2-9a7a-b3fb99198607' to view
the unexpected telemetry. Please refer to the associated reference document
at
http://support.oracle.com/msg/SUNOS-8000-J0 for the latest service procedures and policies regarding this diagnosis.
SUNW-MSG-ID: SUN4V-8002-SP, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Sat Jul 26 01:33:18 UTC 2025
PLATFORM: SUNW,T5240, CSN: 11223344, HOSTNAME: solaris
SOURCE: cpumem-diagnosis, REV: 1.7
EVENT-ID: fe7d5e2f-77d7-40bb-8359-e16d74c53bc9
DESC: The error report generator has received input data that is
inconsistent or improperly formatted.
AUTO-RESPONSE: No automated response.
IMPACT: This error does not affect system operation. The error which could
not be reported may have more serious impact which cannot be determined. REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this
event. The system may need a firmware upgrade. Please retain the error log file. Please refer to the associated reference document at
http://support.oracle.com/msg/SUN4V-8002-SP for the latest service
procedures and policies regarding this diagnosis.
Jul 26 01:33:28 solaris in.routed[1122]: route 0.0.0.0/24 --> 0.0.0.0
nexthop is not directly connected
I was able to break out of the install and get a shell.
From there I ran:
fmadm faulty
--------------- ------------------------------------ --------------
---------
TIME EVENT-ID MSG-ID
SEVERITY
--------------- ------------------------------------ --------------
---------
Jul 26 01:33:18 fe7d5e2f-77d7-40bb-8359-e16d74c53bc9 SUN4V-8002-SP Major
Problem Status : open
Diag Engine : cpumem-diagnosis / 1.7
System
Manufacturer : unknown
Name : SUNW,T5240
Part_Number : unknown
Serial_Number : 11223344
Host_ID : 85b10ec0
----------------------------------------
Suspect 1 of 1 :
Problem class : defect.fw.generic-sparc.erpt-gen
Certainty : 100%
Resource
FMRI : "hc://:chassis-mfg=unknown:chassis-name=SUNW,T5240:chassis-part=unknown:chassis-serial=BDL10502C2:fru-serial=1005LCB-1046DK00F7:fru-part=540790804/motherboard=0"
Manufacturer : unknown
Name : unknown
Part_Number : 540790804
Revision : unknown
Serial_Number : 1005LCB-1046DK00F7
Chassis
Manufacturer : unknown
Name : SUNW,T5240
Part_Number : unknown
Serial_Number : BDL10502C2
Status : faulted but still in service
Description : The error report generator has received input data that is
inconsistent or improperly formatted.
Response : No automated response.
Impact : This error does not affect system operation. The error which
could not be reported may have more serious impact which
cannot
be determined.
Action : Use 'fmadm faulty' to provide a more detailed view of this
event.
The system may need a firmware upgrade. Please retain the
error
log file. Please refer to the associated reference document at
http://support.oracle.com/msg/SUN4V-8002-SP for the latest
service procedures and policies regarding this diagnosis.
--------------- ------------------------------------ --------------
---------
TIME EVENT-ID MSG-ID
SEVERITY
--------------- ------------------------------------ --------------
---------
Jul 26 01:33:17 63482a2a-4716-43c2-9a7a-b3fb99198607 SUNOS-8000-J0 Major
Problem Status : open
Diag Engine : eft / 1.16
System
Manufacturer : unknown
Name : SUNW,T5240
Part_Number : unknown
Serial_Number : 11223344
Host_ID : 85b10ec0
----------------------------------------
Suspect 1 of 2 :
Problem class : defect.sunos.eft.unexpected_telemetry
Certainty : 50%
Resource
FMRI : "hc:///motherboard=0/hostbridge=0/pciexrc=1"
Manufacturer : unknown
Name : unknown
Part_Number : unknown
Revision : unknown
Serial_Number : unknown
Chassis
Manufacturer : unknown
Name : unknown
Part_Number : unknown
Serial_Number : unknown
Status : faulted but still in service ----------------------------------------
Suspect 2 of 2 :
Problem class : fault.sunos.eft.unexpected_telemetry
Certainty : 50%
Resource
FMRI : "hc:///motherboard=0/hostbridge=0/pciexrc=1"
Manufacturer : unknown
Name : unknown
Part_Number : unknown
Revision : unknown
Serial_Number : unknown
Chassis
Manufacturer : unknown
Name : unknown
Part_Number : unknown
Serial_Number : unknown
Status : faulted but still in service
Description : The diagnosis engine encountered telemetry from the listed
devices for which it was unable to perform a diagnosis - no
valid
path to component was found in ereport.io.pciex.tl.ptlp.
Response : Error reports have been logged for examination.
Impact : Automated diagnosis and response for these events will not
occur.
Action : Use 'fmadm faulty' to provide a more detailed view of this
event.
Use 'fmdump -epV -u 63482a2a-4716-43c2-9a7a-b3fb99198607' to
view
the unexpected telemetry. Please refer to the associated
reference document at
http://support.oracle.com/msg/SUNOS-8000-J0
for the latest service procedures and policies regarding this
diagnosis.
So this probably isn't the proper place to continue with this since this
list is for Debian. But I don't really know where to go from here. I'm just trying to start with Sun/Sparc things.
--
Jeremy Leonard
[email protected]
Cell: (517) 285-8309
<div dir="ltr"><div dir="ltr">On Fri, Jul 25, 2025 at 10:28 AM Jeremy Leonard <<a href="mailto:
[email protected]">
[email protected]</a>> wrote:</div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 25, 2025 at 7:21 AM John Paul Adrian Glaubitz <<a
href="mailto:
[email protected]" target="_blank">
[email protected]</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Jeremy,<br>
On Fri, 2025-07-25 at 06:42 -0400, Jeremy Leonard wrote:<br>
> I was attempting a bare-metal install.<br>
Could you test whether Solaris 11.4 CBE works fine on your T5240?<br>