All of lore.kernel.org
 help / color / mirror / Atom feed
* [ALSA - firmware 0000209]: Sometimes XMMS stop playing songs (dmix used)
From: bugtrack @ 2006-03-22  2:06 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=209> 
======================================================================
Reported By:                srr
Assigned To:                
======================================================================
Project:                    ALSA - firmware
Issue ID:                   209
Category:                   
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             04-14-2004 11:41 CEST
Last Modified:              03-22-2006 03:06 CET
======================================================================
Summary:                    Sometimes XMMS stop playing songs (dmix used)
Description: 
Sometimes XMMS stop playing songs and show message that says "Audio device
not
properly configured or busy". It happends when new song just start
playing. If I click on Play button, songs continued playing. 

I can't repeat this bug, it happends 3-5 times in day.

If i start mpg123 and xmms they are play simultaniously (even if i start
10
copies of mpg123)

This is output from xmms:

ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
Device
or resource busy
ALSA lib pcm_dmix.c:868:(snd_pcm_dmix_open) unable to open slave
 
** WARNING **: alsa_setup(): Failed to open pcm device (default): Device
or
resource busy


======================================================================

----------------------------------------------------------------------
 Steve Fink - 07-21-05 08:21 
----------------------------------------------------------------------
I have a very similar problem with mplayer (mplayer-1.0pre3try2). I set the
default device to go through dmix. After some combination of starting and
stopping mplayers (some of them overlap in time), I will end up with an
mplayer that sits and sleeps for half a second, over and over again.

That kind of sucks, but it's an mplayer problem. My real problem is that
then when I start up the next program that uses ALSA (another mplayer, my
application, aplay, or whatever), it gets the "open /dev/snd/pcmC0D0p
failed: Device or resource busy" error.

If I kill the offending mplayer process, it fixes it.

I am using alsa-driver 1.0.8 and alsa-lib 1.0.8 with the snd-intel8x0
driver. I tried compiling a 1.0.9 (or something calling itself that) and
using it, but I still had the same problem.

Could anyone tell me what sort of thing is happening? I thought that if
everything went through dmix, you should never be able to get into an
EBUSY state. But it seems that the kernel driver is doing something behind
the pcmC?D?p device that can get into this state? (I see similar output
when I have a user play an ALSA sound app, and then try to play something
from the root account. So it does seem like some state is sticking to the
device somehow.) Is there anything that will dump out the state of a
device? Where can I read more about how this all works?

I don't have a simple test script that shows the problem yet. How I
actually see it is that I start up my application (which itself opens up
the pcm device, via SDL with SDL_AUDIODRIVER=alsa), and it forks off an
mplayer (with -ao sdl:alsa). Then I flip rapidly between two different
movies, where each flip kill -TERM's the old mplayer and starts up a new
one. Oddly, every one of these mplayers is able to play sound. Then I shut
down my app, and wait for the mplayers to stop. If I get the bug, which I
do 80% of the time, then one of them will never stop, and when I try to
restart my app (or aplay, or mplayer), it gives me the error message and
fails to play sound.

fuser /dev/snd/pcmC0D0p shows only the mplayer processes (when my app has
exited and there is an mplayer lurking around.)



----------------------------------------------------------------------
 rlrevell - 03-22-06 03:06 
----------------------------------------------------------------------
This should be fixed in CVS, can you please test?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
04-14-04 11:41 srr            New Issue                                    
04-16-04 11:54 tiwai          Note Added: 0000832                          
04-20-04 07:39 srr            Note Added: 0000869                          
04-20-04 07:41 srr            Issue Monitored: srr                         
10-14-04 22:40 chtephan       Note Added: 0002160                          
10-20-04 20:42 martin         Note Added: 0002218                          
11-28-04 18:33 martin         Note Added: 0002626                          
01-12-05 10:41 leahcim        Note Added: 0003161                          
01-12-05 10:41 leahcim        Issue Monitored: leahcim                     
01-12-05 20:26 Dawid Gajownik Issue Monitored: Dawid Gajownik                   

01-19-05 16:54 tiwai          Note Added: 0003296                          
01-19-05 16:54 tiwai          File Added: xmms-1.2.10-alsa-multithread.diff     
              
07-20-05 17:34 Steve Fink     Issue Monitored: Steve Fink                    
07-21-05 01:03 Steve Fink     Note Added: 0005536                          
07-21-05 08:21 Steve Fink     Note Edited: 0005536                         
03-22-06 03:06 rlrevell       Note Added: 0008796                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* [ALSA - lib 0001277]: Choosing of default playback device on the fly
From: bugtrack @ 2006-03-22  2:06 UTC (permalink / raw)
  To: alsa-devel


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1277> 
======================================================================
Reported By:                oldium
Assigned To:                
======================================================================
Project:                    ALSA - lib
Issue ID:                   1277
Category:                   0_general
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
======================================================================
Date Submitted:             07-23-2005 10:42 CEST
Last Modified:              03-22-2006 03:06 CET
======================================================================
Summary:                    Choosing of default playback device on the fly
Description: 
Situation: There is on-board sound card and one pluggable (USB/PCMCIA)
sound card which is preferred to play the sound.

Problem: If the preferred sound card is plugged-in before the boot time,
it is taken as the default output card (as of snd-card-0 settings and
driver is loaded first), but when the sound card is plugged after the
boot, it gets index 1 and is not the default.

Suggestion: Please consider creating plugin to use preferred sound card as
default output whenever it is plugged in and use fallback card whenever it
is not available, or let the user space program (shell script) decide
which card is default.

Usage: This is good for laptops using external sound card at home and
built-in on the way.
======================================================================

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:06 
----------------------------------------------------------------------
Not a bug (feature requests should be discussed on alsa-devel ML)

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-23-05 10:42 oldium         New Issue                                    
03-22-06 03:06 rlrevell       Status                   new => closed       
03-22-06 03:06 rlrevell       Note Added: 0008795                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* [ALSA - driver 0001283]: Allegro-1 does not generate interrupts - but does on linux 2.4.27
From: bugtrack @ 2006-03-22  2:05 UTC (permalink / raw)
  To: alsa-devel


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1283> 
======================================================================
Reported By:                sclark46
Assigned To:                tiwai
======================================================================
Project:                    ALSA - driver
Issue ID:                   1283
Category:                   PCI - maestro3
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Distribution:               Fedora Core 4
Kernel Version:             2.6.12-1.1398_FC4
Resolution:                 open
Fixed in Version:           
======================================================================
Date Submitted:             07-27-2005 03:51 CEST
Last Modified:              03-22-2006 03:05 CET
======================================================================
Summary:                    Allegro-1 does not generate interrupts - but does on
linux 2.4.27
Description: 
Aplay fails with a write error and the following error message:
Jul 26 21:06:14 joker4 kernel: ALSA
/home/sclark/alsa-driver-1.0.9rc4a/acore/pcm_native.c:1442: playback drain
error (DMA or IRQ trouble?)

