All of lore.kernel.org
 help / color / mirror / Atom feed
From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000367]: alsamixer problems with preempt
Date: Tue, 6 Jul 2004 13:31:14 +0200	[thread overview]
Message-ID: <83e9579ce630bfa178a37bb2ed44036d@bugtrack.alsa-project.org> (raw)


A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000367
======================================================================
Reported By:                Safari
Assigned To:                
======================================================================
Project:                    ALSA - driver
Bug ID:                     367
Category:                   CORE - control
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             2.6.7-bk18 + gcc-3.4.0
======================================================================
Date Submitted:             07-06-2004 06:24 CEST
Last Modified:              07-06-2004 13:31 CEST
======================================================================
Summary:                    alsamixer problems with preempt
Description: 
when I for example mute channels in alsamixer, I get "bad: scheduling while
atomic!".

======================================================================

----------------------------------------------------------------------
 jesse - 07-06-2004 13:31 CEST 
----------------------------------------------------------------------
I got some similar messages here when I try to run xmms with alsa plugin on
2.6.7-bk18.

Jul  6 12:05:10 libra kernel: [<c0105c77>] dump_stack+0x17/0x20
Jul  6 12:05:10 libra kernel: [<c028a300>] schedule+0x4c0/0x4d0
Jul  6 12:05:10 libra kernel: [<c028a77e>] io_schedule+0xe/0x20
Jul  6 12:05:10 libra kernel: [<c0134f05>] __lock_page+0xb5/0xe0
Jul  6 12:05:10 libra kernel: [<c01356e7>]
do_generic_mapping_read+0x397/0x440
Jul  6 12:05:10 libra kernel: [<c0135a30>]
__generic_file_aio_read+0x1d0/0x200
Jul  6 12:05:10 libra kernel: [<c0135b24>] generic_file_read+0x64/0x80
Jul  6 12:05:10 libra kernel: [<c01528a2>] vfs_read+0xa2/0x100
Jul  6 12:05:10 libra kernel: [<c0152ad5>] sys_read+0x35/0x60
Jul  6 12:05:10 libra kernel: [<c0104e89>] sysenter_past_esp+0x52/0x71
Jul  6 12:05:10 libra kernel: [<c0105c77>] dump_stack+0x17/0x20
Jul  6 12:05:10 libra kernel: [<c028a300>] schedule+0x4c0/0x4d0
Jul  6 12:05:10 libra kernel: [<c0104f02>] work_resched+0x5/0x16
Jul  6 12:05:10 libra kernel: [<c0105c77>] dump_stack+0x17/0x20
Jul  6 12:05:10 libra kernel: [<c028a300>] schedule+0x4c0/0x4d0
Jul  6 12:05:10 libra kernel: [<c0104f02>] work_resched+0x5/0x16
Jul  6 12:05:10 libra kernel: [<c0105c77>] dump_stack+0x17/0x20
Jul  6 12:05:10 libra kernel: [<c028a300>] schedule+0x4c0/0x4d0
Jul  6 12:05:10 libra kernel: [<c0104f02>] work_resched+0x5/0x16

After doing this, I can get rid of this problem...

--- 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);

Bug History
Date Modified  Username       Field                    Change              
======================================================================
07-06-04 06:24 Safari         New Bug                                      
07-06-04 06:24 Safari         Kernel Version            => 2.6.7-bk18 +
gcc-3.4.0
07-06-04 13:31 jesse          Bugnote Added: 0001384                       
======================================================================




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com

             reply	other threads:[~2004-07-06 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 11:31 noreply [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-24 11:35 [ALSA - driver 0000367]: alsamixer problems with preempt bugtrack
2004-07-16 10:08 noreply
2004-07-06 12:28 noreply
2004-07-06  4:24 noreply

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=83e9579ce630bfa178a37bb2ed44036d@bugtrack.alsa-project.org \
    --to=noreply@alsa-project.org \
    --cc=alsa-devel@alsa-project.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 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.