From: Wen-chien Jesse Sung <jesse@cola.voip.idv.tw>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7+BK bad: scheduling while atomic! (ALSA?)
Date: Wed, 07 Jul 2004 10:40:50 +0800 [thread overview]
Message-ID: <1089168049.3892.19.camel@libra> (raw)
In-Reply-To: <Pine.GSO.4.44.0407070206220.24637-100000@math.ut.ee>
[-- 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 --]
next prev parent reply other threads:[~2004-07-07 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-07-07 8:53 ` Meelis Roos
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=1089168049.3892.19.camel@libra \
--to=jesse@cola.voip.idv.tw \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox