Repository navigation
[BUG][logger] 'Inappropriate ioctl for device' when start logger to acquire error log #3446
Description
Describe the bug
Once our test failed, we will start sof-logger like this /usr/bin/sof-logger -l /etc/sof/sof-byt.ldc -o /home/ubuntu/sof-test/logs/check-alsabat/2020-09-18-16:49:54-26390/etrace.txt to acquire error log. and the logger conplained error: in logger_read(), fread(..., /sys/kernel/debug/sof/etrace) failed: Inappropriate ioctl for device(25)
check the failure in https://sof-ci.01.org/linuxpr/PR2452/build4513/devicetest/. We also observed this sof-logger failure with other test case failure.
Reproduction Rate
once test case failed, quite high rate to see this sof-logger issue.
Expected behavior
sof-logger should be able to collect error log.
Environment
Linux: 337674140e88 ASoC: SOF: topology: remove const in sizeof()
SOF: 646e562 travis: remove duplicate and deprecated host-build-all.sh
Activity
marc-hb commentedon Sep 22, 2020
This happens when a second, concurrent sof-logger is started and can be reproduced very easily with a one-line change, see example in thesofproject/sof-test#386
I think it has been like this since forever, it's just no one cared about sof-logger issues before: most errors were ignored and messages were silenced, see #3402 , thesofproject/sof-test#373 etc.
lgirdwood commentedon Sep 23, 2020
@slawblauciak could be a race or etrace is empty ?
slawblauciak commentedon Sep 23, 2020
@lgirdwood that looks like a kernel issue to me
ktrzcinx commentedon Sep 23, 2020
It doesn't look like like race, after quick reading the code, I looks rather like reading empty file error, but it doesn't fully fit bug description - I can add it to my buglist to fix
ktrzcinx commentedon Sep 24, 2020
@aiChaoSONG could you check if this patch could help: #3463 ?
slawblauciak commentedon Nov 4, 2020
@aiChaoSONG any updates?
marc-hb commentedon Nov 4, 2020
This could be a different issue but I noticed trying to access the
etracein suspend produces a confusing error message. More investigation / stress-testing is on my TODO list but keeps getting de-prioritized :-(aiChaoSONG commentedon Nov 5, 2020
@marc-hb If you mean the below error message, then we are all good, this message has nothing to do with any error, it is used to avoid an empty error trace, which will help us to detect if sof-logger error trace works. It is printed on purpose. check #3265
marc-hb commentedon Nov 5, 2020
No I meant some
ioctlor other linux system call error, forgot which one exactly sorry.aiChaoSONG commentedon Jan 11, 2022
This is not reproducible any more, let's close