On Thu, 29 Jan 2004, Thomas Charbonnel wrote: > Hi, > > I noticed this problem today using midi on my setup (alsa 1.0.1, kernel > 2.6.1 with CONFIG_DEBUG_SPINLOCK_SLEEP) : > > Debug: sleeping function called from invalid context at > include/asm/uaccess.h:473 > in_atomic():1, irqs_disabled():1 > Call Trace: > [<c012139c>] __might_sleep+0xac/0xe0 > [<c010b170>] handle_signal+0xd0/0x140 > [<c03955ef>] snd_rawmidi_kernel_read1+0x10f/0x170 > [<c03957e7>] snd_rawmidi_read+0x147/0x1b0 > [<c01131cf>] restore_i387_fxsave+0x8f/0xa0 > [<c015b2f3>] vfs_read+0xd3/0x140 > [<c015b59f>] sys_read+0x3f/0x60 > [<c010b4bb>] syscall_call+0x7/0xb > > I'm sorry I didn't check if this was fixed in 1.0.2, but though it was > worth mentioning. This caused regular (~ 1/second) dropouts in pd while > using midi.
I'm not sure, but it looks like kernel problem. We don't call handle_signal() function from snd_rawmidi_kernel_read1() - you may check this function - scheduling is not involved. I wonder why this function is called from in the spinlock context. Please, report this problem to LKML or try the latest 2.6 kernel. Jaroslav ----- Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel