From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Courtier-Dutton Subject: Re: Re: [linux-audio-dev] Re: any update on the pcmcia bug blocking Audigy2 notebook sound card driver development Date: Wed, 10 Aug 2005 11:22:44 +0100 Message-ID: <42F9D574.1090508@superbug.co.uk> References: <1ed860e3050807084449b0daac@mail.gmail.com> <20050807104332.320aec48.akpm@osdl.org> <1123519224.16205.5.camel@cmn37.stanford.edu> <1123570490.26998.1.camel@mindpipe> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Takashi Iwai Cc: Lee Revell , Fernando Lopez-Lezcano , The Linux Audio Developers' Mailing List , Raymond Lai , linux-pcmcia@lists.infradead.org, alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Takashi Iwai wrote: >At Tue, 09 Aug 2005 02:54:49 -0400, >Lee Revell wrote: > > >>[added James to cc:] >> >>On Mon, 2005-08-08 at 09:40 -0700, Fernando Lopez-Lezcano wrote: >> >> >>>On Sun, 2005-08-07 at 10:43, Andrew Morton wrote: >>> >>> >>>>Raymond Lai wrote: >>>> >>>> >>>>>Hi all, >>>>> >>>>>I remember there's a kernel pcmcia bug preventing the development for >>>>>the Audigy2 pcmcia notebook sound card driver. >>>>> >>>>>See http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Creative_Labs#matrix >>>>> >>>>>Is there any new updates on the situation? Has the bug been fixed? or >>>>>anyone working on it? >>>>> >>>>> >>>>Is it related to http://bugzilla.kernel.org/show_bug.cgi?id=4788 ? >>>> >>>> >>>I think not, the card in question is the Creative Audigy 2 ZS PCMCIA >>>card. I have one I can't use yet :-( The kernel locks hard when ALSA >>>tries to load the driver. >>> >>> >>Maybe we should have the emu10k1 driver not claim the device until this >>is fixed. It's better than locking the machine (this behavior has been >>confirmed by several other users). >> >> > >It seems to have the same PCI ID. If the probing phase already >triggers the hang up, we can't stop it. > > >Takashi > > > The PCI ID is the same, but the subsystem ID is different. All PCI probing works ok, so we can detect it and disable the driver for now. The hang happens on the first inb/w/d(.) function call. outb/w/d() commands do not hang the system. I don't really see the point of changing anything. The system might hang, but just removing the PCMCIA card gets everything going again. It is still a PCMCIA cardbus bug in the kernel that is the real cause. I have had very little time recently to look at it. It is extremely difficult to track down the reason for this bug, so I think that fixing this is a long way away at present. James ------------------------------------------------------- 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