-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG][logger] 'Inappropriate ioctl for device' when start logger to acquire error log #3446
Comments
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. |
@slawblauciak could be a race or etrace is empty ? |
@lgirdwood that looks like a kernel issue to me |
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 |
@aiChaoSONG could you check if this patch could help: #3463 ? |
@aiChaoSONG any updates? |
This could be a different issue but I noticed trying to access the |
@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
|
No I meant some |
This is not reproducible any more, let's close |
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 conplainederror: 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
The text was updated successfully, but these errors were encountered: