From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000376]: inserting maestro3 hangs system
Date: Thu, 7 Apr 2005 21:02:02 +0200 [thread overview]
Message-ID: <871d665270026b614104868ed0dc69f4@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=376>
======================================================================
Reported By: tmarble
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 376
Category: PCI - maestro3
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
Distribution: Debian unstable
Kernel Version: 2.4.26
======================================================================
Date Submitted: 07-11-2004 18:30 CEST
Last Modified: 04-07-2005 21:02 CEST
======================================================================
Summary: inserting maestro3 hangs system
Description:
modprobe snd-maestro3 consistently hangs the system.
======================================================================
----------------------------------------------------------------------
tmarble - 07-15-04 19:40
----------------------------------------------------------------------
I actually think that I had 1.0.4 working on 2.4.26... but it's been
long enough that I don't have accurate records.
Instead of using my custom kernel I have also tried the pre-built
debian kernel (2.4.26) and alsa-modules (1.0.5a) and they fail
the same way.
I also tried to rebuild my kernel so that soundcore was a loadable
module, but that didn't help.
My current thinking is that either there is some inherent
breakage in the 1.0.5+ driver OR it has to do with my module
configuration OR it has to do with something in the 2.4.26 kernel
(with debian patches) that recently changed.
My next step is to install a stock 2.6.7 kernel from scratch
with the pre-build (latest) alsa-modules and see if that works.
I'll let you know.
--Tom
----------------------------------------------------------------------
jdthood - 04-07-05 21:02
----------------------------------------------------------------------
Submitter: Has there been any progress on this issue?
Issue History
Date Modified Username Field Change
======================================================================
07-11-04 18:30 tmarble New Issue
07-11-04 18:30 tmarble Distribution => Debian unstable
07-11-04 18:30 tmarble Kernel Version => 2.4.26
07-13-04 07:37 tmarble File Added: 2.4.26-tm2.config.txt
07-13-04 07:38 tmarble File Added: System.map-2.4.26-tm2.txt
07-13-04 07:38 tmarble File Added: alsa-1.0.conf
07-13-04 07:39 tmarble File Added: depmod.txt
07-13-04 07:40 tmarble File Added: depends.txt
07-13-04 07:41 tmarble File Added: 20040712233907.modules.txt
07-13-04 07:41 tmarble File Added: 20040712233907.ksyms.txt
07-13-04 07:43 tmarble Note Added: 0001412
07-15-04 11:25 tiwai Note Added: 0001428
07-15-04 19:40 tmarble Note Added: 0001437
04-07-05 21:02 jdthood Note Added: 0004368
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-04-07 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 19:02 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 8:37 [ALSA - driver 0000376]: inserting maestro3 hangs system bugtrack
2005-04-15 17:37 bugtrack
2005-04-15 12:21 bugtrack
2004-07-15 17:40 noreply
2004-07-15 9:25 noreply
2004-07-13 5:43 noreply
2004-07-11 16:30 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=871d665270026b614104868ed0dc69f4@bugtrack.alsa-project.org \
--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.