From: Jan Killius <jkillius@arcor.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1-ac3 snd_usb_audio problem
Date: Wed, 23 Jul 2003 23:22:18 +0200 [thread overview]
Message-ID: <20030723212218.GA13903@gate.unimatrix> (raw)
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
Hi,
I have a little problem with the ALSA usb driver it doesn't work.
I think it is a general problem with the 2.6 kernel scheduler.
However i have attached some dmesg call trace output.
This output comes if i try to play a audio file...
--
Greets
Jan Killius
[-- Attachment #2: calltrace --]
[-- Type: text/plain, Size: 2898 bytes --]
bad: scheduling while atomic!
Call Trace:
[<c01199d9>] schedule+0x3a9/0x3b0
[<c01251ff>] schedule_timeout+0x5f/0xc0
[<c0125190>] process_timeout+0x0/0x10
[<c0260217>] usb_start_wait_urb+0xb7/0x1a0
[<c0119a40>] default_wake_function+0x0/0x30
[<c026036b>] usb_internal_control_msg+0x6b/0x80
[<c0260416>] usb_control_msg+0x96/0xb0
[<c0260f21>] usb_set_interface+0xc1/0x220
[<c025f9c0>] hcd_endpoint_disable+0x0/0x1a0
[<e493843f>] set_format+0xbf/0x2b0 [snd_usb_audio]
[<e4938694>] snd_usb_pcm_prepare+0x34/0x50 [snd_usb_audio]
[<e49239b4>] snd_pcm_do_prepare+0x14/0x40 [snd_pcm]
[<e4922e09>] snd_pcm_action_single+0x39/0x70 [snd_pcm]
[<e4922f58>] snd_pcm_action_lock_irq+0x98/0xa0 [snd_pcm]
[<e4923a71>] snd_pcm_prepare+0x61/0x80 [snd_pcm]
[<e492631e>] snd_pcm_playback_ioctl1+0x5e/0x450 [snd_pcm]
[<c01250b0>] do_timer+0xe0/0xf0
[<c0162893>] sys_ioctl+0xf3/0x280
[<c0118040>] do_page_fault+0x0/0x453
[<c010918b>] syscall_call+0x7/0xb
bad: scheduling while atomic!
Call Trace:
[<c01199d9>] schedule+0x3a9/0x3b0
[<c01251ff>] schedule_timeout+0x5f/0xc0
[<c0125190>] process_timeout+0x0/0x10
[<c0260217>] usb_start_wait_urb+0xb7/0x1a0
[<c0119a40>] default_wake_function+0x0/0x30
[<c026036b>] usb_internal_control_msg+0x6b/0x80
[<c0260416>] usb_control_msg+0x96/0xb0
[<e49382a6>] init_usb_sample_rate+0xb6/0x190 [snd_usb_audio]
[<c025f9c0>] hcd_endpoint_disable+0x0/0x1a0
[<e4938505>] set_format+0x185/0x2b0 [snd_usb_audio]
[<e4938694>] snd_usb_pcm_prepare+0x34/0x50 [snd_usb_audio]
[<e49239b4>] snd_pcm_do_prepare+0x14/0x40 [snd_pcm]
[<e4922e09>] snd_pcm_action_single+0x39/0x70 [snd_pcm]
[<e4922f58>] snd_pcm_action_lock_irq+0x98/0xa0 [snd_pcm]
[<e4923a71>] snd_pcm_prepare+0x61/0x80 [snd_pcm]
[<e492631e>] snd_pcm_playback_ioctl1+0x5e/0x450 [snd_pcm]
[<c01250b0>] do_timer+0xe0/0xf0
[<c0162893>] sys_ioctl+0xf3/0x280
[<c0118040>] do_page_fault+0x0/0x453
[<c010918b>] syscall_call+0x7/0xb
bad: scheduling while atomic!
Call Trace:
[<c01199d9>] schedule+0x3a9/0x3b0
[<c01251ff>] schedule_timeout+0x5f/0xc0
[<c0125190>] process_timeout+0x0/0x10
[<c0260217>] usb_start_wait_urb+0xb7/0x1a0
[<c0119a40>] default_wake_function+0x0/0x30
[<c026036b>] usb_internal_control_msg+0x6b/0x80
[<c0260416>] usb_control_msg+0x96/0xb0
[<e4938302>] init_usb_sample_rate+0x112/0x190 [snd_usb_audio]
[<c025f9c0>] hcd_endpoint_disable+0x0/0x1a0
[<e4938505>] set_format+0x185/0x2b0 [snd_usb_audio]
[<e4938694>] snd_usb_pcm_prepare+0x34/0x50 [snd_usb_audio]
[<e49239b4>] snd_pcm_do_prepare+0x14/0x40 [snd_pcm]
[<e4922e09>] snd_pcm_action_single+0x39/0x70 [snd_pcm]
[<e4922f58>] snd_pcm_action_lock_irq+0x98/0xa0 [snd_pcm]
[<e4923a71>] snd_pcm_prepare+0x61/0x80 [snd_pcm]
[<e492631e>] snd_pcm_playback_ioctl1+0x5e/0x450 [snd_pcm]
[<c01250b0>] do_timer+0xe0/0xf0
[<c0162893>] sys_ioctl+0xf3/0x280
[<c0118040>] do_page_fault+0x0/0x453
[<c010918b>] syscall_call+0x7/0xb
next reply other threads:[~2003-07-23 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 21:22 Jan Killius [this message]
2003-07-24 8:27 ` 2.6.0-test1-ac3 snd_usb_audio problem Takashi Iwai
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=20030723212218.GA13903@gate.unimatrix \
--to=jkillius@arcor.de \
--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;
as well as URLs for NNTP newsgroup(s).