thesofproject
CML: RT711 jack removal error thrown in check-kmod-load-unload-after-playback.
Found while testing unrelated changes for RT715
2024-03-28 19:12:43 UTC [ERROR] Caught kernel log error
===========================>>
[ 445.264185] kernel: Jack removal in rt711_headset_detect
[ 447.207724] kernel: Jack removal in rt711_headset_detect
[ 450.588717] kernel: Jack removal in rt711_headset_detect
<<===========================
2024-03-28 19:12:43 UTC Sub-Test: [INFO] Starting func_exit_handler(1)
2024-03-28 19:12:43 UTC Sub-Test: [ERROR] Starting func_exit_handler(), exit status=1, FUN\
CNAME stack:
2024-03-28 19:12:43 UTC Sub-Test: [ERROR] main() @ /root/sof-test/test-case/check-playb\
ack.sh
2024-03-28 19:12:44 UTC Sub-Test: [INFO] Starting /usr/local/bin/sof-logger -l /lib/firmwa\
re/intel/sof/sof-cml.ldc > /root/sof-test/logs/check-kmod-load-unload-after-playback/2024-\
03-28-14:11:41-13984/etrace.txt &
2024-03-28 19:12:46 UTC Sub-Test: [INFO] pkill -TERM sof-logger
2024-03-28 19:12:47 UTC Sub-Test: [INFO] nlines=3 /root/sof-test/logs/check-kmod-load-unlo\
ad-after-playback/2024-03-28-14:11:41-13984/etrace.txt
2024-03-28 19:12:47 UTC Sub-Test: [INFO] Test Result: FAIL!
2024-03-28 19:12:47 UTC Sub-Test: [ERROR] aplay check failed
2024-03-28 19:12:47 UTC Sub-Test: [INFO] Starting func_exit_handler(1)
2024-03-28 19:12:47 UTC Sub-Test: [ERROR] Starting func_exit_handler(), exit status=1, FUN\
CNAME stack:
2024-03-28 19:12:47 UTC Sub-Test: [ERROR] die() @ /root/sof-test/test-case/../case-lib/\
lib.sh
2024-03-28 19:12:47 UTC Sub-Test: [ERROR] main() @ /root/sof-test/test-case/check-kmod-\
load-unload-after-playback.sh:95
2024-03-28 19:12:47 UTC Sub-Test: [INFO] Test Result: FAIL!
@shumingfan any idea what this could be? There was no headphone or headset connected....
@plbossart It is weird. The pin sense detected the jack inserted first, then checked the result of jack type detection. During the type detection, the pin sense detected the jack unplugged. Could you share the whole log?
@shumingfan unfortunately I saw this only at the end of my tests and the dmesg log was gone. I haven't been able to reproduce it for now. The hardware is an early prototype that's over 3 years old so it's possible that it's not quite functional either.
I'll keep this open and try to see if this re-occurs.