Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jordi Mallach <jordi@debian.org>
Cc: alsa-devel@lists.sourceforge.net, debian-alsa@lists.wedontsleep.org
Subject: Re: unresolved bugs in the Debian BTS
Date: Mon, 10 Mar 2003 12:05:51 +0100	[thread overview]
Message-ID: <s5hk7f75vn4.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030306181713.GA15224@nubol.int.oskuro.net>

Hi Jordi,

thanks for the summary.


At Thu, 6 Mar 2003 19:17:13 +0100,
Jordi Mallach wrote:
> 
> ########################
> Bug 183315: Sequencer device opening fails with ENOMEM
> 
> After some time (several open/close cycles of /dev/sequencer?), the next
> attempt to use the device will cause any open attempt to return ENOMEM. The
> usage counts of snd-emu10k1-synth, snd-emux-synth and snd-emu10k1 become
> non-zero and are incremented for each open failure, rendering them (AFAIK)
> unremovable without a reboot.
> 
> To trigger this, I've found it sufficient to run some lxmusserv-using Doom
> port several times [1]; though I don't think that it matters which program is
> used, I don't currently know whether it matters if AWE emulation/support is
> used.
> 
> The problem appears to only affect OSS sequencer usage; pmidi and programs
> which use other OSS devices still work.
 
fixed on the latest rc.


> ########################
> Bug 182840: hw_pointer warning with 845PE chipset
> 
> this system has an Asustek P4PE motherbooard with an Intel 845PE
> chipset.  Here is the lspci output for the integrated audio
> controller:
> 
> 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio (rev 02)
> 
> I finally managed to get sound out of this motherboard with alsaplayer
> (not with the ALSA xmms output plugin yet).
> 
> So all is well, except that I saw this warning message in the dmesg
> output:
> 
> ALSA ../alsa-kernel/core/pcm_lib.c:187: Unexpected hw_pointer value (stream = 0, delta: -1168, max jitter = 8192): wrong interrupt acknowledge?
> 
> PS: the other soundcard (ens1371) is managed by OSS/Free.

likely a hardware problem.  not a fatal bug.
the above appears only when the driver is compiled with the debug option.


> #########################
> Bug 180653: Bad audio quality on VT8233 with rc7
> 
> Quoting:
> -----------------
> The quality of the audio output has decreased very strongly from rc6
> to rc7.  With rc6, everything was working fine, but with rc7 there is
> always a bit of noise when sound is played (I had the same problem
> with older versions of alsa, but rc6 was working fine).
> 
> My sound card is an on-board VT8233 chip, and I'm running kernel
> 2.4.20.  I didn't try rc7-1.
> ------------------
> 
> Could this be related to the bad detection code in rc7 for VIA8233?
 
rc7 had a bug on VIA8233A.  fixed on the later versions.


> #########################
> 
> Bug 177522: aplay segfaults on multiple files
> 
> Submitted against RC3, but I think it's still there:
> 
> -----------------
> sorry fellas, when one mixes .au and .wav, or does more than one of the same
> file, e.g.
> $ y=/usr/share/emacs/site-lisp/emacspeak/sounds/default-8k/yank-object.au
> $ aplay $y $y $y $y
> one wont hear all what is requested, and will even seg fault!
> 
> 
> aplay: pcm.c:5692: snd_pcm_unlink_ptr: Assertion `0' failed.

this happend only on a certain chip.
should have been fixed already on rc7.


> ########################
> Bug 174690: alsamixer silently fails with ALI5451 South Bridge card
> 
> (against beta12)
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=174690
 
already fixed on rc6 or rc7.


> ########################
> Bug 172967: "AC'97 0:0 does not respond"
> 
> (against rc6)
> 
> He said:
> When attempting to load the es1968 driver, built against kernel 2.4.18,
> 2.4.19 or 2.4.20, I get the following message from the ALSA code:
> 
>     kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1529: AC'97 0:0 does not respond - RESET [REC_GAIN = 0x0]
> 
> The driver fails to load.
> 
> Same for rc5, works with beta12.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172967
 
this might be due to the detection of modem codec.
fixed on the recent version (hopefully).


> #######################
> Bug 126797: Rear channels no longer work on SB Live ! 512
> 
> (against beta10)
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126797
> 
> Probably fixed?
 
should work - needs another tests with the latest version.


> #######################
> Bug 123800: maestro3 breaks irda
> 
> ancient bug, submitter doesn't have the hardware anymore. The bug has a pointer to a patch, but it's a 404 now, so I couldn't check.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=123800
 
already fixed for Dell Inspiron 4000 and 8000.
for other notebooks, we need the PCI subsystem vendor and device id
numbers to add the quirks in the driver code.


> ########################
> Bug 108572: PCI IRQ sharing with USB will crash ALSA
> (against beta 4)
> 
> Null pointer dereference when loading the cs45xx module.
> Another user confirmed this for rc6, but now with kernel panic.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108572
> 
> Would be nice to have a look at this one.
 
hmm, it's difficult to guess.
we need a trace from kernel oops.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-03-10 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 18:17 unresolved bugs in the Debian BTS Jordi Mallach
2003-03-06 18:23 ` Jordi Mallach
2003-03-10 11:05 ` Takashi Iwai [this message]
2003-03-10 16:48   ` Jordi Mallach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hk7f75vn4.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=debian-alsa@lists.wedontsleep.org \
    --cc=jordi@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox