Re: could not start jack - already registered problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 26.04.2013 00:08, schrieb Hartmut Noack:
> Am 25.04.2013 20:57, schrieb david:
>> On 04/25/2013 06:32 AM, Markus Seeber wrote:
>>> On 04/25/2013 03:33 PM, Hartmut Noack wrote:
>>>> Am 25.04.2013 13:27, schrieb Patrick Shirkey:
>>>>> On Thu, April 25, 2013 8:14 pm, Hartmut Noack wrote:
>>>>>> Am 25.04.2013 09:56, schrieb Patrick Shirkey:
>>>>>>> On Thu, April 25, 2013 4:40 pm, Hartmut Noack wrote:
>>>>>>>> Am 24.04.2013 17:15, schrieb Johannes Kroll:
>>>>>>>>> On Wed, 24 Apr 2013 16:10:56 +0200
>>>>>>>>> Hartmut Noack <zettberlin@xxxxxxxxxxx> wrote:
>>>>>>>>>
>>>>>>>>>> Am 24.04.2013 15:51, schrieb Len Ovens:
>>>>>>>>>>> On Wed, April 24, 2013 6:26 am, Hartmut Noack wrote:
>>>>>>>>>>>> Hello,
>>>>>>>>>>>>
>>>>>>>>>>>> I run KXStudio on Ubuntu 12.10 on a Lenovo Ideapad with a MAudio
>>>>>>>>>>>> Mobile
>>>>>>>>>>>> Pre USB1 interface.
>>>>>>>>>>>>
>>>>>>>>>>>> Normaly all this works near perfection but there is a problem
>>>>>>>>>>>> starting
>>>>>>>>>>>> Jack:
>>>>>>>>>>>>
>>>>>>>>>>>> Tue Apr 23 09:58:52 2013: ERROR: cannot register object path
>>>>>>>>>>>> "/org/freedesktop/ReserveDevice1/Audio2": A handler is already
>>>>>>>>>>>> registered for /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>>>>>> Tue Apr 23 09:58:52 2013: ERROR: Failed to acquire device name :
>>>>>>>>>>>> Audio2
>>>>>>>>>>>> error : A handler is already registered for
>>>>>>>>>>>> /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>>>>> Ok, so what application already has the audio port? Are you
>>>>>>>>>>> running
>>>>>>>>>>> an
>>>>>>>>>>> audio or video player? Have you been using a web browser that was
>>>>>>>>>>> seeing a
>>>>>>>>>>> video or just hit a page with video adds?
>>>>>>>>>>>
>>>>>>>>>>> To put it another way, does this problem show up right after a
>>>>>>>>>>> fresh
>>>>>>>>>>> login?
>>>>>>>>>> Exactly: after a fresh login.
>>>>>>>>>>
>>>>>>>>>>> or only after having used the system for a while. What does your
>>>>>>>>>>> desktop use for most of it's non-jack audio output?
>>>>>>>>>> Before I do anything else, I check if Jack is running. Browser,
>>>>>>>>>> Skype
>>>>>>>>>> and the like use Pulse Jack sink, so I let Cadence start pulse-jack
>>>>>>>>>> after starting Jack.
>>>>>>>>> The command "lsof /dev/snd/pcm*" should show a list of commands
>>>>>>>>> which
>>>>>>>>> are using any sound cards. Try it the next time the problem shows
>>>>>>>>> up.
>>>>>>>> Right now I have go the situation:
>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>
>>>>>>>> zettberlin@zettberlin-Lenovo-U410:~$ lsof /dev/snd/pcm*
>>>>>>>> zettberlin@zettberlin-Lenovo-U410:~$ cat /proc/asound/cards
>>>>>>>>   0 [Loopback       ]: Loopback - Loopback
>>>>>>>>                        Loopback 1
>>>>>>>>   1 [PCH            ]: HDA-Intel - HDA Intel PCH
>>>>>>>>                        HDA Intel PCH at 0xeb610000 irq 46
>>>>>>>>   2 [MobilePre      ]: USB-Audio - MobilePre
>>>>>>>>                        M Audio MobilePre at usb-0000:00:14.0-2, full
>>>>>>>> speed
>>>>>>>>
>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>
>>>>>>>> Thu Apr 25 08:29:57 2013: JACK server starting in realtime mode with
>>>>>>>> priority 10
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: cannot register object path
>>>>>>>> "/org/freedesktop/ReserveDevice1/Audio2": A handler is already
>>>>>>>> registered for /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: Failed to acquire device name :
>>>>>>>> Audio2
>>>>>>>> error : A handler is already registered for
>>>>>>>> /org/freedesktop/ReserveDevice1/Audio2
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: Audio device hw:MobilePre,0
>>>>>>>> cannot be
>>>>>>>> acquired...
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: Cannot initialize driver
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: JackServer::Open failed with -1
>>>>>>>> Thu Apr 25 08:29:57 2013: ERROR: Failed to open server
>>>>>>>> Thu Apr 25 08:30:04 2013: ------------------
>>>>>>>> Thu Apr 25 08:30:04 2013: Controller activated. Version 1.9.9.5
>>>>>>>> (unknown) built on Sat Dec 22 19:50:40 2012
>>>>>>>> Thu Apr 25 08:30:04 2013: Loading settings from
>>>>>>>> "/home/zettberlin/.config/jack/conf.xml" using expat_2.1.0 ...
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'engine':'driver':'(null)'
>>>>>>>> to value "alsa"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'engine':'realtime':'(null)'
>>>>>>>> to value "true"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'engine':'verbose':'(null)'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'engine':'client-timeout':'(null)' to value "1000"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'device'
>>>>>>>> to
>>>>>>>> value "hw:2"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'capture'
>>>>>>>> to value "hw:MobilePre,0"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'playback'
>>>>>>>> to value "hw:MobilePre,0"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'rate' to
>>>>>>>> value "48000"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'period'
>>>>>>>> to
>>>>>>>> value "256"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'nperiods'
>>>>>>>> to value "3"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'hwmon' to
>>>>>>>> value "false"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'hwmeter'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'duplex'
>>>>>>>> to
>>>>>>>> value "true"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'softmode'
>>>>>>>> to value "true"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'monitor'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'dither'
>>>>>>>> to
>>>>>>>> value "n"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter 'drivers':'alsa':'shorts'
>>>>>>>> to
>>>>>>>> value "true"
>>>>>>>> Thu Apr 25 08:30:04 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'midi-driver' to value "seq"
>>>>>>>> Thu Apr 25 08:30:04 2013: Listening for D-Bus messages
>>>>>>>> Thu Apr 25 08:30:04 2013: Starting jack server...
>>>>>>>> Thu Apr 25 08:30:04 2013: JACK server starting in realtime mode with
>>>>>>>> priority 10
>>>>>>>> Thu Apr 25 08:30:05 2013: Acquired audio card Audio2
>>>>>>>> Thu Apr 25 08:30:05 2013: creating alsa driver ...
>>>>>>>> hw:MobilePre,0|hw:MobilePre,0|256|3|48000|0|0|nomon|swmeter|soft-mode|16bit
>>>>>>>>
>>>>>>>> Thu Apr 25 08:30:05 2013: Using ALSA driver USB-Audio running on
>>>>>>>> card 2
>>>>>>>> - M Audio MobilePre at usb-0000:00:14.0-2, full speed
>>>>>>>> Thu Apr 25 08:30:05 2013: configuring for 48000Hz, period = 256
>>>>>>>> frames
>>>>>>>> (5.3 ms), buffer = 3 periods
>>>>>>>> Thu Apr 25 08:30:05 2013: ALSA: final selected sample format for
>>>>>>>> capture: 16bit little-endian
>>>>>>>> Thu Apr 25 08:30:05 2013: ALSA: use 3 periods for capture
>>>>>>>> Thu Apr 25 08:30:05 2013: ERROR: ALSA: cannot set hardware parameters
>>>>>>>> for capture
>>>>>>>> Thu Apr 25 08:30:05 2013: ERROR: ALSA: cannot configure capture
>>>>>>>> channel
>>>>>>>> Thu Apr 25 08:30:05 2013: ERROR: Cannot initialize driver
>>>>>>>> Thu Apr 25 08:30:05 2013: ERROR: JackServer::Open failed with -1
>>>>>>>> Thu Apr 25 08:30:05 2013: ERROR: Failed to open server
>>>>>>>> ##############################################################
>>>>>>>> Now I unplug the Mobile Pre....
>>>>>>>> Replug it
>>>>>>>> And:
>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>
>>>>>>>> Thu Apr 25 08:34:19 2013: ------------------
>>>>>>>> Thu Apr 25 08:34:19 2013: Controller activated. Version 1.9.9.5
>>>>>>>> (unknown) built on Sat Dec 22 19:50:40 2012
>>>>>>>> Thu Apr 25 08:34:20 2013: Loading settings from
>>>>>>>> "/home/zettberlin/.config/jack/conf.xml" using expat_2.1.0 ...
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'engine':'driver':'(null)'
>>>>>>>> to value "alsa"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'engine':'realtime':'(null)'
>>>>>>>> to value "true"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'engine':'verbose':'(null)'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'engine':'client-timeout':'(null)' to value "1000"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'device'
>>>>>>>> to
>>>>>>>> value "hw:2"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'capture'
>>>>>>>> to value "hw:MobilePre,0"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'playback'
>>>>>>>> to value "hw:MobilePre,0"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'rate' to
>>>>>>>> value "48000"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'period'
>>>>>>>> to
>>>>>>>> value "256"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'nperiods'
>>>>>>>> to value "3"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'hwmon' to
>>>>>>>> value "false"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'hwmeter'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'duplex'
>>>>>>>> to
>>>>>>>> value "true"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'softmode'
>>>>>>>> to value "true"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'monitor'
>>>>>>>> to value "false"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'dither'
>>>>>>>> to
>>>>>>>> value "n"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter 'drivers':'alsa':'shorts'
>>>>>>>> to
>>>>>>>> value "true"
>>>>>>>> Thu Apr 25 08:34:20 2013: setting parameter
>>>>>>>> 'drivers':'alsa':'midi-driver' to value "seq"
>>>>>>>> Thu Apr 25 08:34:20 2013: Listening for D-Bus messages
>>>>>>>> Thu Apr 25 08:34:20 2013: Starting jack server...
>>>>>>>> Thu Apr 25 08:34:20 2013: JACK server starting in realtime mode with
>>>>>>>> priority 10
>>>>>>>> Thu Apr 25 08:34:20 2013: Acquired audio card Audio2
>>>>>>>> Thu Apr 25 08:34:20 2013: creating alsa driver ...
>>>>>>>> hw:MobilePre,0|hw:MobilePre,0|256|3|48000|0|0|nomon|swmeter|soft-mode|16bit
>>>>>>>>
>>>>>>>> Thu Apr 25 08:34:20 2013: Using ALSA driver USB-Audio running on
>>>>>>>> card 2
>>>>>>>> - M Audio MobilePre at usb-0000:00:14.0-2, full speed
>>>>>>>> Thu Apr 25 08:34:20 2013: configuring for 48000Hz, period = 256
>>>>>>>> frames
>>>>>>>> (5.3 ms), buffer = 3 periods
>>>>>>>> Thu Apr 25 08:34:20 2013: ALSA: final selected sample format for
>>>>>>>> capture: 16bit little-endian
>>>>>>>> Thu Apr 25 08:34:20 2013: ALSA: use 3 periods for capture
>>>>>>>> Thu Apr 25 08:34:20 2013: ALSA: final selected sample format for
>>>>>>>> playback: 16bit little-endian
>>>>>>>> Thu Apr 25 08:34:20 2013: ALSA: use 3 periods for playback
>>>>>>>> Thu Apr 25 08:34:20 2013: port created: Midi-Through:midi/playback_1
>>>>>>>> Thu Apr 25 08:34:20 2013: port created: Midi-Through:midi/capture_1
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:capture_1'
>>>>>>>> Thu Apr 25 08:34:20 2013: New client 'system' with PID 0
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:capture_2'
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:playback_1'
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port 'system:playback_2'
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port
>>>>>>>> 'system:midi_capture_1'
>>>>>>>> Thu Apr 25 08:34:20 2013: graph reorder: new port
>>>>>>>> 'system:midi_playback_1'
>>>>>>>> ################################################################
>>>>>>>>
>>>>>>>> Please, people! Is there nobody out there who could say, what is
>>>>>>>> registering the Device? I guess, it has to do with dbus but I really
>>>>>>>> would like to jump straight to the core of the problem, learning all
>>>>>>>> mysteries of dbus/freedesktop/Jackdbus whatever is not an option for
>>>>>>>> me.
>>>>>>>> So if anybody could point me to that spurious registering-process it
>>>>>>>> would be most appreciated :-)
>>>>>>>>
>>>>>>>
>>>>>>> You might have better luck with this one on the PA mailing list.
>>>>>> So you suspect PA (and not dbus) to be the registering spectre?
>>>>>>
>>>>>> If I remember correctly I have tried some PA-voodoo also. Such as
>>>>>> killall -9 pulseaudio. But to no avail.
>>>>>>
>>>>>> Anyway thanks for the hint: I will try once more to find out,
>>>>>> whether PA
>>>>>> has the custom to "register" handlers for
>>>>>> /org/freedesktop/ReserveDevice1/Audio2
>>>>>>
>>>>>
>>>>> You can try adding
>>>>>
>>>>>    autospawn = no
>>>> This is in the file already, guess KXStudio does it automagically. And
>>>> it looks like it works, PA never starts automatically and it does not
>>>> respawn as I kill it.
>>>>
>>>> In fact I do not believe, that the problem is directly related to
>>>> pulse...
>>>>
>>>>> to
>>>>>
>>>>>     ~/.pulse/client.conf
>>>>>
>>>>>
>>>>> This is reminiscent of the other pulse bug.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Patrick Shirkey
>>>>> Boost Hardware Ltd
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>> Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
>>>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>>>
>>> I stumbled over the same issue a while ago but i can't reproduce the
>>> exact issue at the moment. I noticed, you are using Skype at the same
>>> time? Actually Skype doesn't support Jack and tries to do strange stuff
>>> sometimes, which inevitably breaks things on my system, because it
>>> aggressively tries to obtain access to the audio card somehow. The only
>>> way i discovered to free the device, is to stop Skype, start pulse
>>> audio, and kill pulseaudio afterwards. I try to avoid Skype now as much
>>> as possible, when i am Using Jack, because i couldn't get it working in
>>> a reliable way with the pulseaudio bridge.
>>> Basically i guess Skype is causing you problems.
>>
>> Or it's Pulse causing the problems. I don't use either Skype or Pulse.
> 
> I have found a hint now, that though pulseaudio is not directly
> responsible, something that comes from the pulse-package *could* be
> involved:
> http://git.0pointer.de/?p=reserve.git;a=blob;f=reserve.txt
> 
> Here we have the ghastly ReserverDevice1 thing.
> 
> As I read this, the problem is caused by 2 things:
> 
> 1.) the priority of the process, that tries to start Jack is lower than
> the one that has a grip upon the device at startup. How this priority is
> exactly set I do not know, I have raised the realtime-priority for Jack
> from 10 to 66 - simply this is the only whatever priority I see a way to
> set.
> 
> 2.) Lennart Poettering recommends to spawn a usefull message that could
> help the user to find out, what is happening:
> 
> Optionally the owner of the device access may export a few
>  172         properties with a bit of descriptive information about
>  173         itself. This is supposed to be useful to show a nice message
>  174         to the user: "Application %s is blocking device %s. Please
>  175         close this application or make sure it closes the access to
>  176         that device." with ApplicationName and  ApplicationDeviceName
>  177         filled in.
> 
> whoever is in charge have chosen just to spawn:
> 
> "A handler is already registered"
> 
> which have made me search for about 3 days now only to find the
> *potential* reason.

Now after restart, Jack cannot start with the higher priority either.


:~$ jack_control status
--- status
stopped


PA is *not* running:

:~$ paplay jack_capture_01.wav
Verbindungsfehler: Verbindung verweigert
pa_context_new() fehlgeschlagen: Verbindung verweigert

(Verbindungsfehler is basically: Connection failed)

:~$ pavucontrol
(pavucontrol:2891): Gtk-CRITICAL **: gtk_main_quit: assertion
`main_loops != NULL' failed

And it cannot start:

:~$ pulseaudio
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
(argument: "device_id="2" name="usb-M_Audio_MobilePre-00-MobilePre"
card_name="alsa_card.usb-M_Audio_MobilePre-00-MobilePre"
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
initialization failed.
W: [pulseaudio] module-udev-detect.c: Tried to configure
/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/sound/card2
(alsa_card.usb-M_Audio_MobilePre-00-MobilePre) more often than 5 times
in 10s



Nobody admits to have a grip on any soundcard:

:~$ lsof /dev/snd/*
COMMAND  PID       USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
kded4   2261 zettberlin   24u   CHR 116,15      0t0 8948 /dev/snd/controlC1
kded4   2261 zettberlin   26u   CHR  116,9      0t0 1739 /dev/snd/controlC2
kmix    2552 zettberlin   12u   CHR 116,15      0t0 8948 /dev/snd/controlC1
kmix    2552 zettberlin   17u   CHR  116,9      0t0 1739 /dev/snd/controlC2

These are just controls... the pcm interfaces are clean.

OK, so I un/replug again....

:~$ tail -f /var/log/syslog
Apr 26 09:20:09 zettberlin-Lenovo-U410 kernel: [ 1252.495471] usb 3-2:
USB disconnect, device number 2
Apr 26 09:20:09 zettberlin-Lenovo-U410 kernel: [ 1252.498259] xhci_hcd
0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep
ffff88021eab1c40
Apr 26 09:20:09 zettberlin-Lenovo-U410 kernel: [ 1252.498269] xhci_hcd
0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep
ffff88021eab1c80
Apr 26 09:20:34 zettberlin-Lenovo-U410 kernel: [ 1277.213574] usb 3-2:
new full-speed USB device number 5 using xhci_hcd
Apr 26 09:20:34 zettberlin-Lenovo-U410 kernel: [ 1277.799954] usb 3-2:
New USB device found, idVendor=0763, idProduct=200f
Apr 26 09:20:34 zettberlin-Lenovo-U410 kernel: [ 1277.799965] usb 3-2:
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 26 09:20:34 zettberlin-Lenovo-U410 kernel: [ 1277.799971] usb 3-2:
Product: MobilePre
Apr 26 09:20:34 zettberlin-Lenovo-U410 kernel: [ 1277.799976] usb 3-2:
Manufacturer: M Audio
Apr 26 09:20:34 zettberlin-Lenovo-U410 mtp-probe: checking bus 3, device
5: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Apr 26 09:20:34 zettberlin-Lenovo-U410 mtp-probe: bus: 3, device: 5 was
not an MTP device

Now I try to start Jack using Cadence again:

Apr 26 09:22:18 zettberlin-Lenovo-U410 rtkit-daemon[2169]: Successfully
made thread 3046 of process 3046 (n/a) owned by '1000' high priority at
nice level -11.
Apr 26 09:22:18 zettberlin-Lenovo-U410 rtkit-daemon[2169]: Supervising 1
threads of 1 processes of 1 users.
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
pid.c: Stale PID file, overwriting.
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
sink.c: Default and alternate sample rates are the same.
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
module-jack-sink.c: JACK error >Cannot use real-time scheduling
(RR/61)(1: Die Operation ist nicht erlaubt)<
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
module-jack-sink.c: JACK error >JackClient::AcquireSelfRealTime error<
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
source.c: Default and alternate sample rates are the same.
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
module-jack-source.c: JACK error >Cannot use real-time scheduling
(RR/61)(1: Die Operation ist nicht erlaubt)<
Apr 26 09:22:18 zettberlin-Lenovo-U410 pulseaudio[3046]: [pulseaudio]
module-jack-source.c: JACK error >JackClient::AcquireSelfRealTime error<


:~$ uname -a
Linux zettberlin-Lenovo-U410 3.5.0-26-lowlatency #28-Ubuntu SMP PREEMPT
Tue Mar 19 10:32:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
:~$ groups
audio dip video plugdev (and others)
:~$ cat /etc/security/limits.d/audio.conf
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#

@audio   -  rtprio     95
@audio   -  memlock    unlimited

So still I do not know, whatever is registering that handler on the
Reserve Device defined by the PA-package....

Anyone?


> 
> And still I am far from a sane solution....
> 
> best regards and thank you all for your help.
> 
> HZN
> 
> 
>>
> 
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
> http://lists.linuxaudio.org/listinfo/linux-audio-user
> 

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user




[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux