2014-10-14, 11:16
Okay, as weird as it sounds... so far with 4.1.6, if the unit's asleep, sending an unused MCE command *before* sending POWER seems to have 100% cured the issue with the system randomly being non-responsive upon wakeup.
No idea why this is, but that doesn't mean I won't make a wild guess. I'm not certain how USB communications work in this case, but based on that one wacky log entry I'm almost wondering if the receiver is waiting to finish sending the concluding "_UP" command, but the system is going into sleep mode before this happens. Since sending POWER while the system is off does NOT actually transmit that to the PC, when the system does wake up the receiver finishes sending the last valid command it had - or at least the tail "_UP" portion, or perhaps some garbled data relating to it... which in turn occasionally locks up LIRC. However, sending a random command while the system is off causes the receiver to flush its buffer so this doesn't happen. I'm probably wrong.
Anyways, I guess the next step is to see if this fix continues to work in 4.2.1, or if the issue you linked earlier also applies (nothing that says I can't be seeing TWO problems at once!)
No idea why this is, but that doesn't mean I won't make a wild guess. I'm not certain how USB communications work in this case, but based on that one wacky log entry I'm almost wondering if the receiver is waiting to finish sending the concluding "_UP" command, but the system is going into sleep mode before this happens. Since sending POWER while the system is off does NOT actually transmit that to the PC, when the system does wake up the receiver finishes sending the last valid command it had - or at least the tail "_UP" portion, or perhaps some garbled data relating to it... which in turn occasionally locks up LIRC. However, sending a random command while the system is off causes the receiver to flush its buffer so this doesn't happen. I'm probably wrong.
Anyways, I guess the next step is to see if this fix continues to work in 4.2.1, or if the issue you linked earlier also applies (nothing that says I can't be seeing TWO problems at once!)