On Wednesday 26 February 2003 18:59, Patrick Shirkey wrote:
Sorry I must have missed sending this here.
The following has been submitted as a note for the documentation of cs46xx.
sender: [EMAIL PROTECTED]
date: Friday, 03 January 2003
Terratec DMX XFire 1024:
The DMX XFire
are you sure both all kernel sources and alsa drivers are compiled
with the same compiler?
you cannot mix gcc-2.x and gcc-3.x binaries for kernel. the
combination likely causes oops.
I had this problem some time ago. The same compiler was used for
both kernel and ALSA. I assumed it was a
are you sure both all kernel sources and alsa drivers are compiled
with the same compiler?
you cannot mix gcc-2.x and gcc-3.x binaries for kernel. the
combination likely causes oops.
I just tried compiling the kernel with 2.95 and alsa with 3.2.
This combination results in the kind of
I guess another way of dealing with this kind of problem is to use a
semaphore rather than a spinlock, and a workqueue: when the interrupt
comes in, the call to snd_ctl_notify is put on the queue, where it will
later be run in process context, and can safely take the semaphore.
yes,
Got this with today 2.5 BK tree:
Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
[c0113f1a] __might_sleep+0x52/0x58
[c024291a] snd_cs46xx_iec958_put+0x36/0xf8
[c0217f28] snd_ctl_elem_write+0xe0/0x1a4
[c0218360] snd_ctl_ioctl+0x184/0x2c8
On Tuesday 03 December 2002 13:01, Takashi Iwai wrote:
At Tue, 3 Dec 2002 04:07:52 +0100,
Duncan Sands wrote:
Got this with today 2.5 BK tree:
Debug: sleeping function called from illegal context at
include/asm/semaphore.h:119 Call Trace:
[c0113f1a] __might_sleep+0x52/0x58
On Tuesday 03 December 2002 14:56, Takashi Iwai wrote:
At Tue, 3 Dec 2002 04:55:15 +0100,
Duncan Sands wrote:
On Tuesday 03 December 2002 13:01, Takashi Iwai wrote:
At Tue, 3 Dec 2002 04:07:52 +0100,
Duncan Sands wrote:
Got this with today 2.5 BK tree:
Debug: sleeping
yes, basically what snd_ctl_notify() does is the same.
it queues an event and wakes up the sleepers.
thus, it's ok to separate the stuff from the semaphore.
the attached is a patch to rewrite the locks with rwsem.
please check whether it works for you.
This is against alsa cvs and not
The usb subsystem has been pretty unstable lately, so this oops
may not be the fault of snd-usb-audio.
Duncan.
drivers/usb/core/usb.c: deregistering driver snd-usb-audio
Unable to handle kernel paging request at virtual address cc8b4278
printing eip:
cc8b4278
*pde = 0be81067
*pte =
Another point to keep in mind here, is that a lot of people are now
using journaled filesystems, and may just turn off the computer
without shutting down. You could say that they deserve what they
get, but I'm not so sure. Imagine someone using alsamixer to change
mixer settings.
On Friday 27 September 2002 19:53, Takashi Iwai wrote:
except for the check of /proc/asound, the hotplug problem can be
sorted to the following:
1. hotplug may be called before alsa init script.
2. hotplug needs to manage the mixer configuration of plugged /
unplugged devices
On Thursday 26 September 2002 13:49, Takashi Iwai wrote:
At Thu, 26 Sep 2002 10:20:25 +0200, Duncan Sands wrote:
I have a usb webcam with audio plugged into my computer,
and a cs46xx sound card inside.
When I boot the following sequence occurs:
(1) the hotplug subsytem is started
On Thursday 26 September 2002 12:40, Tim Goetze wrote:
Duncan Sands wrote:
(1) the hotplug subsytem is started. This automatically
loads the snd-usb-audio module and the modules it
depends on. In particular /proc/asound/ is created.
(2) the alsasound init script is run. It detects
I have a usb webcam with audio plugged into my computer,
and a cs46xx sound card inside.
When I boot the following sequence occurs:
(1) the hotplug subsytem is started. This automatically
loads the snd-usb-audio module and the modules it
depends on. In particular /proc/asound/ is created.
If alsa is compiled directly into the 2.5.5 kernel (rather than
as modules) then it calls modprobe before the root file system
is mounted. The call of course fails leading to a slew of annoying
error messages.
All the best,
Duncan.
___
Alsa-devel
Actually, the problem is deeper: even if I compile everything as
modules, I still get no such device when trying to read from
/proc/asound entries. I will look into this further myself.
Duncan.
___
Alsa-devel mailing list
[EMAIL PROTECTED]
On Friday 15 February 2002 9:30 am, Guenther Sohler wrote:
did you insmod the snd.o ???
Yes. I have /proc/asound with all entries. They just aren't
readable. The soundcard is detected when I modprobe the
card module (nonetheless /proc/asound/cards is not readable:
no such device). I have
I just gave the 2.5.5-pre1 kernel a whirl. Just to be different,
I compiled all sound support into the kernel rather than as
modules. On startup I get:
Feb 14 15:43:55 baldrick kernel: Advanced Linux Sound Architecture Driver Version
0.9.0beta10.
Feb 14 15:43:55 baldrick kernel: kmod: failed
I got the following in my syslog using CVS alsa of a few days ago
and kernel 2.5.2-dj2. While shutting down:
Jan 23 23:09:24 baldrick kernel: ALSA ../alsa-kernel/core/memory.c:71: Not freed
snd_alloc_kmalloc = 6157848
Jan 23 23:09:24 baldrick kernel: ALSA ../alsa-kernel/core/memory.c:78:
If nobody has comments, I'm ready to prepare a whole patch for Linus
against the actual 2.5.1pre code.
Since there is no need for this patch to support 2.2 kernels, some
simplifications should be possible.
Duncan.
PS: I'm not saying that it is desirable to remove 2.2 support, it's just
a
So I tried to collect as much information as I can about this freezing
bug.
Try using the magic SysRq key to get information (see the
sysrq.txt file in the linux/Documentation directory of your
kernel sources; you will probably have to recompile your
kernel).
Duncan.
21 matches
Mail list logo
