Skip to content
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

Getting CheckSize and CheckRead error all the time #599

Open
main-- opened this issue Jun 12, 2020 · 5 comments
Open

Getting CheckSize and CheckRead error all the time #599

main-- opened this issue Jun 12, 2020 · 5 comments

Comments

@main--
Copy link

main-- commented Jun 12, 2020

Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error

I'm getting this output very often. Irregular time intervals, but on average once every two seconds or so.

I'm not experiencing any other issues, audio works just fine.

Any idea could be causing this error and how to deal with it?

@main--
Copy link
Author

main-- commented Jun 13, 2020

I found out that the errors go away if I remove the type multi capture device from my ALSA configuration. Given that this is an officially documented solution to combine multiple cards, this is still a problem though.

@main--
Copy link
Author

main-- commented Jun 15, 2020

FWIW I don't observe this problem with jack1.

@hugovangalen
Copy link

hugovangalen commented Sep 9, 2020

FWIW I am also having this issue on a type multi configuration to combine two USB 2.0 audio-interfaces. Audio appears to work fine though, but it generates many of such lines per second which probably waste useful CPU time.

ERROR: Unknown request 0
ERROR: CheckSize error size = -1 Size() = 4
ERROR: CheckRead error
ERROR: Unknown request 4294967295
ERROR: CheckSize error size = 32 Size() = 12
ERROR: CheckRead error
ERROR: CheckSize error size = -1 Size() = 4
ERROR: CheckRead error
ERROR: Unknown request 0
ERROR: CheckSize error size = 32 Size() = 12
ERROR: CheckRead error

I'm on Ubuntu 18.04.5 LTS with kernel 5.4.0-42-lowlatency #46~18.04.1-Ubuntu SMP PREEMPT Fri Jul 10 08:10:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux running jackdmp version 1.9.12.

It is probably not a coincidence that 4294967295 happens to be the integer value for 0xFFFFFFFF.

Note that I also observe Unknown request 0. So obviously, somehow, invalid values are generated somewhere and attempted to get processed.

Edited to add: With the latest development branch at the time of writing this, I observe the same errors. I also observed a crash:

ERROR: Abort!
ERROR: info.si_signo = 6
ERROR: info.si_errno = 0
ERROR: info.si_code  = -6 (unknown)
ERROR: info.si_addr  = 0x3e80000731a
ERROR: reg[00]       = 0x0000000000000000
ERROR: reg[01]       = 0x00007f919dde63a0
ERROR: reg[02]       = 0x0000000000000008
ERROR: reg[03]       = 0x0000000000000246
ERROR: reg[04]       = 0x00007f919db0a048
ERROR: reg[05]       = 0x00007f919db0a0b6
ERROR: reg[06]       = 0x0000000000000030
ERROR: reg[07]       = 0x00007ffdd236f3e0
ERROR: reg[08]       = 0x0000000000000002
ERROR: reg[09]       = 0x00007f919dde63a0
ERROR: reg[10]       = 0x00007f919cbeda38
ERROR: reg[11]       = 0x0000000000000000
ERROR: reg[12]       = 0x0000000000000000
ERROR: reg[13]       = 0x0000000000000000
ERROR: reg[14]       = 0x00007f919ca74f47
ERROR: reg[15]       = 0x00007f919dde63a0
ERROR: reg[16]       = 0x00007f919ca74f47
ERROR: reg[17]       = 0x0000000000000246
ERROR: reg[18]       = 0x002b000000000033
ERROR: reg[19]       = 0x0000000000000000
ERROR: reg[20]       = 0x0000000000000000
ERROR: reg[21]       = 0x0000000000005a07
ERROR: reg[22]       = 0x0000000000000000
ERROR: Stack trace:
ERROR:  1: 0x7f919ca74f47 <gsignal+199> (/lib/x86_64-linux-gnu/libc.so.6)
ERROR: End of stack trace

Edited to add more: If it doesn't crash, the development branch hangs quite often just playing back in Audacity. It appears less stable than the 1.9.12 version that Ubuntu 18.04 installs by default.

Edited to add even more: After updating to the latest QjackCtl it appears that the crashes and hangs stopped occurring. (To be clear, I am still seeing the CheckSize and CheckRead errors though.)

Another edit: Forget that last remark about the latest QjackCtl. Although it initially appeared more stable as I could work on an audio file for much longer -- but jackdbus eventually still locks up. :( Running jackd as a separate process also can lock it up without any output to standard out. Occasionally it crashes with the following message:

jackd: ../common/JackGraphManager.cpp:48: void Jack::JackGraphManager::AssertPort(jack_port_id_t): Assertion `port_index < fPortMax' failed.

@carlocaione
Copy link

Is still any definitive solution to this? I'm still getting this when using the jack (compiled from master) on a type multi alsa PCM.

@synthnassizer
Copy link

synthnassizer commented Apr 15, 2024

+1 issue for me as well.
I have been using a setup of 2 (same) sound cards - which however do not share the same clock.
It had been working find in the past (many) years but I started having this issue a few months ago.

ERROR: Unknown request 0
ERROR: CheckSize error size = -1 Size() = 4
ERROR: CheckRead error
ERROR: Unknown request 4294967295
ERROR: CheckSize error size = 32 Size() = 12
ERROR: CheckRead error
ERROR: CheckSize error size = -1 Size() = 4
ERROR: CheckRead error

where does this originate from ?

Jack finally reaches the assertion point

jackd: ../common/JackGraphManager.cpp:48: void Jack::JackGraphManager::AssertPort(jack_port_id_t): Assertion port_index < fPortMax' failed.`

and exits.

also on ubustu[studio] 18.04.6 with kernel
Linux audiosrv 4.15.0-213-lowlatency #224-Ubuntu SMP PREEMPT Mon Jun 19 14:03:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants