Bug#815787: May be a kernel problem not a pulseaudio one?

[Felipe Sateler]

Control: reassign -1 linux-image-4.4.0-1-amd64



On 25 February 2016 at 14:20, Russel Winder <russel at winder.org.uk> wrote:
> Hi,
>
>>
>> Thanks, that is useful.
>
> Splendid. I appreciate it can be a pain having to ask for data, but it
> is much easier to send it what is asked for and will be useful than to
> try and guess ahead of time and inundate with useless stuff.

Yes, moreover, the level of output from pulseaudio verbose mode is too
much for normal usage so it cannot be automatically included.

>
>> The log contains:
>>
>> module-udev-detect.c: Found 1 cards.
>>
>> And no trace of the sound blaster. The code suggests that this is
>> either because it is no longer in the sound subsystem, or that the
>> path does not have an id[1].
>
> Sound blaster is definitely still there, witness that it is in the
> lspci listing and it works fine in earlier kernels.
>
> 09:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1
> (rev 05)
> 09:02.1 Input device controller: Creative Labs SB Live! Game Port (rev
> 05)
>
>> What is the output of:
>>
>> ls -d /sys/devices/*/*/sound/*
>
> |> ls -d /sys/devices/*/*/sound/*
> ls: cannot access '/sys/devices/*/*/sound/*': No such file or directory
>
> Which seems a bit terminal. Shall I reboot to 4.3.0 and do the same for
> comparison?

Second attempt is to do `ls /dev/snd/control*` , and run `udevadm info
$controlfile` for each result.

But, I somehow missed over the fact that in the initial bug report,
one of the attachments shows alsa knows nothing of the sound blaster.
If alsa does not know about it, then neither will pulseaudio. This
most likely is a problem in the kernel, so I am reassigning there and
CCing the kernel list.

>
>> And for each of those paths, what is the output of:
>>
>> udevadm info -p $path
>>
>> ?
>>
>> Also please attach the output of `lsmod | grep snd`
>
> |> lsmod | grep snd
> snd_hda_codec_hdmi     53248  1
> snd_hda_intel          36864  0
> snd_hda_codec         131072  2 snd_hda_codec_hdmi,snd_hda_intel
> snd_hda_core           65536  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
> snd_hwdep              16384  1 snd_hda_codec
> snd_pcm               102400  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
> snd_timer              32768  1 snd_pcm
> snd                    81920  6 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
> soundcore              16384  1 snd

The emu10k1 (or emu10k1x) driver (for the sound blaster) is not
loaded, so this is almost certainly a kernel problem.


-- 

Saludos,
Felipe Sateler