From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267957AbUI1QWi (ORCPT ); Tue, 28 Sep 2004 12:22:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267973AbUI1QWi (ORCPT ); Tue, 28 Sep 2004 12:22:38 -0400 Received: from cantor.suse.de ([195.135.220.2]:47289 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S267957AbUI1QWd (ORCPT ); Tue, 28 Sep 2004 12:22:33 -0400 Date: Tue, 28 Sep 2004 18:22:32 +0200 Message-ID: From: Takashi Iwai To: Jan De Luyck Cc: linux-kernel@vger.kernel.org Subject: Re: [2.6.9-rc2] ALSA nm256 driver causes system lockup In-Reply-To: <200409281755.14844.lkml@kcore.org> References: <200409281447.17537.lkml@kcore.org> <200409281755.14844.lkml@kcore.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 MULE XEmacs/21.4 (patch 15) (Security Through Obscurity) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Tue, 28 Sep 2004 17:55:14 +0200, Jan De Luyck wrote: > > On Tuesday 28 September 2004 17:48, Takashi Iwai wrote: > > At Tue, 28 Sep 2004 14:47:17 +0200, > > > > Jan De Luyck wrote: > > > Hello list, > > > > > > I'm trying to configure a laptop (Dell Latitude CXs) with 2.6.9-rc2. All > > > runs well, except the ALSA nm256 driver for the Neomagic Audio chip. > > > Loading this driver results in an immediate and complete system > > > lockup.... > > > > > > I've tried appending "vaio_hack=1" on the kernel command line, but that > > > didn't really do anything. > > > > > > ALSA is compiled as modules. > > > > > > Any pointers? > > > > Try to load snd-nm256 driver before X. The chip uses the video RAM > > for the sound buffer. It seems that X clears all video RAM that > > confuses the sound driver. I.e. if you already started X, there is no > > way back :) > > Yups, so I read in the documentation accompanying the kernel. It's being > loaded by hotplug during bootup, but even at that early stage it locks up > completely. Does changing latitude_workaround = 0 in nm256.c have any influence? Takashi