From alsa-user-owner@alsa.jcu.cz  Sat Jun 13 19:25:58 1998
Received: from elektron.elka.pw.edu.pl (root@elektron.elka.pw.edu.pl [148.81.63.249])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id TAA11302
	for <alsa-user@alsa.jcu.cz>; Sat, 13 Jun 1998 19:24:40 +0200
Received: from default ([148.81.63.249]) by elektron.elka.pw.edu.pl with SMTP id <4484-628>; Sat, 13 Jun 1998 19:23:51 +0200
From: "Piniek (aka Piotr Ingling)" <pingling@elka.pw.edu.pl>
To: alsa-user@alsa.jcu.cz
Date: 	Sat, 13 Jun 1998 19:26:26 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: GUS ACE problems with 2.1.105 kernel
Message-Id: <19980613172351Z4484-628+1@elektron.elka.pw.edu.pl>
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Hi!

I own two sndcards - SBPro and GUS ACE. I decided to try the ALSA drivers and 
here my problems started. SB part works OK. But I can't load the GUS module - 
all I get is that oops when I issue a 'modprobe snd-gusclassic' command:

Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 01e07000, %cr3 = 01e07000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c28219a0>]
EFLAGS: 00010293
eax: c17f8df0   ebx: c17a6104   ecx: c2821e94   edx: 00000002
esi: 00000000   edi: 00000000   ebp: c17a62d8   esp: c179fecc
ds: 0018   es: 0018   ss: 0018
Process insmod (pid: 196, process nr: 20, stackpage=c179f000)
Stack: c17a6104 c17f8df0 00000000 00000256 c17a62d8 c2835908 00000000 c2837468
       00000000 00000000 c17f8dcc 00000001 c17f8df0 00000000 c2837000 00000001
       00000005 00000000 c2837a64 00000250 c2837000 00000000 c17a642c c28376cd
Call Trace: [<c2835908>] [<c2837468>] [<c2837000>] [<c2837a64>] [<c2837000>] 
[<c28376cd>] [<c2837000>]
       [<c2835b34>] [<c0114f8a>] [<c011e252>] [<c2815000>] [<c2830000>]
[<c2837048>] [<c01097fc>]
Code: 8b 06 8b 00 c1 e0 02 8d 1c 07 83 3c 9d fc 1e 82 c2 00 74 1c
snd-gus: Device or resource busy

My GUS is set to irq 11, addr 0x250 and dma 5. I was trying to set both dmas 
to the same value, but (just before the oops) i got a message that playback 
dma cannot be assigned because it's being already used.
Before the ALSA adventure I was using the Ultra-2.72c drivers and everything 
was working perfectly so it is not a h/w problem. And as the ALSA drivers are 
based (at least I think they are) on these from Ultra they should be working 
as well...
Any suggestions? My linux is rh4.0, kernel 2.1.105, modutils 2.1.71, 
alsadrivers 0.1.3. H/w is P150. My conf.modules is based upon the INSTALL doc.

Thanks for any help.

                         Piotr Ingling
e-mail: pingling@elka.pw.edu.pl
------------------------------------------------------------
Ceny na gieldzie komputerowej w Warszawie:
        http://home.elka.pw.edu.pl/~pingling/ceny-pl.html

