Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Peter L Jones <peter@drealm.org.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: 2.5.40bk4 "bad"!
Date: Tue, 08 Oct 2002 12:57:17 +0200	[thread overview]
Message-ID: <s5hn0pp2o6q.wl@alsa2.suse.de> (raw)
In-Reply-To: <200210060056.08839@advent.drealm.org.uk>

At Sun, 6 Oct 2002 00:56:08 +0100,
Peter L Jones wrote:
> 
> Hi there,
> 
> Is this a known problem?
> 
> kernel: bad: scheduling while atomic!
> kernel: Call Trace:
> kernel:  [schedule+61/724] schedule+0x3d/0x2d4
> kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
> kernel:  [interruptible_sleep_on+91/144] interruptible_sleep_on+0x5b/0x90
> kernel:  [default_wake_function+0/52] default_wake_function+0x0/0x34
> kernel:  [<cb8d5bce>] snd_seq_cell_alloc+0x9a/0x15c [snd-seq]
> kernel:  [<cb8d5d09>] snd_seq_event_dup+0x79/0x1e8 [snd-seq]
> kernel:  [<cb8d6773>] snd_seq_enqueue_event+0xa3/0xac [snd-seq]
> kernel:  [<cb8d2ed8>] snd_seq_client_enqueue_event+0xbc/0xf4 [snd-seq]
> kernel:  [<cb8d311d>] snd_seq_write+0x1a9/0x1ec [snd-seq]
> kernel:  [vfs_write+177/304] vfs_write+0xb1/0x130
> kernel:  [sys_write+42/60] sys_write+0x2a/0x3c
> kernel:  [syscall_call+7/11] syscall_call+0x7/0xb

it looks related with the spinlock and preemption.
can you try the latest cvs version?  i hope it's fixed now.


ciao,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2002-10-08 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05 23:56 2.5.40bk4 "bad"! Peter L Jones
2002-10-08 10:57 ` Takashi Iwai [this message]

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=s5hn0pp2o6q.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=peter@drealm.org.uk \
    /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