From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000344]: usx2y driver causes kernel oops
Date: Mon, 28 Jun 2004 09:51:32 +0200 [thread overview]
Message-ID: <b91ed716f4a666d8fe510e91fc12ecd2@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=0000344
======================================================================
Reported By: maggoi
Assigned To: karsten
======================================================================
Project: ALSA - driver
Bug ID: 344
Category: USB - usb-usx2y
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Gentoo
Kernel Version: 2.6.6
======================================================================
Date Submitted: 06-24-2004 18:06 CEST
Last Modified: 06-28-2004 09:51 CEST
======================================================================
Summary: usx2y driver causes kernel oops
Description:
While playing a soundfile using my Tascam us-122 (Alsa Module snd-usx2y)
after a few seconds the sound stutters and i get an Kernel oops.
This is not happening if I use Jack.
I'm using the latest alsa drivers 1.0.5. With kernel 2.6.6.
dmesg:
Debug: sleeping function called from invalid context at mm/slab.c:1996
in_atomic():1, irqs_disabled():1
[<c01152f7>] __might_sleep+0xb7/0xe0
[<c013be33>] __kmalloc+0xa3/0xb0
[<c026dad1>] usb_alloc_urb+0x21/0x60
[<f89b3775>] snd_usX2Y_substream_prepare+0xd5/0x1c0 [snd_usb_usx2y]
[<f89b3397>] snd_usX2Y_urb_play_start+0xa7/0x170 [snd_usb_usx2y]
[<f89b35bf>] snd_usX2Y_pcm_play_trigger+0x3f/0x50 [snd_usb_usx2y]
[<f89490e8>] snd_pcm_do_start+0x28/0x30 [snd_pcm]
[<f8948dc9>] snd_pcm_action_single+0x39/0x70 [snd_pcm]
[<f8948f12>] snd_pcm_action_lock_irq+0x92/0x1e0 [snd_pcm]
[<c0112a8c>] do_page_fault+0x34c/0x54e
[<f894c4d7>] snd_pcm_common_ioctl1+0x167/0x2f0 [snd_pcm]
[<f894c6c0>] snd_pcm_playback_ioctl1+0x60/0x3b0 [snd_pcm]
[<c0150a32>] vfs_write+0xd2/0x130
[<c0162f20>] sys_ioctl+0x100/0x270
[<c010413b>] syscall_call+0x7/0xb
======================================================================
----------------------------------------------------------------------
karsten - 06-24-2004 22:17 CEST
----------------------------------------------------------------------
As a test please replace all occurrences of GFP_KERNEL in
function snd_usX2Y_substream_prepare() with GFP_ATOMIC.
That function is in alsa-driver/usb/usx2y/usbusx2yaudio.c.
Thanks for debugging.
----------------------------------------------------------------------
maggoi - 06-28-2004 09:51 CEST
----------------------------------------------------------------------
Thank's a lot, this has solved the issue. Will you include this fix in
further versions?
Bug History
Date Modified Username Field Change
======================================================================
06-24-04 18:06 maggoi New Bug
06-24-04 18:06 maggoi Distribution => Gentoo
06-24-04 18:06 maggoi Kernel Version => 2.6.6
06-24-04 22:17 karsten Bugnote Added: 0001337
06-28-04 09:51 maggoi Bugnote Added: 0001343
======================================================================
-------------------------------------------------------
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
next reply other threads:[~2004-06-28 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 7:51 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 7:36 [ALSA - driver 0000344]: usx2y driver causes kernel oops bugtrack
2005-08-30 10:27 bugtrack
2004-09-30 23:27 bugtrack
2004-08-25 8:02 bugtrack
2004-07-15 9:48 noreply
2004-06-30 22:43 noreply
2004-06-30 13:44 noreply
2004-06-29 8:45 noreply
2004-06-28 19:04 noreply
2004-06-28 8:34 noreply
2004-06-24 20:17 noreply
2004-06-24 16:06 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=b91ed716f4a666d8fe510e91fc12ecd2@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.