es8316 i2c-ESSX8316:00: ASoC: error at soc_component_write_no_lock

[Jeffrey Walton]

Hi Everyone,

Attached is a dmesg for a Fedora 33 machine that went sideways tonight
after a 'dnf upgrade' and reboot. The machine is a low-end Cherry
Trail. It boots but something broke with the USB modem. The error
message is " Failed to open device /dev/ttyACM0: No such file or
directory".

The dmesg is full of:

[   14.970968] es8316 i2c-ESSX8316:00: ASoC: error at
soc_component_write_no_lock on i2c-ESSX8316:00: -121
[   14.976669] es8316 i2c-ESSX8316:00: ASoC: error at
soc_component_write_no_lock on i2c-ESSX8316:00: -121
[   15.008046] es8316 i2c-ESSX8316:00: ASoC: error at
soc_component_write_no_lock on i2c-ESSX8316:00: -121
[   15.008166] es8316 i2c-ESSX8316:00: ASoC: error at
soc_component_write_no_lock on i2c-ESSX8316:00: -121

What kernel component should this bug report be filed against?

Thanks in advance.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cherry-trail-dmesg.zip
Type: application/octet-stream
Size: 20228 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20201120/91f141ef/attachment-0001.obj>