Did some experiments with blacklisting the module vs. running the rmmod command, and it revealed some interesting facts. But first, here’s some background: my computer is an LGGram and, as such, it suffers form this bug. (And no, it’s not specific to Ubuntu: Clear Linux suffers from it too, so it’s likely a kernel matter.) Two of the most annoying issues about this bug are (a) the syslog spamming and (b) the high CPU temperature.
Running the rmmod command fixes (a), but not (b), while blacklisting the module fixes them both, though at the expense of very high CPU utilization(!) that renders the whole system pretty much unusable. At this point, it looks to me that running the rmmod command is the best compromise in this matter.