* 2.6.7+BK bad: scheduling while atomic! (ALSA?)
@ 2004-07-06 9:34 Meelis Roos
2004-07-06 19:26 ` Christian Kujau
2004-07-06 23:17 ` Meelis Roos
0 siblings, 2 replies; 5+ messages in thread
From: Meelis Roos @ 2004-07-06 9:34 UTC (permalink / raw)
To: Linux Kernel list
While running alsamixergui -c 2, I got alsamixergui killed with SEGV and
the following in dmesg. Additionally, mplayer has big problems playing
through ALSA with messages
alsa-space: xrun of at least 30,716 msecs. resetting stream 0,0% 0 0 90%
and I haven't yet found the place where to turn on xrun debugging.
x86 UP PREEMPT.
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c014aa58>] sys_write+0x38/0x60
[<c0103eee>] work_resched+0x5/0x16
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c0113aa4>] do_page_fault+0x104/0x4ff
[<c023e91f>] __kfree_skb+0xaf/0x140
[<c011635f>] sys_sched_yield+0x3f/0x50
[<c0155621>] coredump_wait+0x31/0xa0
[<c0155783>] do_coredump+0xf3/0x1b1
[<c01e405c>] pty_write+0x10c/0x110
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c01048d1>] error_code+0x2d/0x38
[<c0120ed6>] __dequeue_signal+0xc6/0x160
[<c0120f93>] dequeue_signal+0x23/0x80
[<c012284b>] get_signal_to_deliver+0x24b/0x330
[<c0103c85>] do_signal+0x85/0x100
[<c012787c>] __kernel_text_address+0x1c/0x30
[<c0104b03>] print_context_stack+0x23/0x60
[<c0103eee>] work_resched+0x5/0x16
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c0104b83>] show_trace+0x43/0x80
[<c02987b8>] schedule+0x278/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c0103d35>] do_notify_resume+0x35/0x38
[<c0103f12>] work_notifysig+0x13/0x15
note: alsamixergui[3027] exited with preempt_count 1
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c013c21f>] zap_pmd_range+0x3f/0x60
[<c0115186>] try_to_wake_up+0x96/0xb0
[<c013c27d>] unmap_page_range+0x3d/0x70
[<c013c46e>] unmap_vmas+0x1be/0x1f0
[<c0140087>] exit_mmap+0x77/0x150
[<c0116e55>] mmput+0x55/0x70
[<c011ad23>] do_exit+0x143/0x3e0
[<c011b052>] do_group_exit+0x32/0xa0
[<c0122839>] get_signal_to_deliver+0x239/0x330
[<c0103c85>] do_signal+0x85/0x100
[<c012787c>] __kernel_text_address+0x1c/0x30
[<c0104b03>] print_context_stack+0x23/0x60
[<c0103eee>] work_resched+0x5/0x16
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c0104b83>] show_trace+0x43/0x80
[<c02987b8>] schedule+0x278/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c0103d35>] do_notify_resume+0x35/0x38
[<c0103f12>] work_notifysig+0x13/0x15
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.7+BK bad: scheduling while atomic! (ALSA?)
2004-07-06 9:34 2.6.7+BK bad: scheduling while atomic! (ALSA?) Meelis Roos
@ 2004-07-06 19:26 ` Christian Kujau
2004-07-06 23:17 ` Meelis Roos
1 sibling, 0 replies; 5+ messages in thread
From: Christian Kujau @ 2004-07-06 19:26 UTC (permalink / raw)
To: Linux Kernel list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Meelis Roos schrieb:
> While running alsamixergui -c 2, I got alsamixergui killed with SEGV and
> the following in dmesg. Additionally, mplayer has big problems playing
yes, "me too". upon using ALSA (same .config as earlier kernels) i got:
kernel: bad: scheduling while atomic!
kernel: [<c031dc56>] schedule+0x486/0x4c0
kernel: [<c0118764>] sys_sched_yield+0x44/0x60
kernel: [<c0160bc2>] coredump_wait+0x32/0xa0
kernel: [<c010b557>] convert_fxsr_to_user+0x107/0x170
kernel: [<c0160d31>] do_coredump+0x101/0x20b
kernel: [<c0123a0c>] free_uid+0x1c/0x70
kernel: [<c01242a5>] __dequeue_signal+0x105/0x180
kernel: [<c0124355>] dequeue_signal+0x35/0xb0
kernel: [<c012605f>] get_signal_to_deliver+0x30f/0x3f0
kernel: [<c0103e61>] do_signal+0x91/0x170
kernel: [<c01479cd>] do_mmap_pgoff+0x3ed/0x6f0
kernel: [<c010aa66>] sys_mmap2+0x86/0xd0
kernel: [<c0116070>] do_page_fault+0x0/0x57e
kernel: [<c0103f77>] do_notify_resume+0x37/0x3c
kernel: [<c0104156>] work_notifysig+0x13/0x15
kernel: bad: scheduling while atomic!
kernel: [<c031dc56>] schedule+0x486/0x4c0
kernel: [<c01174ca>] wake_up_state+0x1a/0x20
kernel: [<c031dd48>] wait_for_completion+0x78/0xe0
kernel: [<c0117db0>] default_wake_function+0x0/0x20
kernel: [<c0117db0>] default_wake_function+0x0/0x20
kernel: [<c0160b1c>] zap_threads+0x4c/0xc0
kernel: [<c0160c18>] coredump_wait+0x88/0xa0
kernel: [<c010b557>] convert_fxsr_to_user+0x107/0x170
kernel: [<c0160d31>] do_coredump+0x101/0x20b
kernel: [<c0123a0c>] free_uid+0x1c/0x70
kernel: [<c01242a5>] __dequeue_signal+0x105/0x180
kernel: [<c0124355>] dequeue_signal+0x35/0xb0
kernel: [<c012605f>] get_signal_to_deliver+0x30f/0x3f0
kernel: [<c0103e61>] do_signal+0x91/0x170
kernel: [<c01479cd>] do_mmap_pgoff+0x3ed/0x6f0
kernel: [<c010aa66>] sys_mmap2+0x86/0xd0
kernel: [<c0116070>] do_page_fault+0x0/0x57e
kernel: [<c0103f77>] do_notify_resume+0x37/0x3c
kernel: [<c0104156>] work_notifysig+0x13/0x15
kernel: note: xmms[17326] exited with preempt_count 1
this is latest 2.6.7-bk, debian/unstable (i386), but my kernel is
tainted (nvidia).
Christian.
- --
BOFH excuse #26:
first Saturday after first full moon in Winter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA6vzt+A7rjkF8z0wRAu6YAJ9GdFOhhU/QmqTT3ynvGnCvKrmnJQCgkuQB
nt71aEqg6gMPflfyyHUQwo0=
=jvHX
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.7+BK bad: scheduling while atomic! (ALSA?)
2004-07-06 9:34 2.6.7+BK bad: scheduling while atomic! (ALSA?) Meelis Roos
2004-07-06 19:26 ` Christian Kujau
@ 2004-07-06 23:17 ` Meelis Roos
2004-07-07 2:40 ` Wen-chien Jesse Sung
1 sibling, 1 reply; 5+ messages in thread
From: Meelis Roos @ 2004-07-06 23:17 UTC (permalink / raw)
To: Linux Kernel list
> alsa-space: xrun of at least 30,716 msecs. resetting stream 0,0% 0 0 90%
> and I haven't yet found the place where to turn on xrun debugging.
OK, recompiled ALSA with debug on and now I could turn on xrun_debug:
XRUN: pcmC0D0p
Stack pointer is garbage, not printing trace
XRUN: pcmC0D0p
[<d897472a>] snd_pcm_period_elapsed+0x27a/0x3b0 [snd_pcm]
[<c0115a87>] __wake_up_common+0x37/0x60
[<d894a61b>] snd_via82xx_interrupt+0xfb/0x120 [snd_via82xx]
[<c011fdc9>] update_wall_time+0x9/0x40
[<c0105f80>] handle_IRQ_event+0x30/0x60
[<c0106310>] do_IRQ+0xc0/0x1a0
=======================
[<c0104834>] common_interrupt+0x18/0x20
[<c0102053>] default_idle+0x23/0x30
[<c01020bc>] cpu_idle+0x2c/0x40
[<c039b73b>] start_kernel+0x14b/0x170
[<c039b380>] unknown_bootoption+0x0/0x160
XRUN: pcmC0D0p
Stack pointer is garbage, not printing trace
XRUN: pcmC0D0p
[<d897472a>] snd_pcm_period_elapsed+0x27a/0x3b0 [snd_pcm]
[<c0115a87>] __wake_up_common+0x37/0x60
[<d894a61b>] snd_via82xx_interrupt+0xfb/0x120 [snd_via82xx]
[<c0105f80>] handle_IRQ_event+0x30/0x60
[<c0106310>] do_IRQ+0xc0/0x1a0
=======================
[<c0104834>] common_interrupt+0x18/0x20
[<c0102053>] default_idle+0x23/0x30
[<c01020bc>] cpu_idle+0x2c/0x40
[<c039b73b>] start_kernel+0x14b/0x170
[<c039b380>] unknown_bootoption+0x0/0x160
XRUN: pcmC0D0p
[<d897472a>] snd_pcm_period_elapsed+0x27a/0x3b0 [snd_pcm]
[<c0115a87>] __wake_up_common+0x37/0x60
[<d894a61b>] snd_via82xx_interrupt+0xfb/0x120 [snd_via82xx]
[<c011fdc9>] update_wall_time+0x9/0x40
[<c0105f80>] handle_IRQ_event+0x30/0x60
[<c0106310>] do_IRQ+0xc0/0x1a0
=======================
[<c0104834>] common_interrupt+0x18/0x20
[<c0102053>] default_idle+0x23/0x30
[<c01020bc>] cpu_idle+0x2c/0x40
[<c039b73b>] start_kernel+0x14b/0x170
[<c039b380>] unknown_bootoption+0x0/0x160
XRUN: pcmC0D0p
[<d897472a>] snd_pcm_period_elapsed+0x27a/0x3b0 [snd_pcm]
[<c022fd01>] psmouse_interrupt+0x91/0x2c0
[<c0115a87>] __wake_up_common+0x37/0x60
[<d894a61b>] snd_via82xx_interrupt+0xfb/0x120 [snd_via82xx]
[<c011fdc9>] update_wall_time+0x9/0x40
[<c0105f80>] handle_IRQ_event+0x30/0x60
[<c0106310>] do_IRQ+0xc0/0x1a0
=======================
[<c0104834>] common_interrupt+0x18/0x20
[<c0102053>] default_idle+0x23/0x30
[<c01020bc>] cpu_idle+0x2c/0x40
[<c039b73b>] start_kernel+0x14b/0x170
[<c039b380>] unknown_bootoption+0x0/0x160
XRUN: pcmC0D0p
[<d897472a>] snd_pcm_period_elapsed+0x27a/0x3b0 [snd_pcm]
[<c0115a87>] __wake_up_common+0x37/0x60
[<d894a61b>] snd_via82xx_interrupt+0xfb/0x120 [snd_via82xx]
[<c0105f80>] handle_IRQ_event+0x30/0x60
[<c0106310>] do_IRQ+0xc0/0x1a0
=======================
[<c0104834>] common_interrupt+0x18/0x20
[<c0102053>] default_idle+0x23/0x30
[<c01020bc>] cpu_idle+0x2c/0x40
[<c039b73b>] start_kernel+0x14b/0x170
[<c039b380>] unknown_bootoption+0x0/0x160
This was with onboard Via sound. With snd_ens1371 I get only
XRUN: pcmC0D0p
Stack pointer is garbage, not printing trace
on each xrun but xrun happens only once on mplayer startup (but ther is
still no sound). Alsamixergui aslo still segfaults (with double
segfault as it actually did before):
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c014aa58>] sys_write+0x38/0x60
[<c0103eee>] work_resched+0x5/0x16
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c0113aa4>] do_page_fault+0x104/0x4ff
[<c023e91f>] __kfree_skb+0xaf/0x140
[<c011635f>] sys_sched_yield+0x3f/0x50
[<c0155621>] coredump_wait+0x31/0xa0
[<c0155783>] do_coredump+0xf3/0x1b1
[<c01e405c>] pty_write+0x10c/0x110
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c01048d1>] error_code+0x2d/0x38
[<c0120ed6>] __dequeue_signal+0xc6/0x160
[<c0120f93>] dequeue_signal+0x23/0x80
[<c012284b>] get_signal_to_deliver+0x24b/0x330
[<c0103c85>] do_signal+0x85/0x100
[<c012787c>] __kernel_text_address+0x1c/0x30
[<c0104b03>] print_context_stack+0x23/0x60
[<c0103eee>] work_resched+0x5/0x16
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c0104b83>] show_trace+0x43/0x80
[<c02987b8>] schedule+0x278/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c0103d35>] do_notify_resume+0x35/0x38
[<c0103f12>] work_notifysig+0x13/0x15
note: alsamixergui[3345] exited with preempt_count 1
bad: scheduling while atomic!
[<c02989a3>] schedule+0x463/0x470
[<c013c21f>] zap_pmd_range+0x3f/0x60
[<c0115186>] try_to_wake_up+0x96/0xb0
[<c013c27d>] unmap_page_range+0x3d/0x70
[<c013c46e>] unmap_vmas+0x1be/0x1f0
[<c0140087>] exit_mmap+0x77/0x150
[<c0116e55>] mmput+0x55/0x70
[<c011ad23>] do_exit+0x143/0x3e0
[<c011b052>] do_group_exit+0x32/0xa0
[<c0122839>] get_signal_to_deliver+0x239/0x330
[<c0103c85>] do_signal+0x85/0x100
[<c012787c>] __kernel_text_address+0x1c/0x30
[<c0104b03>] print_context_stack+0x23/0x60
[<c0103eee>] work_resched+0x5/0x16
[<c0114f5b>] recalc_task_prio+0x8b/0x180
[<c0104b83>] show_trace+0x43/0x80
[<c02987b8>] schedule+0x278/0x470
[<c014a984>] vfs_write+0xe4/0x120
[<c01139a0>] do_page_fault+0x0/0x4ff
[<c0103d35>] do_notify_resume+0x35/0x38
[<c0103f12>] work_notifysig+0x13/0x15
Will try turning off PREEMPT next.
--
Meelis Roos
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.7+BK bad: scheduling while atomic! (ALSA?)
2004-07-06 23:17 ` Meelis Roos
@ 2004-07-07 2:40 ` Wen-chien Jesse Sung
2004-07-07 8:53 ` Meelis Roos
0 siblings, 1 reply; 5+ messages in thread
From: Wen-chien Jesse Sung @ 2004-07-07 2:40 UTC (permalink / raw)
To: Linux Kernel list
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
> Alsamixergui aslo still segfaults (with double
> segfault as it actually did before):
>
> bad: scheduling while atomic!
> [<c02989a3>] schedule+0x463/0x470
> [<c014a984>] vfs_write+0xe4/0x120
> [<c014aa58>] sys_write+0x38/0x60
> [<c0103eee>] work_resched+0x5/0x16
Hi,
I got similar output here when I try to run xmms with alsa plugin.
Solved with modified sound/core/control.c. Maybe you can try this tiny
patch. :)
--
Best Regards,
Wen-chien Jesse Sung
--- linux/sound/core/control.c.orig 2004-07-06 18:38:55.000000000 +0800
+++ linux/sound/core/control.c 2004-07-06 18:39:30.000000000 +0800
@@ -1114,7 +1114,7 @@ static ssize_t snd_ctl_read(struct file
wait_queue_t wait;
if ((file->f_flags & O_NONBLOCK) != 0 || result > 0) {
err = -EAGAIN;
- goto out;
+ goto __end;
}
init_waitqueue_entry(&wait, current);
add_wait_queue(&ctl->change_sleep, &wait);
@@ -1135,7 +1135,7 @@ static ssize_t snd_ctl_read(struct file
kfree(kev);
if (copy_to_user(buffer, &ev, sizeof(snd_ctl_event_t))) {
err = -EFAULT;
- goto __end;
+ goto out;
}
spin_lock_irq(&ctl->read_lock);
buffer += sizeof(snd_ctl_event_t);
[-- Attachment #2: 這是數位加簽的郵件 --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-07-07 8:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-06 9:34 2.6.7+BK bad: scheduling while atomic! (ALSA?) Meelis Roos
2004-07-06 19:26 ` Christian Kujau
2004-07-06 23:17 ` Meelis Roos
2004-07-07 2:40 ` Wen-chien Jesse Sung
2004-07-07 8:53 ` Meelis Roos
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.