The sound clip plays repeatedly until that error pops up.

I booted a Knoppix CD to verify the HW worked and sound played correctly.
The Knoppix kernel was 2.4.27


======================================================================

----------------------------------------------------------------------
 rlrevell - 07-30-05 09:11 
----------------------------------------------------------------------
This should be reported to the kernel bugzilla.

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:05 
----------------------------------------------------------------------
Not an ALSA bug

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-27-05 03:51 sclark46       New Issue                                    
07-27-05 03:51 sclark46       Distribution              => Fedora Core 4   
07-27-05 03:51 sclark46       Kernel Version            => 2.6.12-1.1398_FC4
07-27-05 03:52 sclark46       Issue Monitored: sclark46                    
07-27-05 03:52 sclark46       Issue End Monitor: sclark46                    
07-30-05 05:21 sclark46       Note Added: 0005588                          
07-30-05 09:11 rlrevell       Note Added: 0005590                          
03-22-06 03:05 rlrevell       Status                   assigned => closed  
03-22-06 03:05 rlrevell       Note Added: 0008794                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: [PATCH 07/15] libata: Remove dependence on host_set->dev for SAS
From: Jeff Garzik @ 2006-03-22  2:05 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172304.k2HN4gNg015028@d03av03.boulder.ibm.com>

Brian King wrote:
> Remove some of the dependence on the host_set struct
> in preparation for supporting SAS HBAs. Adds a struct device
> pointer to the ata_port struct.
> 
> Signed-off-by: Brian King <brking@us.ibm.com>

Given previous discussion, ACK.



^ permalink raw reply

* [ALSA - driver 0000833]: [snd_via82xx] setting ac97_clock greater than 48000 should be ?ignored? but breaks sound output for kernels >= linux-2.6.9
From: bugtrack @ 2006-03-22  2:04 UTC (permalink / raw)
  To: alsa-devel


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=833> 
======================================================================
Reported By:                t35t0r
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   833
Category:                   PCI - via82xx
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Distribution:               gentoo
Kernel Version:             2.6.10-gentoo-r5 (but error is reproducible in stock
kernels also)
Resolution:                 open
Fixed in Version:           
======================================================================
Date Submitted:             01-18-2005 17:35 CET
Last Modified:              03-22-2006 03:04 CET
======================================================================
Summary:                    [snd_via82xx] setting ac97_clock greater than 48000
should be ?ignored? but breaks sound output for kernels >= linux-2.6.9
Description: 
Please read: http://bugs.gentoo.org/show_bug.cgi?id=78327

Forwarded email below

From: Jaroslav Kysela <perex@suse.cz>
To: t35t0r@gmail.com
Cc: Takashi Iwai <tiwai@suse.de>
Date: Tue, 18 Jan 2005 10:40:56 +0100 (CET)
Subject: Re: snd_via82xx ac97_clock=96000 parameter doesn't work for
kernels >= linux-2.6.9 (fwd)

> > Dear sir:
> >
> > If you get a chance can you look at
> > http://bugs.gentoo.org/show_bug.cgi?id=78327 . It seems that setting
> > ac97_clock=96000 no longer works for kernels >= linux-2.6.9. I didn't
> > try any other ac97_clock settings since the 96000 setting was working
> > for a 2.6.7 and 2.6.8.1 kernel. The url has some of my hardware
> > specifications.

It seems that the no-sound bug is caused with the AC'97 codec
initialization. Specifying 96000 as ac97_clock parameter won't help,
because this value must be from 8000 to 48000 otherwise it is ignored.
Please, fill a bug to our bugtrack system.

                                               Jaroslav
======================================================================

----------------------------------------------------------------------
 perex - 08-04-05 09:15 
----------------------------------------------------------------------
To confirm: Does the driver work without using ac97_clock parameter?

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:04 
----------------------------------------------------------------------
No response

Issue History
Date Modified  Username       Field                    Change              
======================================================================
01-18-05 17:35 t35t0r         New Issue                                    
01-18-05 17:35 t35t0r         Distribution              => gentoo          
01-18-05 17:35 t35t0r         Kernel Version            => 2.6.10-gentoo-r5 (but
error is reproducible in stock kernels also)
01-18-05 17:44 tiwai          Note Added: 0003252                          
07-22-05 02:46 connolly       Note Added: 0005544                          
08-04-05 09:15 perex          Note Added: 0005642                          
03-22-06 03:04 rlrevell       Status                   new => closed       
03-22-06 03:04 rlrevell       Note Added: 0008793                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: [PATCH 02/15] libata: Add some dummy noop functions
From: Jeff Garzik @ 2006-03-22  2:03 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172304.k2HN49hr018969@d03av01.boulder.ibm.com>

Brian King wrote:
> Add some dummy noop functions for use by libata clients
> that do not need to do anything. Future SAS patches will
> utilize these functions.
> 
> Signed-off-by: Brian King <brking@us.ibm.com>

applied 2-3



^ permalink raw reply

* [ALSA - driver 0001342]: SOund is not working
From: bugtrack @ 2006-03-22  2:03 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1342> 
======================================================================
Reported By:                taya
Assigned To:                tiwai
======================================================================
Project:                    ALSA - driver
Issue ID:                   1342
Category:                   PCI - hda-intel
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Distribution:               
Kernel Version:             2.6.10-5-386
======================================================================
Date Submitted:             08-16-2005 20:11 CEST
Last Modified:              03-22-2006 03:03 CET
======================================================================
Summary:                    SOund is not working
Description: 
Hi, I have laptop: Asus w500
It has integrated sound card: Intel high definition audio.
It seems that alsa driver is working, but it does not.
Please correct this.
Thanks
======================================================================

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:03 
----------------------------------------------------------------------
Was this resolved in later ALSA releases?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-16-05 20:11 taya           New Issue                                    
08-16-05 20:11 taya           Kernel Version            => 2.6.10-5-386    
03-22-06 03:03 rlrevell       Note Added: 0008792                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: Running Linux 2.6.16 and Xorg 7.0 on iMac G5 rev C (iSight)
From: Benjamin Herrenschmidt @ 2006-03-22  2:03 UTC (permalink / raw)
  To: Étienne Bersac; +Cc: Linuxppc-dev, debian-powerpc, ubuntu-devel
In-Reply-To: <82FEFC77-5EDB-4349-B935-AD422913F3F7@laposte.net>


>   - Get Ben's kernel at http://bersace03.free.fr/pub/iMac%20G5/ 
> vmlinux.bz2 (mirror of http://gate.crashing.org/~benh/vmlinux.bz2).  
> bunzip2 it at /.

Don't do that ! :)

There is no such thing as benh's kernels :) that's long gone. In fact, I
just removed the above one from the site... it was just a build to help
you. 2.6.16 should work on this machine, if you need a pre-build version
of it, try to get somebody on this list or post yourself one somewhere
but don't spread the idea that there is still such a thing as "benh's
kernel" :)

Ben.

^ permalink raw reply

* Re: [PATCH 06/15] libata: Stop using host->max_cmd_len
From: Jeff Garzik @ 2006-03-22  2:03 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172304.k2HN4YEF019986@d03av01.boulder.ibm.com>

Brian King wrote:
> In preparation for SAS attached SATA devices, quit using
> the max_cmd_len in the scsi_host struct.
> 
> Signed-off-by: Brian King <brking@us.ibm.com>

I see this as a bit of a hack.  In general, its best to inform upper 
layers of known limits as soon as possible.  For the non-SAS case, for 
that point of view, this patch is a regression.

	Jeff



^ permalink raw reply

* [ALSA - utils 0000577]: Please make it possible for two (or more) mixer sliders to be locked together
From: bugtrack @ 2006-03-22  2:03 UTC (permalink / raw)
  To: alsa-devel


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=577> 
======================================================================
Reported By:                ldarby
Assigned To:                
======================================================================
Project:                    ALSA - utils
Issue ID:                   577
Category:                   alsamixer
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
======================================================================
Date Submitted:             10-10-2004 17:35 CEST
Last Modified:              03-22-2006 03:03 CET
======================================================================
Summary:                    Please make it possible for two (or more) mixer
sliders to be locked together
Description: 
I noticed that the only way to reduce the volume to the lowest (not muting
it tho) is reducing both Master and PCM sliders, and to get the loudest
non-distorted volume, both need to increased to almost max.  I think I
remember a mixer for a windows driver that could lock two mixer sliders
together to do this, and I've done this myself from within XMMS, but it
relies on Master and PCM elems being in a certain position (probably sound
card dependent).  Would it be a good idea to implement this in a general
way in alsamixer, or has this already been done in another mixer?
(googling for linux mixers reveals far too many to check through...)

Thanks,
Laurence
======================================================================

----------------------------------------------------------------------
 tiwai - 10-14-04 14:58 
----------------------------------------------------------------------
Sending bugs to alsa-devel is fine, IMO, since alsa-devel is the
place where every development process should be centralized.
(Though, the message should be shorten, containing only diffs.)

Again, BTS is not the place for DISCUSSION.  It's the place for
REPORTING.
If you ask something, or want to hear something from other people
(like this case), then alsa-devel is the appropriate place.
That's my point.

The feature request itself is fine (although it will be likely in
the low priority).

BTW, any patches are very appreciated, of course :) !!

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:03 
----------------------------------------------------------------------
Not a bug

Issue History
Date Modified  Username       Field                    Change              
======================================================================
10-10-04 17:35 ldarby         New Issue                                    
10-11-04 16:15 tiwai          Note Added: 0002082                          
10-11-04 20:26 ldarby         Note Added: 0002084                          
10-12-04 11:49 tiwai          Note Added: 0002088                          
10-14-04 14:45 ldarby         Note Added: 0002147                          
10-14-04 14:58 tiwai          Note Added: 0002148                          
08-20-05 15:57 jdthood        Summary                  locking two (or more)
mixer sliders together to get full volume range => Please make it possible for
two (or more) mixer sliders to be locked together
03-22-06 03:03 rlrevell       Status                   new => closed       
03-22-06 03:03 rlrevell       Note Added: 0008791                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: [RFC] [PATCH 1/7] Add process virtualisation umbrella structure (vx_info)
From: Herbert Poetzl @ 2006-03-22  2:02 UTC (permalink / raw)
  To: Dave Hansen
  Cc: Sam Vilain, linux-kernel, Eric W.Biederman,
	OpenVZ developers list, Serge E.Hallyn, Andrew Morton
In-Reply-To: <1142967185.10906.188.camel@localhost.localdomain>

On Tue, Mar 21, 2006 at 10:53:05AM -0800, Dave Hansen wrote:
> On Tue, 2006-03-21 at 18:13 +1200, Sam Vilain wrote:
> > +static inline void release_vx_info(struct vx_info *vxi,
> > +       struct task_struct *task)
> > +{
> > +       might_sleep();
> > +
> > +       if (atomic_dec_and_test(&vxi->vx_tasks))
> > +               unhash_vx_info(vxi);
> > +} 
> 
> Are these better handled by krefs and their destructors?

well, those were there long before krefs got
into the kernel, IIRC :)

best,
Herbert

> -- Dave

^ permalink raw reply

* Re: [PATCH] Add SA_PERCPU_IRQ flag support
From: Benjamin Herrenschmidt @ 2006-03-22  2:00 UTC (permalink / raw)
  To: Christoph Lameter; +Cc: Andrew Morton, Dimitri Sivanich, linux-kernel, hch, jes
In-Reply-To: <Pine.LNX.4.64.0603211543430.14462@schroedinger.engr.sgi.com>


> +	else
> +		BUG_ON(desc->status & IRQ_PER_CPU);

I see that you are a member of the school of brutalism ! :)

Ben.



^ permalink raw reply

* [ALSA - driver 0000299]: No audio after recommended patch (see 0000216)
From: bugtrack @ 2006-03-22  2:02 UTC (permalink / raw)
  To: alsa-devel


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=299> 
======================================================================
Reported By:                salmo
Assigned To:                mjander
======================================================================
Project:                    ALSA - driver
Issue ID:                   299
Category:                   PCI - au88x0
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Distribution:               Gentoo Linux
Kernel Version:             2.6.6
Resolution:                 open
Fixed in Version:           
======================================================================
Date Submitted:             05-22-2004 22:25 CEST
Last Modified:              03-22-2006 03:02 CET
======================================================================
Summary:                    No audio after recommended patch (see 0000216)
Description: 
This is a continuation of bug 0000216.  Would have added this comment there
but bug was closed.

Applied the patch
(http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/aureal-2.6.5.diff.gz)
cleanly, recompiled, rebooted twice.  Now I get no sound output at all. 
Checked with headphones, checked mixer levels.  

The modules (snd_au8830, snd_ac97_codec, snd_mpu401_uart, snd_rawmidi,
snd_seq_oss, snd_seq_midi_event, snd_seq, snd_seq_device, snd_pcm_oss,
snd_pcm, snd_page_alloc, snd_timer, snd_mixer_oss, snd) are loaded,
everything seems fine.  XMMS, Rhythmbox, etc. will "play" the files at a
normal rate using both ALSA and OSS outputs, but nothing comes out of the
card.

Let me know if there is any information that I can give you that will
help.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0000216 Speed/pitch issues when playing multipl...
======================================================================

----------------------------------------------------------------------
 perex - 08-09-05 13:14 
----------------------------------------------------------------------
reporter: Does this problem exists at the time?

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:02 
----------------------------------------------------------------------
No response

Issue History
Date Modified  Username       Field                    Change              
======================================================================
05-22-04 22:25 salmo          New Issue                                    
05-22-04 22:25 salmo          Distribution              => Gentoo Linux    
05-22-04 22:25 salmo          Kernel Version            => 2.6.6           
05-22-04 23:42 mjander        Note Added: 0001176                          
08-09-05 13:13 perex          Relationship added       related to 0000216  
08-09-05 13:14 perex          Note Added: 0005729                          
08-26-05 15:05 Raymond        Note Added: 0005954                          
02-06-06 04:14 Raymond        Note Deleted: 0005954                        
03-22-06 03:02 rlrevell       Status                   assigned => closed  
03-22-06 03:02 rlrevell       Note Added: 0008790                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* [ALSA - driver 0000343]: au8820 hangs the system at some occasions
From: bugtrack @ 2006-03-22  2:01 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=343> 
======================================================================
Reported By:                sandman
Assigned To:                mjander
======================================================================
Project:                    ALSA - driver
Issue ID:                   343
Category:                   PCI - au88x0
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Distribution:               RedHat 9
Kernel Version:             2.6.7
======================================================================
Date Submitted:             06-23-2004 07:20 CEST
Last Modified:              03-22-2006 03:01 CET
======================================================================
Summary:                    au8820 hangs the system at some occasions
Description: 
At some occasions the system hangs without any means
to recover other than reset button. No mouse, no pings and
even the alt-SysRq feature doesn't help.
As a result I reboot the system a few times a day (sometimes).
The problem is present in 2.6.5, 2.6.6 and 2.6.7 kernels at
least. 
======================================================================

----------------------------------------------------------------------
 Raymond - 08-25-05 18:51 
----------------------------------------------------------------------
Do ALSA support dual Opteron (Dual CPU) ?

The CVS version include the patch "Fixed missing spin_unlock" which may
fix your problem.

----------------------------------------------------------------------
 rlrevell - 03-22-06 03:01 
----------------------------------------------------------------------
Was this problem solved in later ALSA releases?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-23-04 07:20 sandman        New Issue                                    
06-23-04 07:20 sandman        Distribution              => RedHat 9        
06-23-04 07:20 sandman        Kernel Version            => 2.6.7           
04-07-05 21:04 jdthood        Note Added: 0004370                          
04-12-05 20:26 alien999999999 Issue Monitored: alien999999999                   

04-19-05 09:47 sandman        Note Added: 0004519                          
04-19-05 10:03 jdthood        Status                   assigned => acknowledged
08-25-05 18:51 Raymond        Note Added: 0005942                          
03-22-06 03:01 rlrevell       Note Added: 0008789                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* What's in git.git
From: Junio C Hamano @ 2006-03-22  1:58 UTC (permalink / raw)
  To: git

* The 'master' branch has these since the last announcement.

 - git.el updates (Alexandre Julliard)
 - git-svn updates (Eric Wong)
 - git-blame updates (Fredrik Kuivinen)
 - documentation updates (Francis Daly, Jon Loeliger)
 - Makefile: Add TAGS and tags targets (Fredrik Kuivinen)
 - http-push support for deleting remote branches (Nick Hengeveld)

 - assorted minor fixes and tweaks (Alexandre Julliard, Mark
   Hollomon, Shawn Pearce, Yasushi SHOJI, Nicolas Pitre, Randal
   L. Schwartz and me)

* The 'next' branch, in addition, has two important fixes and
  enhancements, and it probably is a good time to do a 1.3
  release when they graduate to "master" and prove stable.

 - quicker and dirtier rename detection by Linus and me.

   I've been using this myself and haven't seen major
   misdetection so far, but I do not use much renames.  Maybe
   it's time to push this out and see what happens.  This is
   _not_ the "important" part.

 - cvsimport post-import checkout fix.

   Earlier we had a workaround to deal with people who import
   into the current branch by not checking out.  After
   incrementally importing from the same CVS repository again,
   however, the code did update the branch head.  This made the
   working tree and the index stale and was causing more
   confusion than it avoided.

   This fix is to make re-importing act more like git-pull, not
   git-fetch.  So if you run an incremental import into the
   current branch, it tries to fast-forward the working tree and
   index (your current branch head, index and working tree had
   better be pristine with respect to the CVS repository for
   this, but that is already an requirement for a tracking
   branch anyway) when your current branch is the tracking
   branch, or merge the imported result into your current branch
   if you are using a separate tracking branch.

   I've done some testing on this myself, but am waiting for
   independent confirmations from cvsimport users.  Merlyn?

 - refs/remotes support.

   This has been the recent hot topic, on git-clone.

   First, not so controversial one.  A new option --reference
   can be used to help cloning a project similar to what you
   already have over thin wire:

	$ git clone --reference /git/linux-2.6.git \
          git://git.kernel.org/pub/.../jgarzik/libata-dev.git/ \
          libata-dev

   What happens here is that the new repository (libata-dev you
   are creating by cloning from Jeff) is set up to borrow from
   vanilla Linus repository you already keep track of, and the
   initial clone downloads and expands objects that are only
   present in Jeff's tree.

   Another new option, --use-separate-remote, changes the way
   $GIT_DIR/remotes/origin file and your tracking branches are
   set up after the initial cloning.  Without it, all the remote
   heads are copied to your $GIT_DIR/refs/heads/ and a copy of
   the remote HEAD is made as $GIT_DIR/refs/heads/origin, and
   remotes/origin file is set up to keep this structure up to
   date.  This is the traditional behaviour.

   When --use-separate-remote is in effect, the tracking
   branches are created in $GIT_DIR/refs/remotes/origin/ and you
   will not get the extra "origin" head.  Your local branch
   namespace under $GIT_DIR/refs/heads/ will only have "master".
   In addition, a symref $GIT_DIR/refs/remotes/origin/HEAD
   points at the primary branch of the remote repository.
   Similar to a filename in $GIT_DIR/refs/{heads,tags} that can
   be used to name a ref (e.g. when you say "git diff frotz",
   you are telling git to read from $GIT_DIR/refs/heads/frotz
   and use that commit ID to diff your working tree against), a
   directory that has such a symref under $GIT_DIR/refs/remotes
   can be used to name the ref.  IOW, "git diff origin" in a
   repository a cloned this way means you want a diff against
   $GIT_DIR/refs/remotes/origin/HEAD.

   I've done reasonable amount of testing over git:// transport,
   and some with http:// as well, but I do not know if rsync://
   works at all (I never use rsync:// transport myself).  If
   anybody cares about rsync:// transport, please test it while
   it still is in "next" to keep things working for you.

   A new configuration option, 'core.warnambiguousrefs', can be
   set to warn you if you use "frotz" to name a ref when you
   have more than one "frotz" under $GIT_DIR/refs (e.g. you have
   both branch "frotz" and tag "frotz", and/or you have
   refs/remotes/frotz/HEAD).

   It also has changes by Eric Wong to teach git-fetch about
   $GIT_DIR/refs/remotes hierarchy.

^ permalink raw reply

* Re: [PATCH 05/15] libata: Add __ata_scsi_ioctl
From: Jeff Garzik @ 2006-03-22  1:54 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172304.k2HN4Stx030065@d01av02.pok.ibm.com>

Brian King wrote:
>  
> -int ata_scsi_ioctl(struct scsi_device *scsidev, int cmd, void __user *arg)
> +int __ata_scsi_ioctl(struct scsi_device *scsidev, int cmd, void __user *arg)
>  {
> -	struct ata_port *ap;
> -	struct ata_device *dev;
>  	int val = -EINVAL, rc = -EINVAL;
>  
> -	ap = (struct ata_port *) &scsidev->host->hostdata[0];
> -	if (!ap)
> -		goto out;
> -
> -	dev = ata_scsi_find_dev(ap, scsidev);
> -	if (!dev) {
> -		rc = -ENODEV;
> -		goto out;
> -	}
> -
>  	switch (cmd) {


Rather than create a new function, it looks like the above code can 
simply be removed.  I don't see anything that uses 'ap' or 'dev'.

	Jeff



^ permalink raw reply

* Re: [PATCH] fix memory leak in mm/slab.c::alloc_kmemlist()  (try #3)
From: Christoph Lameter @ 2006-03-22  1:52 UTC (permalink / raw)
  To: Andrew Morton; +Cc: jesper.juhl, penberg, linux-kernel
In-Reply-To: <20060321174623.2f92331b.akpm@osdl.org>

On Tue, 21 Mar 2006, Andrew Morton wrote:

> Well that's a big pickle.  How about allocating everything first, saving it
> locally then, if that all worked out, install it?

That wont work for the tuning case. We need to know somehow if we are 
updating or creating a new kmemlist.

But there is so much messy stuff in there. Maybe we should start with a 
cleanup patch to increase our comprehension of the situation?




alloc_kmemlist: Some cleanup in preparation for a real memory leak fix

Inspired by Jesper Juhl's patch from today

1. Get rid of err
	We do not set it to anything else but zero.

2. Drop the CONFIG_NUMA stuff.
	There are definitions for alloc_alien_cache and free_alien_cache()
	that do the right thing for the non NUMA case.

3. Better naming of variables.

4. Remove redundant cachep->nodelists[node] expressions.

Signed-off-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>

Index: linux-2.6.16-rc6-mm2/mm/slab.c
===================================================================
--- linux-2.6.16-rc6-mm2.orig/mm/slab.c	2006-03-21 17:45:02.000000000 -0800
+++ linux-2.6.16-rc6-mm2/mm/slab.c	2006-03-21 17:49:16.000000000 -0800
@@ -3421,37 +3421,38 @@ static int alloc_kmemlist(struct kmem_ca
 {
 	int node;
 	struct kmem_list3 *l3;
-	int err = 0;
+	struct array_cache *new_shared;
+	struct array_cache **new_alien;
 
 	for_each_online_node(node) {
-		struct array_cache *nc = NULL, *new;
-		struct array_cache **new_alien = NULL;
-#ifdef CONFIG_NUMA
+
 		new_alien = alloc_alien_cache(node, cachep->limit);
 		if (!new_alien)
 			goto fail;
-#endif
-		new = alloc_arraycache(node, cachep->shared*cachep->batchcount,
+
+		new_shared = alloc_arraycache(node, cachep->shared*cachep->batchcount,
 					0xbaadf00d);
-		if (!new)
+		if (!new_shared)
 			goto fail;
+
 		l3 = cachep->nodelists[node];
 		if (l3) {
+			struct array_cache *shared = l3->shared;
+
 			spin_lock_irq(&l3->list_lock);
 
-			nc = cachep->nodelists[node]->shared;
-			if (nc)
-				free_block(cachep, nc->entry, nc->avail, node);
+			if (shared)
+				free_block(cachep, shared->entry, shared->avail, node);
 
-			l3->shared = new;
-			if (!cachep->nodelists[node]->alien) {
+			l3->shared = new_shared;
+			if (!l3->alien) {
 				l3->alien = new_alien;
 				new_alien = NULL;
 			}
 			l3->free_limit = (1 + nr_cpus_node(node)) *
 					cachep->batchcount + cachep->num;
 			spin_unlock_irq(&l3->list_lock);
-			kfree(nc);
+			kfree(shared);
 			free_alien_cache(new_alien);
 			continue;
 		}
@@ -3462,16 +3463,15 @@ static int alloc_kmemlist(struct kmem_ca
 		kmem_list3_init(l3);
 		l3->next_reap = jiffies + REAPTIMEOUT_LIST3 +
 				((unsigned long)cachep) % REAPTIMEOUT_LIST3;
-		l3->shared = new;
+		l3->shared = new_shared;
 		l3->alien = new_alien;
 		l3->free_limit = (1 + nr_cpus_node(node)) *
 					cachep->batchcount + cachep->num;
 		cachep->nodelists[node] = l3;
 	}
-	return err;
+	return 0;
 fail:
-	err = -ENOMEM;
-	return err;
+	return -ENOMEM;
 }
 
 struct ccupdate_struct {

^ permalink raw reply

* Re: [PATCH 04/15] libata: ata_scsi_queuecmd cleanup
From: Jeff Garzik @ 2006-03-22  1:51 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172304.k2HN4LDp014215@d03av03.boulder.ibm.com>

Brian King wrote:
> Encapsulate part of ata_scsi_queuecmd so that it can be
> reused by future SAS patches.
> 
> Signed-off-by: Brian King <brking@us.ibm.com>
> ---
> 
>  libata-dev-bjking1/drivers/scsi/libata-scsi.c |   26 ++++++++++++++++----------
>  1 files changed, 16 insertions(+), 10 deletions(-)
> 
> diff -puN drivers/scsi/libata-scsi.c~libata_scsi_queuecmd drivers/scsi/libata-scsi.c
> --- libata-dev/drivers/scsi/libata-scsi.c~libata_scsi_queuecmd	2006-03-14 13:55:38.000000000 -0600
> +++ libata-dev-bjking1/drivers/scsi/libata-scsi.c	2006-03-14 13:55:38.000000000 -0600
> @@ -2565,6 +2565,21 @@ static inline void ata_scsi_dump_cdb(str
>  #endif
>  }
>  
> +static void __ata_scsi_queuecmd(struct scsi_cmnd *cmd, void (*done)(struct scsi_cmnd *),

static inline, please


> +				struct ata_port *ap, struct ata_device *dev)
> +{
> +	if (dev->class == ATA_DEV_ATA) {
> +		ata_xlat_func_t xlat_func = ata_get_xlat_func(dev,
> +							      cmd->cmnd[0]);
> +
> +		if (xlat_func)
> +			ata_scsi_translate(ap, dev, cmd, done, xlat_func);
> +		else
> +			ata_scsi_simulate(ap, dev, cmd, done);
> +	} else
> +		ata_scsi_translate(ap, dev, cmd, done, atapi_xlat);
> +}
> +
>  /**
>   *	ata_scsi_queuecmd - Issue SCSI cdb to libata-managed device
>   *	@cmd: SCSI command to be sent
> @@ -2605,16 +2620,7 @@ int ata_scsi_queuecmd(struct scsi_cmnd *
>  		goto out_unlock;
>  	}
>  
> -	if (dev->class == ATA_DEV_ATA) {
> -		ata_xlat_func_t xlat_func = ata_get_xlat_func(dev,
> -							      cmd->cmnd[0]);
> -
> -		if (xlat_func)
> -			ata_scsi_translate(ap, dev, cmd, done, xlat_func);
> -		else
> -			ata_scsi_simulate(ap, dev, cmd, done);
> -	} else
> -		ata_scsi_translate(ap, dev, cmd, done, atapi_xlat);
> +	__ata_scsi_queuecmd(cmd, done, ap, dev);

might as well kill the out_unlock goto target, and do something like

	if (likely(dev))
		__ata_scsi_queuecmd()
	else
		BAD TARGET


^ permalink raw reply

* [ALSA - driver 0000951]: Fix bugs with early IRQs mishandling, missing silence fill, and wrong timing calculations
From: bugtrack @ 2006-03-22  1:51 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=951> 
======================================================================
Reported By:                charles_levert
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   951
Category:                   CORE - pcm
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             2.4.22
======================================================================
Date Submitted:             02-28-2005 21:26 CET
Last Modified:              03-22-2006 02:51 CET
======================================================================
Summary:                    Fix bugs with early IRQs mishandling, missing
silence fill, and wrong timing calculations
Description: 
A patch is forthcoming.

Here is the text from the patch preamble.

    This patch is against alsa-driver-1.0.8.
    It covers:
        alsa-kernel/core/pcm_lib.c
        alsa-kernel/include/pcm.h
        alsa-kernel/core/pcm_native.c
        alsa-kernel/core/oss/pcm_oss.c
    The main changes are in the first listed file.

    An original bug description was filed
    under "[ALSA - driver] PCI - cmipci":
        <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=946>
    since the problems were first observed on this hardware.

    The patch fixes the following problems:

     -- Properly handle early IRQs in
        snd_pcm_update_hw_ptr_interrupt() in pcm_lib.c.

        This does occur, at least with CMI8738MC6 hardware.

        This bug had a major impact that caused the DMAs
        to run for too long and irritating noise to be
        heard at the end of playback.

     -- Properly compute estimated time of next interrupt
        in snd_pcm_update_hw_ptr_interrupt() in pcm_lib.c;
        this is no longer done with a
        "... % runtime->period_size" kludge (which didn't
        even attempt to round to nearest instead of merely
        truncating).

     -- Test whether hw_avail is big enough to handle
        the next runtime->period_size in
        snd_pcm_update_hw_ptr_post() in pcm_lib.c,
        otherwise call snd_pcm_tick_prepare() to
        tentatively set up a timer if needed (to be able
        to take earlier action in that case).

     -- Centralize all folding of values with regard to
        runtime->boundary in the new snd_pcm_next_buf()
        function in pcm_lib.c.

        All relevant values are now systematically in
        coherent synchronization without resorting to the
        ugly and error-prone "value %= runtime->boundary"
        kludge all over the place; unobvious wrapping
        conditions testing is no longer needed in these
        places.

        A safe zone worth one runtime->buffer_size is now
        kept on the left side of the operating interval,
        just like it was the case for the right side;
        this is necessary for proper simplified operation.

     -- Direct manipulations of values with respect to
        runtime->boundary needed to be brought in line
        with new proper practices (and thus simplified)
        in pcm.h, pcm_lib.c, pcm_native.c, and pcm_oss.c.

     -- Isolate the second part of
        snd_pcm_playback_silence() in the new
        snd_pcm_playback_silence_fill() function in
        pcm_lib.c.

        This makes the code more readable since the
        task this performs should not be confused with
        what is done in the remaining first part of
        snd_pcm_playback_silence().

        The isolated code is unchanged.

     -- Rewrite the remaining first part of
        snd_pcm_playback_silence() to properly handle all
        situations, including computing minimum silence
        insertion even when "runtime->silence_size == 0".

        This is needed for proper operation of the aplay
        program, for one, and is much more forgiving on the
        user; insertion of silence samples in user space
        was always useless and a wrong solution anyway (but
        user space specification of kernel space silence
        insertion is useful and still very much supported).

        The code is now much more straightforward to read.

        Updates of runtime->control->appl_ptr (due
        to the user writing samples) and updates to
        runtime->status->hw_ptr (due to the audio hardware
        consuming samples) are now _both_ properly
        accounted for in all cases; the new code makes
        this much more obvious.

     -- All calls to snd_pcm_playback_silence() in
        pcm_lib.c and pcm_native.c must no longer be under
        the "runtime->silence_size > 0" condition.

     -- Properly perform rounded-up integer division in
        snd_pcm_system_tick_set() in pcm_lib.c.

        This only had a minor impact.

     -- Properly compute distance to next interrupt in
        snd_pcm_tick_prepare() in pcm_lib.c; again, avoid
        using any "... % runtime->period_size" kludge.

     -- The usage of runtime->rate in
        snd_pcm_tick_prepare() in pcm_lib.c was incorrect,
        regarless of other changes.

        The impact was that the timer was systematically
        set to 1 single tick when it needed to be set to
        typically hundreds of ticks.

     -- The usage of runtime->sleep_min in
        snd_pcm_tick_prepare() in pcm_lib.c was incorrect,
        regarless of other changes.

        The impact was that the number of ticks for
        the timer was not properly adjusted up to what
        sleep_min is documented to mean, when needed.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0000946 Early playback DMA IRQ with CMI8738MC6 ...
======================================================================

----------------------------------------------------------------------
 tiwai - 03-18-05 18:12 
----------------------------------------------------------------------
IMO, snd_pcm_timer_set() is confusing with the functions in pcm_timer.c.
Also, if we use snd_pcm_timer_set(), we should rename
snd_pcm_tick_prepare(), too.

----------------------------------------------------------------------
 rlrevell - 03-22-06 02:51 
----------------------------------------------------------------------
What is the status of this bug?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-28-05 21:26 charles_levert New Issue                                    
02-28-05 21:26 charles_levert Kernel Version            => 2.4.22          
02-28-05 21:29 charles_levert File Added: early-irqs.patch                    
03-01-05 09:36 perex          Relationship added       related to 0000946  
03-01-05 09:40 perex          Note Added: 0003755                          
03-01-05 11:15 charles_levert Note Added: 0003757                          
03-02-05 09:22 Clemens LadischNote Added: 0003761                          
03-02-05 13:01 charles_levert Note Added: 0003768                          
03-02-05 13:39 perex          Note Added: 0003771                          
03-02-05 14:53 charles_levert Note Added: 0003776                          
03-03-05 14:21 charles_levert File Added: hz-int-div.0b03.patch                 
  
03-03-05 14:22 charles_levert File Added: rate-sleep-ticks.0b03.patch           
        
03-03-05 14:23 charles_levert File Added: appl_ptr-boundary.0b03.patch          
         
03-03-05 14:23 charles_levert File Added: early-irqs.0b03.patch                 
  
03-03-05 14:37 charles_levert Note Added: 0003786                          
03-03-05 15:03 perex          Note Added: 0003787                          
03-03-05 15:33 charles_levert File Added: rate-sleep-ticks.0b03x.patch          
         
03-03-05 15:34 charles_levert Note Added: 0003788                          
03-03-05 15:52 perex          Note Added: 0003789                          
03-03-05 16:05 perex          Note Added: 0003790                          
03-03-05 20:30 rlrevell       Note Added: 0003792                          
03-04-05 03:34 charles_levert Note Added: 0003795                          
03-04-05 04:46 charles_levert Note Added: 0003797                          
03-04-05 06:26 charles_levert Note Added: 0003798                          
03-04-05 11:00 perex          Note Added: 0003799                          
03-04-05 11:01 perex          Note Edited: 0003799                         
03-04-05 11:47 charles_levert File Added: timer_usec.0b05.patch                 
  
03-04-05 11:57 charles_levert Note Added: 0003800                          
03-18-05 00:07 charles_levert Note Added: 0003987                          
03-18-05 18:12 tiwai          Note Added: 0003998                          
03-22-06 02:51 rlrevell       Note Added: 0008788                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: [PATCH] fix memory leak in mm/slab.c::alloc_kmemlist()  (try #3)
From: Andrew Morton @ 2006-03-22  1:46 UTC (permalink / raw)
  To: Christoph Lameter; +Cc: jesper.juhl, penberg, linux-kernel
In-Reply-To: <Pine.LNX.4.64.0603211732420.14503@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@sgi.com> wrote:
>
> On Wed, 22 Mar 2006, Jesper Juhl wrote:
> 
> > Fix memory leak in mm/slab.c::alloc_kmemlist().
> > If one allocation fails we have to roll-back all allocations made up to the 
> > point of failure.
> 
> Sorry but you cannot roll back. alloc_kmemlist() could have been used for
> tuning the cpucache while accesses to the slab continue. "Rolling back" 
> would partially destroy the slab for some nodes and likely cause the 
> system to crash. We can only roll back if this is actually an initial 
> allocation and we are assured that the whole thing is not yet in use.

Well that's a big pickle.  How about allocating everything first, saving it
locally then, if that all worked out, install it?


^ permalink raw reply

* [ALSA - driver 0001850]: source available
From: bugtrack @ 2006-03-22  1:48 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1850> 
======================================================================
Reported By:                coz
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1850
Category:                   PCI - echoaudio
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               ubuntu/breezy/Debian
Kernel Version:             2.6.12.10.386
======================================================================
Date Submitted:             02-16-2006 13:05 CET
Last Modified:              03-22-2006 02:48 CET
======================================================================
Summary:                    source available
Description: 
can't start layla24
======================================================================

----------------------------------------------------------------------
 coz - 03-22-06 02:38 
----------------------------------------------------------------------
hello,
 well the problem is when I installall of the required elements I still
get no sound. i also get no errors.
 As I metioned before, a fellow from ubuntu even wlked me through this and
he was stumped as well.
i hae noidea , apparently, how to do this but even with someone who is
familiar with alsa installation it turned out not to work.
 So, I can keep trying, alsa driver first then lib then tools then u
tilities right/
i can try again. thanks
 Coz

----------------------------------------------------------------------
 rlrevell - 03-22-06 02:48 
----------------------------------------------------------------------
What is CONFIG_FW_LOADER set to in your kernel config?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-16-06 13:05 coz            New Issue                                    
02-16-06 13:05 coz            Distribution              => ubuntu/breezy/Debian
02-16-06 13:05 coz            Kernel Version            => 2.6.12.10.386   
02-18-06 13:34 pochini        Note Added: 0008119                          
02-20-06 03:30 coz            Note Added: 0008140                          
02-20-06 22:02 pochini        Note Added: 0008150                          
03-13-06 19:49 coz            Note Added: 0008456                          
03-13-06 22:38 pochini        Note Added: 0008465                          
03-13-06 23:02 johnrigg       Note Added: 0008466                          
03-16-06 14:54 coz            Note Added: 0008605                          
03-18-06 22:02 pochini        Note Added: 0008676                          
03-18-06 22:07 pochini        Note Edited: 0008676                         
03-19-06 16:05 coz            Note Added: 0008690                          
03-20-06 22:10 pochini        Note Added: 0008725                          
03-22-06 02:38 coz            Note Added: 0008781                          
03-22-06 02:48 rlrevell       Note Added: 0008787                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* [ALSA - driver 0000415]: Terratec EWS88D and clockword sync (Ice1712)
From: bugtrack @ 2006-03-22  1:47 UTC (permalink / raw)
  To: alsa-devel


The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=415> 
======================================================================
Reported By:                Michele Spinolo
Assigned To:                rlrevell
======================================================================
Project:                    ALSA - driver
Issue ID:                   415
Category:                   PCI - ice1712
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     resolved
Distribution:               Suse
Kernel Version:             2.6.5
Resolution:                 fixed
Fixed in Version:           
======================================================================
Date Submitted:             07-30-2004 12:14 CEST
Last Modified:              03-22-2006 02:47 CET
======================================================================
Summary:                    Terratec EWS88D and clockword sync (Ice1712)
Description: 
Up to four Terratec EWS88D cards can be installed in one system, allowing
an internal connection to sync the clocks.
Using Envy24control "clockword sync" option is not present, so it is not
possible to internally sync multiple cards if s/pdif in/out is used for
other purposes.

======================================================================

----------------------------------------------------------------------
 rlrevell - 03-22-06 02:47 
----------------------------------------------------------------------
Fixed in recent versions

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-30-04 12:14 Michele SpinoloNew Issue                                    
07-30-04 12:14 Michele SpinoloDistribution              => Suse            
07-30-04 12:14 Michele SpinoloKernel Version            => 2.6.5           
11-24-04 19:12 Michele SpinoloIssue Monitored: Michele Spinolo                  
 
03-22-06 02:47 rlrevell       Status                   new => resolved     
03-22-06 02:47 rlrevell       Resolution               open => fixed       
03-22-06 02:47 rlrevell       Assigned To               => rlrevell        
03-22-06 02:47 rlrevell       Note Added: 0008786                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* Re: [PATCH 01/15] libata: Setup nbytes in ata_sg_init_one
From: Jeff Garzik @ 2006-03-22  1:46 UTC (permalink / raw)
  To: Brian King; +Cc: linux-ide, linux-scsi
In-Reply-To: <200603172303.k2HN3voJ028508@d01av02.pok.ibm.com>

Brian King wrote:
> Setup nbytes in ata_sg_init_one to the total transfer length
> of the command.
> 
> Signed-off-by: Brian King <brking@us.ibm.com>
> ---
> 
>  libata-dev-bjking1/drivers/scsi/libata-core.c |    1 +
>  1 files changed, 1 insertion(+)
> 
> diff -puN drivers/scsi/libata-core.c~libata_setup_nbytes drivers/scsi/libata-core.c
> --- libata-dev/drivers/scsi/libata-core.c~libata_setup_nbytes	2006-03-17 15:35:26.000000000 -0600
> +++ libata-dev-bjking1/drivers/scsi/libata-core.c	2006-03-17 15:35:26.000000000 -0600
> @@ -2887,6 +2887,7 @@ void ata_sg_init_one(struct ata_queued_c
>  	qc->n_elem = 1;
>  	qc->orig_n_elem = 1;
>  	qc->buf_virt = buf;
> +	qc->nbytes = buflen;

Why?

This is largely an internal variable used by the ATAPI code.

	Jeff




^ permalink raw reply

* [ALSA - driver 0000656]: ICE1712 and multiple cards clock sync
From: bugtrack @ 2006-03-22  1:46 UTC (permalink / raw)
  To: alsa-devel


The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=656> 
======================================================================
Reported By:                Michele Spinolo
Assigned To:                rlrevell
======================================================================
Project:                    ALSA - driver
Issue ID:                   656
Category:                   PCI - ice1712
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     resolved
Distribution:               Fedora Core 1
Kernel Version:             2.4.26
Resolution:                 fixed
Fixed in Version:           
======================================================================
Date Submitted:             11-19-2004 09:41 CET
Last Modified:              03-22-2006 02:45 CET
======================================================================
Summary:                    ICE1712 and multiple cards clock sync
Description: 
I have set up my PC with 3 Terratec EWS88D cards, based on ICE1712 chip.

They offer the chance to be synched one to each other, defining a master
one
and using an internal connector to send the clock signal.

The problem is that using both envy24control or alsa control panel there
is
no option releated to this feature, so multiple boards clock sync is
impossible to be used.
======================================================================

----------------------------------------------------------------------
 rlrevell - 03-22-06 02:45 
----------------------------------------------------------------------
Fixed in recent versions

Issue History
Date Modified  Username       Field                    Change              
======================================================================
11-19-04 09:41 Michele SpinoloNew Issue                                    
11-19-04 09:41 Michele SpinoloDistribution              => Fedora Core 1   
11-19-04 09:41 Michele SpinoloKernel Version            => 2.4.26          
11-24-04 19:12 Michele SpinoloIssue Monitored: Michele Spinolo                  
 
03-22-06 02:45 rlrevell       Status                   new => resolved     
03-22-06 02:45 rlrevell       Resolution               open => fixed       
03-22-06 02:45 rlrevell       Assigned To               => rlrevell        
03-22-06 02:45 rlrevell       Note Added: 0008785                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply

* [ALSA - driver 0000222]: Request for Microphone support.
From: bugtrack @ 2006-03-22  1:44 UTC (permalink / raw)
  To: alsa-devel


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=222> 
======================================================================
Reported By:                dolphy
Assigned To:                tiwai
======================================================================
Project:                    ALSA - driver
Issue ID:                   222
Category:                   PPC - powermac
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Distribution:               Debian
Kernel Version:             2.6.5
======================================================================
Date Submitted:             04-19-2004 13:47 CEST
Last Modified:              03-22-2006 02:44 CET
======================================================================
Summary:                    Request for Microphone support.
Description: 
I know my imac (ilamp model) has a microphone but no way to get it working
with alsa. Is it supported ? Is it just alsamixer not supporting it ?
======================================================================

----------------------------------------------------------------------
 tiwai - 04-23-04 17:37 
----------------------------------------------------------------------
the codec chip on snapper is different from the tumbler, so it's
not easy.  looking at the source code of drawin would be the only
proper way.

----------------------------------------------------------------------
 rlrevell - 03-22-06 02:44 
----------------------------------------------------------------------
Is this fixed in recent ALSA versions?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
04-19-04 13:47 dolphy         New Issue                                    
04-19-04 13:47 dolphy         Distribution              => Debian          
04-19-04 13:47 dolphy         Kernel Version            => 2.6.5           
04-20-04 12:47 tiwai          Note Added: 0000874                          
04-20-04 12:53 dolphy         Note Added: 0000877                          
04-20-04 12:56 tiwai          Note Added: 0000879                          
04-20-04 17:27 dolphy         Note Added: 0000887                          
04-23-04 17:37 tiwai          Note Added: 0000910                          
01-04-06 17:14 schwab         Issue Monitored: schwab                      
03-22-06 02:44 rlrevell       Note Added: 0008784                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

^ permalink raw reply


This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.