Hi, Peter!
Sorry, can't really help on debugging, but during my years of using
various brands of laptops (Dell, IBM Thinkpads, Lenovo, HP, Asus) and
OSes (Windows and Linux), my experience has been that the ability of
OSes to recover from suspended states has often (or always?) been
tripped up by whether or not the hardware device(s) involved could
properly recover from suspension.
I've had laptops that recovered fine from suspension, but their
installed wifi or networking hardware wouldn't recover. In some cases,
the only way to get the hardware to work again was to completely shut
down and do a cold start.
I think the hardware itself simply couldn't recover in a state that
allowed to OS to set it up properly again. I've also had OSes (Windows)
come out of suspend and simply assume the hardware was still set up as
it had been prior to suspending, without checking anything. This would
lead to unpredictable results when trying to use the device.
I haven't encountered that with Linux, but I rarely use suspend, so I
really don't know anything about Linux suspend and external hardware.
Maybe the Edirol needs some setup run when it powers on and Linux runs
that setup on a cold start but doesn't when coming out of suspension?
Since the Roland interface handles suspend while the Edirol doesn't,
maybe use the Roland instead?
Hope that helps! And maybe people on the list that know about this can
chime in.
On 2/16/24 04:02, Peter P. wrote:
Hi list,
I am replying to my own thread (see below), which is still unsolved as of
today.
I investigated further and experienced the same issue with an identical
second Edirol UA-24 soundcard on an identicel second X230 Thinkpad with
jackd2 on Debian and am experiencing the same jackd2 lockups.
However when using a Roland Rubix24 interface for comparison, jackd2
suspends and resumes fine.
Still looking for any pointers how to debug this further,
which are much appreciated!
best, Peter
* Peter P. <peterparker@xxxxxxxxxxxx> [2024-01-24 11:16]:
Hi,
Running jackd2 on an Edirol UA-25 USB interface as
jackd -t2000 -dalsa -r44100 -p512 -n2 -Xseq -D -Chw:UA25 -Phw:UA25 -i2 -o2
I can not get clients to connect after having resumed the computer from
"systemctl suspend".
Upon resuming, jackd reports
status error: No such device
ALSA: channel flush for playback failed (No such device)
JackAudioDriver::ProcessAsync: read error, stopping...
and hangs.
Trying to use mpv or puredata with this locked server then throw the same messages:
Cannot read socket fd = 13 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open mpv client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Nevertheless, qjackctl indicates a running server but throws
Cannot create new client
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err =
Connection timed out
Driver is not running
Cannot create new client
journalctl/dmesg show that the USB sound card is discovered as a new
device after resuming from the suspend state.
Stopping the server takes some time then, throwing:
ALSA: channel flush for playback failed (No such device)
Cannot stop driver
port deleted: UA-25:midi/playback_1
port deleted: UA-25:midi/capture_1
Released audio card Audio2
audio_reservation_finish
11:05:51.251 JACK was stopped
This problem does not exist when using jackd1.
The computers internal soundcard (intel-hda) survives resuming from
suspend with jackd2.
What can I try next?
Thanks!
Peter
--
David W. Jones
gnome@xxxxxxxxxxxxx
authenticity, honesty, community
http://dancingtreefrog.com
"My password is the last 8 digits of π."
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx
