From mboxrd@z Thu Jan 1 00:00:00 1970 From: The Source Subject: Re: Backported sbxfi driver (UNTESTED!) Date: Sat, 11 Oct 2008 20:28:23 +0400 Message-ID: <48F0D427.1070503@gmail.com> References: <1223583478.5018.0.camel@home> <1223619975.4700.2.camel@home> <6d00fe310810100939h6cd61e0cg7817c7f54f6261f6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by alsa0.perex.cz (Postfix) with ESMTP id 3AE3C1037F2 for ; Sat, 11 Oct 2008 18:29:44 +0200 (CEST) Received: by fg-out-1718.google.com with SMTP id 16so677201fgg.44 for ; Sat, 11 Oct 2008 09:29:26 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Takashi Iwai ?????: > At Fri, 10 Oct 2008 20:39:48 +0400, > The Source wrote: > >> 2008/10/10 Takashi Iwai >> >> At Fri, 10 Oct 2008 01:26:15 -0500, >> Ted T. Logian wrote: >> > >> > >> > >> > On Fri, 2008-10-10 at 08:01 +0200, Takashi Iwai wrote: >> > > At Thu, 09 Oct 2008 15:17:58 -0500, >> > > Ted T. Logian wrote: >> > > > >> > > > Sorry for the multiple posts, but once I rmmod snd-sbxfi, running >> mixer does >> > > > fine. It seems if I have snd-sbxfi loaded and I run alsamixer, it >> locks the >> > > > entire system. >> > > >> > > So, do you mean loading the driver itself doesn't lock up? If so, >> > > it's better than I expected. >> > > >> > > Did you run ever PCM playback/capture before that? This is more >> > > dangerous :) >> > > >> > > Also, please give your hardware details, as there are different models >> > > for X-Fi, and some are handled pretty differently. >> > > >> > > [BTW, please stop top-posting, and avoid HTML mails for ML. It's easy >> > > to switch to normal (plain) mail mode on Gmail, just a click.] >> > > >> > > >> > > thanks, >> > > >> > > Takashi >> > >> > >> > I think perhaps from uninstalling pulseaudio I got further. I can use >> > mixer now, and it even has a "Master" device, but nothing else... >> > >> > however, I do get a lock up later. >> > >> > I get this from running aplay, too, if this helps... >> >> Thanks! That's rather a stupid bug. >> The patch is below. >> >> Takashi >> >> diff --git a/sound/pci/sbxfi/sbxfi.c b/sound/pci/sbxfi/sbxfi.c >> index 8066bf4..8a0eea0 100644 >> --- a/sound/pci/sbxfi/sbxfi.c >> +++ b/sound/pci/sbxfi/sbxfi.c >> @@ -831,7 +831,7 @@ static struct sbxfi_port *sbxfi_port_alloc(struct >> sbxfi *chip, >> port->src[0] = src; >> port->src[1] = src + 1; >> spin_lock_irq(&chip->port_lock); >> - list_add(&chip->port_list, &port->list); >> + list_add(&port->list, &chip->port_list); >> spin_unlock_irq(&chip->port_lock); >> return port; >> } >> _______________________________________________ >> Alsa-devel mailing list >> Alsa-devel@alsa-project.org >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel >> >> Hello, I have tried the driver with the fix you provided, but I couldn't get >> anything. Kernel panic on any attempt to use sound or mixer. Also kernel panic >> several seconds after Xorg starts. Each crash causes either hang or reboot so >> I couldn't get any error messages. If there are some logs left, please tell me >> where they are and I'll send them to you. >> My card is X-Fi Platinum Fatality Champion Series. >> > > For testing, first try without X but just use Linux console, so that > you have a better chance to see Oops messages. It's pretty important > to see whether it's an Oops or a panic. Also, double-check whether > you really installed the corrected drivers. Often it's missing in the > right place by stupid reasons. > > For first tests, don't use any sound server. Try with aplay like: > % aplay -Dhw foo.wav > Try first 96kHz samples, 48kHz samples, and then others. > > > thanks, > > Takashi > > aplay in console causes reboot, sorry.