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

Bug#542116: linux-image-2.6.30-1-amd64: media players sometimes fail to open audio device



2009/9/8 Ben Hutchings <ben@decadent.org.uk>:
> Please cc 542116@bugs.debian.org on all mail concerning this bug report.
>
> On Mon, 2009-08-24 at 10:23 +0200, Michal Suchanek wrote:
>> 2009/8/23 Ben Hutchings <ben@decadent.org.uk>:
>> > On Tue, 2009-08-18 at 08:33 +0200, Michal Suchanek wrote:
>> >> 2009/8/18 Ben Hutchings <ben@decadent.org.uk>:
>> >> > On Mon, 2009-08-17 at 23:46 +0200, Michal Suchanek wrote:
>> >> >> Package: linux-image-2.6.30-1-amd64
>> >> >> Version: 2.6.30-3.local
>> >> >> Severity: normal
>> >> >>
>> >> >>
>> >> >> Media players sometimes fail to open the audio device saying that the
>> >> >> device is busy.
>
> Which specific media players are you using?

mplayer and vlc

>
>> >> >> Since re-running the player (or skipping to the next item in playlist)
>> >> >> resolves the problem I don't think this is really the case.
>> >> >>
>> >> >> I am running a rebuild of 2.6.30-3 because I needed the vmlinux image.
>> >> >
>> >> > Are you running esd or any other software mixer?
>> >> >
>> >> No. Next to nothing works with these.
>> >
>> > Which sound driver were you using, or which sound chip do you have?
>> >
>>
>> I guess it's snd-hda-intel - here is it's message when it loads:
>>
>> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
>>
>> This is what oss says about the chip:
>>
>>  1: oss_hdaudio0 Intel HD Audio interrupts=55013 (55013)
>>     HD Audio controller Intel HD Audio
>>     Vendor ID    0x808627d8
>>     Subvendor ID 0x10438249
>>      Codec  0: ALC883 (0x10ec0883/0x1043c603)
>
> Please try snd-hda-intel again, and send a copy of the kernel log from
> after you see the 'device is busy' error.
>

I don't think there's any message. It does not happen always, only
once in ~10 attempts to reopen the device
I will try to reproduce this and see if there is anything in the recent log.

Thanks

Michal



Reply to: