27 ms·

> It actually ran on the separate T1 CPU. Thanks for the clarification, I guess that didn't really change the result. Perhaps the Intel CPU was busy burning CP

by plqbfbv 1mo ago

> It actually ran on the separate T1 CPU. Thanks for the clarification, I guess that didn't really change the result. Perhaps the Intel CPU was busy burning CPU cycles and couldn't process interrupts properly, or because the communication was USB-based, it couldn't reliably deliver the required messages. The end result for me was that whenever I needed to use the ESC key, it wasn't available/visible or was unresponsive.

throw1234567891 1mo ago
Never had any problems with the touch bar. Until it died in a very flashy manner. Never been bothered by it.
- DANmode 26d ago
  Flashy LCD, or flashy smoke coming out? Out of curiosity.
runjake 1mo ago
The Tx SoCs communicated with the main system over Ethernet, IIRC, at least with the T2 SoC. The Tx SoCs themselves should have never locked up because there was a watchdog that would power cycle it when it became unresponsive.
- plqbfbv 1mo ago
  > The Tx SoCs communicated with the main system over Ethernet, IIRC, at least with the T2 SoC. The Wikipedia page linked in your other comment reports: "The T2 communicates with the host via a USB-attached Ethernet port.". So in the end it's really both, Ethernet AND USB. > The Tx SoCs themselves should have never locked up because there was a watchdog that would power cycle it when it became unresponsive. Perhaps I was reaching in the corner too far due to physical ESC muscle memory and it wasn't being registered by the touchbar, but regardless, being eth-over-usb means there was a server or kernel process listening on the Intel side to process those keys and raise them as interrupts or keyboard events. I guess sometimes, when some misbehaving application was already stealing all the Intel CPU capabilities or the kernel or some kernel extension had an issue, the touchbar could become unresponsive due to the load on the Intel side, with the T2 part being perfectly fine. And I did get at least a couple dozen times a completely frozen touchbar that left me with no choice but to reboot the system.

by plqbfbv 1mo ago

throw1234567891 1mo ago

Never had any problems with the touch bar. Until it died in a very flashy manner. Never been bothered by it.

DANmode 26d ago
Flashy LCD, or flashy smoke coming out? Out of curiosity.

runjake 1mo ago

The Tx SoCs communicated with the main system over Ethernet, IIRC, at least with the T2 SoC. The Tx SoCs themselves should have never locked up because there was a watchdog that would power cycle it when it became unresponsive.

plqbfbv 1mo ago
> The Tx SoCs communicated with the main system over Ethernet, IIRC, at least with the T2 SoC. The Wikipedia page linked in your other comment reports: "The T2 communicates with the host via a USB-attached Ethernet port.". So in the end it's really both, Ethernet AND USB. > The Tx SoCs themselves should have never locked up because there was a watchdog that would power cycle it when it became unresponsive. Perhaps I was reaching in the corner too far due to physical ESC muscle memory and it wasn't being registered by the touchbar, but regardless, being eth-over-usb means there was a server or kernel process listening on the Intel side to process those keys and raise them as interrupts or keyboard events. I guess sometimes, when some misbehaving application was already stealing all the Intel CPU capabilities or the kernel or some kernel extension had an issue, the touchbar could become unresponsive due to the load on the Intel side, with the T2 part being perfectly fine. And I did get at least a couple dozen times a completely frozen touchbar that left me with no choice but to reboot the system.