From: Eddahbi Karim <installation_fault_association@yahoo.fr>
To: Jaroslav Kysela <perex@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re² : Alsa create high problems...
Date: Sat, 24 Jan 2004 07:01:04 +0100 [thread overview]
Message-ID: <1074924064.3799.17.camel@gamux> (raw)
In-Reply-To: <Pine.LNX.4.58.0401230957131.1875@pnote.perex-int.cz>
Le ven 23/01/2004 à 09:57, Jaroslav Kysela a écrit :
> On Fri, 23 Jan 2004, Jaroslav Kysela wrote:
> > Ok, let's go. Can you try which files exactly affects the playback?
> > If you find one file, can you remove code step-by-step from routines in
> > linux/sound/core/pcm.c snd*read() functions (locate function by strings
> > in the proc file).
> >
> > I suspect that snd_pcm_stream_lock_irq() and snd_pcm_stream_unlock_irq()
> > will affect this (note that you must remove these calls together).
>
> Also enabling CONFIG_DEBUG_SPINLOCK in your kernel setup might help us.
>
Ok,
So... I've located the file which unlocks the problem while 1 second.
It's /proc/asound/card0/pcm0p/sub0/status.
The function in pcm.c is :
snd_pcm_substream_proc_status_read
I remove it from the routines, it doesn't settle the problem but it
removes /proc/asound/card0/pcm0p/sub0/status which let me without any
way to solve the sound problem anymore (unless kill :P).
I'll try to remove both lock/unlock irq functions and I'll tell you the
problem.
Btw I can't do any report from my kernel 2.6.2-rc1 because the ACPI
seems broken again and my modem don't work so I need to reboot on my
2.6.0 for reporting ;)
--
Eddahbi Karim <installation_fault_association@yahoo.fr>
Installation Fault
next prev parent reply other threads:[~2004-01-24 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 23:41 Re : Alsa create high problems Eddahbi Karim
2004-01-23 6:33 ` Eddahbi Karim
[not found] ` <Pine.LNX.4.58.0401230936130.1875@pnote.perex-int.cz>
[not found] ` <Pine.LNX.4.58.0401230957131.1875@pnote.perex-int.cz>
2004-01-24 6:01 ` Eddahbi Karim [this message]
2004-01-27 11:07 ` Eddahbi Karim
2004-01-27 20:54 ` Eddahbi Karim
2004-01-28 10:57 ` Eddahbi Karim
2004-01-29 1:18 ` Eddahbi Karim
2004-02-05 4:08 ` Eddahbi Karim
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=1074924064.3799.17.camel@gamux \
--to=installation_fault_association@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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 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.