From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001300]: modprobe goes into D-state when inserting snd-ad1816a
Date: Thu, 18 Aug 2005 13:16:53 +0200 [thread overview]
Message-ID: <f4e14d6e4316872412cc57b3d01f47f5@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1300>
======================================================================
Reported By: tek01
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1300
Category: ISA - ad1816a
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: Debian Sarge
Kernel Version: 2.6.12.3 and 2.6.13-rc4
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 08-02-2005 16:56 CEST
Last Modified: 08-18-2005 13:16 CEST
======================================================================
Summary: modprobe goes into D-state when inserting
snd-ad1816a
Description:
Under Linux 2.6.12.3 and Linux 2.6.13-rc4 inserting the snd-ad1816a module
causes the modprobe process to go into D-state forever.
Linux 2.6.11.12 has been tested and is working fine.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0001301 Kernel OSS emulation stops working afte...
related to 0001302 Clicking noise when using kphone with t...
======================================================================
----------------------------------------------------------------------
tek01 - 08-16-05 12:56
----------------------------------------------------------------------
You are absolutly right. The snd-mpu401 module gets loaded earlier during
system startup. After unloading the snd-mpu401 module the snd-ad1816a
module loads fine.
I'll check if #1301 and #1302 are still valid with 2.6.13-rc6.
----------------------------------------------------------------------
perex - 08-18-05 13:16
----------------------------------------------------------------------
Okay, so the bug is resolved. I need only push the patch to mainstream
Linux kernel.
Issue History
Date Modified Username Field Change
======================================================================
08-02-05 16:56 tek01 New Issue
08-02-05 16:56 tek01 Distribution => Debian Sarge
08-02-05 16:56 tek01 Kernel Version => 2.6.12.3 and
2.6.13-rc4
08-02-05 18:27 Adrian Bunk Issue Monitored: Adrian Bunk
08-02-05 22:26 perex Note Added: 0005609
08-03-05 10:10 perex Relationship added related to 0001301
08-03-05 10:11 perex Relationship added related to 0001302
08-09-05 12:57 perex Assigned To => perex
08-09-05 12:57 perex Status new => feedback
08-13-05 22:51 tek01 Note Added: 0005811
08-15-05 14:32 perex File Added: pnp-card.c.patch
08-15-05 14:33 perex Note Added: 0005818
08-15-05 20:34 tek01 Note Added: 0005821
08-16-05 01:25 perex Note Added: 0005825
08-16-05 12:56 tek01 Note Added: 0005828
08-18-05 13:16 perex Status feedback => resolved
08-18-05 13:16 perex Resolution open => fixed
08-18-05 13:16 perex Note Added: 0005846
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-18 11:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 11:16 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 10:56 [ALSA - driver 0001300]: modprobe goes into D-state when inserting snd-ad1816a bugtrack
2005-08-15 23:25 bugtrack
2005-08-15 18:34 bugtrack
2005-08-15 12:33 bugtrack
2005-08-13 20:51 bugtrack
2005-08-09 10:57 bugtrack
2005-08-03 8:11 bugtrack
2005-08-03 8:10 bugtrack
2005-08-02 20:26 bugtrack
2005-08-02 14:56 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=f4e14d6e4316872412cc57b3d01f47f5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox