Bug#745550: pulseaudio: analog output not appearing in list of devices

2014-06-05 Thread Felipe Sateler
Hi Andrej,

On Wed, Apr 23, 2014 at 5:03 PM, Andrej Herich error...@gmail.com wrote:
 On 23 April 2014 21:49, Felipe Sateler fsate...@debian.org wrote:

 Thanks. Indeed it looks like pulseaudio is only seeing one device.
 Could you please post the output of the following commands:

 cat /proc/asound/cards


  0 [PCH]: HDA-Intel - HDA Intel PCH
   HDA Intel PCH at 0xf7d3 irq 49

 cat /proc/asound/devices


   1:: sequencer
   2: [ 0- 7]: digital audio playback
   3: [ 0- 3]: digital audio playback
   4: [ 0- 2]: digital audio capture
   5: [ 0- 1]: digital audio playback
   6: [ 0- 0]: digital audio playback
   7: [ 0- 0]: digital audio capture
   8: [ 0- 3]: hardware dependent
   9: [ 0- 0]: hardware dependent
  10: [ 0]   : control
  33:: timer


 tail -n +1 /proc/asound/card?/pcm*/info


 Attached.

Thanks. It looks like Alsa does see them, and pulseaudio does not pick it up.

Do you have other pulseaudio processes running? Run `ps -fea | grep
pulse` to see if there are other pulseaudio processes. ALso, please
run `sudo lsof /dev/snd/*` to see if some process has opened the
device.



-- 

Saludos,
Felipe Sateler

___
pkg-pulseaudio-devel mailing list
pkg-pulseaudio-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel


Bug#748651: Bug#745550: May be related to systemd

2014-06-05 Thread Felipe Sateler
On Tue, May 27, 2014 at 12:13 PM, Eric Valette eric.vale...@free.fr wrote:
 On 05/27/2014 05:23 PM, Felipe Sateler wrote:

 Hi Eric,

 So, let me summarize what you did:

 1. After some upgrades, pulseaudio didn't see the analog output, just
 the HDMI one.

 I just *first* noticed I had no more sound. As in both case I use analog
 output and not HDMI (because monitors I use have no speakers), the cause was
 probably the same (no more analog audio device) on the two machines although
 after fixing it on one computer I only verified that reinstalling
 sysinit-core on the second and rebooting also fixed the problem on the
 second machine.

 2. Around the same time, pulseaudio started hanging on startup,
 returning EAGAIN from the system dbus socket

 While trying to debug the no sound, I noticed first kde audio/multimedia
 config was hanging on my first machine and later on my other machine at work
 that indeed the pulseaudio was stuck for nearly 2 mins (this probably
 causing the kde multimedia config panel to hang waiting for pulse) and that
 anyway, at the end the analog audio device was not there.

 3. Installing sysvinit-core fixes both issues

 Yes on both machines.

 Is this understanding correct?

 Yes.


 If so, I'm still not sure these are both the same bug: (3) could be a
 race in the boot scripts only exposed by systemd, unrelated to the
 dbus issue.

I'm going to treat them as separate for now. The originally reported
bug does not look like this one.


 I dunno if the bugs are indeed exactly the same or two expressions of a same
 root cause but they are both fixed when going back to sysv init. The race in
 the boot happens on very different type machine (an old core i5 laptop
 single core/hyperthreaded with classical disk 4GB RAM and a high end core I7
 quad core hyperthreaded with SSD and 16 GByte memory).


  Are you willing to try to reproduce the issues again using systemd?
  This can be done by passing init=/bin/systemd in the grub screen (no
  need to reinstall systemd-sysv). Although I fear we will need help
  from the dbus and systemd folks to debug this.

 If you do not manage to reproduce the bug I can spend a limited amount of
 time at it. The fact that the two machines are very different may help
 reproducing it. Maybe you could try to get info from original reporter to
 see if his problem is also fixed by reinstalling  sysvinit-core as an extra
 hint.

Thanks, I indeed cannot reproduce it (and I'm using systemd 208 as well).

Could you please boot with systemd but with full logging? Append to
the boot line:

init=/bin/systemd systemd.log_level=debug

Also please attach a full log of pulseaudio. See
https://wiki.ubuntu.com/PulseAudio/Log for instructions on how to get
one.
And then attach the log produced by `journalctl -b  system.log`
(please get the full log after running pulseaudio).


 NB: both machines were using systemd 208 from experimental. I dunno if
 problem is related to this version of systemd because I'm nearly 100% sure I
 have been using systemd208 with sound for a while before it broke the same
 day after upgrading.

 And to be fair about my setup that is *unusual*:  both machines have a
 distinct / and /usr (I know this i now considered to be bad for systemd but
 the 7.0 installer stills allows that without even emitting a warning...) ,
 do not use initramfs and self tuned recent kernels dedicated to the machines
 with all drivers build-in (except nvidia one ;-)).

This configuration is not really supported, though. Not sure if it is related.

-- 

Saludos,
Felipe Sateler

___
pkg-pulseaudio-devel mailing list
pkg-pulseaudio-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel


Bug#720767:

2014-06-05 Thread Felipe Sateler
Hi Peter,

On Sat, May 10, 2014 at 12:09 AM, Peter Ward peteraw...@gmail.com wrote:

 On 4 May 2014 03:07, Felipe Sateler fsate...@debian.org wrote:

 On Sat, May 3, 2014 at 1:26 AM, Peter Ward peteraw...@gmail.com wrote:
 
  On 29 April 2014 13:26, Felipe Sateler fsate...@debian.org wrote:
 
   When running pulseaudio under my normal user (not in system mode),
   there
   is an initial crackling / white noise which plays until
   module-suspend-on-idle kicks in and suspends the device.
 
  Does this problem happen with pulseaudio 5? If so, I'll need the output
  of
 
  pulseaudio - --log-time
 
 
  Yes, it still happens, and there’s no change in behaviour: by default
  there’s several seconds of crackling, with the timeout=0 workaround,
  there’s
  just a short click.
  I’ve attached pulse.log (which doesn’t have timeout=0) and pulse2.log
  (which
  did).

 Hmm, nothing on the logs!

 
  Also, is the cpu active while the crackling is there? Does the noise
  reappear when the sink is resumed? Does dmesg say anything that might
  be related?
 
 
  Obviously there’s still some startup activity going on, but it’s not
  running
  at 100% cpu or anything like that.
  No, once it’s been suspended, the problem goes away (until next time
  pulseaudio is started).
  And no, I can’t see anything related in dmesg (or
  /var/log/{syslog,kern.log,messages}).

 OK, what happens if you modify default.pa to add tsched=0 to
 module-udev-detect?


 No difference in what I hear, I’ve attached pulse3.log (- --log-time).

I am not seeing any signs of what may happen. I'm going on a limb
here, but you do not have rtkit installed. Does the problem happen if
you install it?


-- 

Saludos,
Felipe Sateler

___
pkg-pulseaudio-devel mailing list
pkg-pulseaudio-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel

Bug#745550: pulseaudio: analog output not appearing in list of devices

2014-06-05 Thread Felipe Sateler
On Thu, Jun 5, 2014 at 1:32 PM, Andrej Herich error...@gmail.com wrote:
 That's almost exactly, what I did in the first place. Nevertheless, here it
 is again. Attached.

Sorry I asked you twice for this. I somehow missed the earlier
attachment when reviewing the log.

Unfortunately, I'm running out of places where to look for a solution.
I've noticed just one thing: the logs say:

(   0.179|   0.000) I: [pulseaudio] alsa-util.c: Successfully attached
to mixer 'hw:0'
(   0.179|   0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out
Front Jack' is now unplugged
(   0.179|   0.000) D: [pulseaudio] device-port.c: Setting port
analog-output-lineout to status no
(   0.179|   0.000) D: [pulseaudio] core-subscribe.c: Dropped
redundant event due to change event.
(   0.179|   0.000) D: [pulseaudio] module-switch-on-port-available.c:
finding port analog-output-lineout
(   0.179|   0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out
CLFE Jack' is now unplugged
(   0.179|   0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Line Out
Surround Jack' is now unplugged
(   0.179|   0.000) D: [pulseaudio] module-alsa-card.c: Jack 'Front
Headphone Jack' is now plugged in
(   0.179|   0.000) D: [pulseaudio] device-port.c: Setting port
analog-output-headphones to status yes

Do you actually have a something plugged into the back analog output?

-- 

Saludos,
Felipe Sateler

___
pkg-pulseaudio-devel mailing list
pkg-pulseaudio-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel