From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000425]: usb-usx2y: System lockup on PCM device open (OHCI)
Date: Sat, 25 Sep 2004 17:18:06 +0200 (CEST) [thread overview]
Message-ID: <20040925151806.93C6D25019@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000425
======================================================================
Reported By: rncbc
Assigned To: karsten
======================================================================
Project: ALSA - driver
Bug ID: 425
Category: USB - usb-usx2y
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Distribution: Mandrake 10.0 Official
Kernel Version: 2.6.8-rc2
======================================================================
Date Submitted: 08-06-2004 10:53 CEST
Last Modified: 09-25-2004 17:18 CEST
======================================================================
Summary: usb-usx2y: System lockup on PCM device open (OHCI)
Description:
As of ALSA 1.0.6rc1, the US-x2y PCM device driver module exposes a hard
conflict on OHCI based USB controllers, causing a complete system lockup
-- kernel oops on an interrupt handler -- exactly upon starting or
openning the PCM device for audio playback.
======================================================================
----------------------------------------------------------------------
rncbc - 08-06-2004 12:16 CEST
----------------------------------------------------------------------
Just to add, that this issue does not occur as of previous
alsa-driver-1.0.5a, same platform, kernel or hardware. Seems to have been
introduced on CVS semewhere since mid-July. Something about "no sleeping"
in ALSA's pcm START/STOP callbacks, but no sure.
----------------------------------------------------------------------
karsten - 09-23-2004 20:52 CEST
----------------------------------------------------------------------
that seams to have something to do with a threaded IRQ10?
Does it also happen with hardirq_preempting off?
Please geneate oops traces from the 2.6.9-rc2-mmx-Sy kernel also.
If those traces also happen in non usx2y-module area,
find out, which snd_*() call triggers the oops.
Check wether it happens if you disable hyperthreads.
Erm, did I fail to include some important errorchecks after calling
kernel/usb functions?
Run with at least ALSA debug options enabled. Other kernel debug options
may help too.
----------------------------------------------------------------------
rncbc - 09-24-2004 09:43 CEST
----------------------------------------------------------------------
Please note that this problem is not related to the voluntary-preempt
kernel patch nor is SMP/HT related. The machine where its beeing exposed
is a Compaq Presario 2516EA (laptop), P4 2.533GHz (UP, no-HT enabled).
Also FWIW, it doesn't matter if ACPI is enabled or not. The point where
the kernel oops occurs seems to be always under ohci_hcd (see
hard-screenshot).
----------------------------------------------------------------------
rncbc - 09-25-2004 17:18 CEST
----------------------------------------------------------------------
Now using 2.6.9-rc2-mm3-S6 (voluntary-preempt).
One thing I've noticed, but just related to VP, is that while having
hardirq-preempt=1 and /proc/irq/10/ohci_hcd/threaded=1, the kernel
doesn't
crash when opening the PCM hw device (either via jackd or aplay). But
still useless or zombie anyway. It does crash however when I unplug my
US-224 (switch its power down).
With hardirq-preempt=0 or /proc/irq/10/ohci_hcd/threaded=0, I get the
same
old bad behavior: a kernel oops somewhere on the ohci_irq handling,
almost
immediately when the PCM device is open (e.g. by jackd or aplay). Yet
another screenshot added here (usx2y-oops4.png).
Bug History
Date Modified Username Field Change
======================================================================
08-06-04 10:53 rncbc New Bug
08-06-04 10:53 rncbc File Added: usx2y-oops3.png
08-06-04 10:53 rncbc Distribution => Mandrake 10.0 Official
08-06-04 10:53 rncbc Kernel Version => 2.6.8-rc2
08-06-04 12:16 rncbc Bugnote Added: 0001538
09-23-04 20:52 karsten Bugnote Added: 0001849
09-24-04 09:43 rncbc Bugnote Added: 0001858
09-25-04 17:13 rncbc File Added: usx2y-oops4.png
09-25-04 17:18 rncbc Bugnote Added: 0001911
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next reply other threads:[~2004-09-25 15:18 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 15:18 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 14:42 [ALSA - driver 0000425]: usb-usx2y: System lockup on PCM device open (OHCI) bugtrack
2004-10-26 19:49 bugtrack
2004-10-26 19:47 bugtrack
2004-10-26 11:47 bugtrack
2004-10-22 7:48 bugtrack
2004-10-20 9:30 bugtrack
2004-10-20 5:39 bugtrack
2004-10-19 13:56 bugtrack
2004-10-19 11:50 bugtrack
2004-10-18 21:07 bugtrack
2004-10-17 20:46 bugtrack
2004-10-17 11:32 bugtrack
2004-10-17 0:20 bugtrack
2004-10-16 21:11 bugtrack
2004-10-16 14:31 bugtrack
2004-10-16 11:58 bugtrack
2004-10-16 1:05 bugtrack
2004-10-15 22:52 bugtrack
2004-10-15 22:36 bugtrack
2004-10-15 10:55 bugtrack
2004-10-15 10:06 bugtrack
2004-10-14 23:40 bugtrack
2004-10-14 23:30 bugtrack
2004-10-14 13:26 bugtrack
2004-10-14 9:21 bugtrack
2004-10-11 19:13 bugtrack
2004-10-10 18:27 bugtrack
2004-10-10 16:45 bugtrack
2004-10-10 13:37 bugtrack
2004-10-10 19:39 ` Werner Schweer
2004-10-10 18:24 ` Karsten Wiese
2004-10-10 23:28 ` Werner Schweer
2004-10-10 22:31 ` Rui Nuno Capela
2004-10-11 0:19 ` Karsten Wiese
2004-10-11 9:54 ` Werner Schweer
2004-10-13 23:59 ` Karsten Wiese
2004-10-14 21:17 ` Werner Schweer
2004-10-08 20:30 bugtrack
2004-10-08 1:40 bugtrack
2004-10-07 17:51 bugtrack
2004-10-07 13:55 bugtrack
2004-10-07 8:42 bugtrack
2004-09-30 23:23 bugtrack
2004-09-30 0:11 bugtrack
2004-09-30 0:00 bugtrack
2004-09-29 23:44 bugtrack
2004-09-28 20:01 bugtrack
2004-09-28 13:16 bugtrack
2004-09-27 21:49 bugtrack
2004-09-27 11:51 bugtrack
2004-09-27 10:10 Rui Nuno Capela
2004-09-26 20:18 bugtrack
2004-09-26 20:00 bugtrack
2004-09-26 13:43 bugtrack
2004-09-26 13:28 bugtrack
2004-09-25 15:45 bugtrack
2004-09-24 7:43 bugtrack
2004-09-23 18:52 bugtrack
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=20040925151806.93C6D25019@server.perex-int.cz \
--to=bugtrack@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.