: modprobe goes into D-state when inserting snd-ad1816a
A NOTE has been added to this issue.
======================================================================
<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: feedback Distribution: Debian Sarge Kernel Version: 2.6.12.3 and 2.6.13-rc4 ====================================================================== Date Submitted: 08-02-2005 16:56 CEST Last Modified: 08-15-2005 14:33 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-13-05 22:51
----------------------------------------------------------------------
Your assumption that the problem might be within the pnp code seems to be correct. I've added some printk-Statements to the AD1816A driver as shipped with vanilla Linux 2.6.13-rc6 preserving line numbers. Here is what happens:
The second call of pnp_request_card_device() in line 125 of ad1816a.c returns NULL, thus snd_card_ad1816a_pnp() returns(-EBUSY) in line 128. The error is passed on to snd_ad1816a_pnp_detect() by snd_card_ad1816a_probe() in line 200. snd_ad1816a_pnp_detect(), which was obviously called by the pnp code, returns the error in line 271. pnp_register_card_driver() in line 314 which initially triggered the call to snd_ad1816a_pnp_detect() does not return.
----------------------------------------------------------------------
perex - 08-15-05 14:33
----------------------------------------------------------------------
Could you try the attached patch (pnp-card.c.patch) ?
It's for the PnP core in kernel not for ALSA.
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
======================================================================
-------------------------------------------------------
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