1
User Zone / Re: Calling for gaming experiences
« on: July 28, 2024, 07:00:14 pm »
mkxp-z has official ppc64le binaries now. That's kinda cool. If there exist any other games with official ppc64le binaries, I haven't seen them.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
The 18c & 22c parts are "paired" meaning 2 SMT4 cores share the same L2 & L3, unlike the 4c and 8c which are "unpaired" meaning each core gets the full L2 and L3 to itself. This is not the same as "fused" (i.e. SMT8 cores) but it is quite likely that the fix will also work for "paired" cores as presumably the issue is sharing cacheable/non-cacheable pathways. Good luck!
I think you're right about the terminology, but yeah, I doubt the IBM docs draw a distinction since those docs are exclusively written for SMT8 users.
I've successfully built a PNOR with IBM's patch; it installed without major issues (I accidentally hosed things the first time I installed it due to the BMC running out of RAM -- protip, don't put multiple PNOR images in OpenBMC /tmp/ -- but power-cycling the BMC fixed that). So far it seems stable, I'll be running it for the next month or so to see if any checkstops happen.
Would you be able to provide more details on which patch? Many thanks
The 18c & 22c parts are "paired" meaning 2 SMT4 cores share the same L2 & L3, unlike the 4c and 8c which are "unpaired" meaning each core gets the full L2 and L3 to itself. This is not the same as "fused" (i.e. SMT8 cores) but it is quite likely that the fix will also work for "paired" cores as presumably the issue is sharing cacheable/non-cacheable pathways. Good luck!
1080p was never an issue. It's about 1200p.
I believe that all OpenPOWER/OPAL-based systems use SMT4 cores, not SMT8 (i.e. "fused") cores. So that may mean you aren't seeing the same problem.
Do you get the same fault callout?
HIPER/Pervasive: A problem was fixed for a processor core checkstop with SRC BC70E540 logged with Signature Description " ex(n0p1c4) (NCUFIR[11]) NCU no response to snooped TLBIE". This problem is intermittent and random but occurs with relatively high frequency for certain workloads. The trigger for the failure is one core of a fused core pair going into a stopped state while the other core of the pair continues running.
Is Wayland still limited to 1024x768 on the ASPEED?
No, probably not. Ignoring endianness for the sake of discussion, while Cell does have a conventional PowerPC core as the PPE, the SPEs are unique and so is the EIB connecting them.