On Saturday 26 July 2003 06:07, Elmar Fasel wrote:
> Hi,
>
> trying to circumvent the problem with the crispy AC97 sound with my
> VIA onboard soundchip (and getting surround sound), I bought a cheap
> Creative Labs Soundblaster Live (CT4760). But now it get's worse...
> :-|
>
> I compiled the module for emu10k1 chip, loading the module works:
> snd-seq-midi 4000 0 (autoclean) (unused)
> snd-emu10k1-synth 4796 0 (autoclean) (unused)
> snd-emux-synth 27644 0 (autoclean) [snd-emu10k1-synth]
> snd-seq-midi-emul 4928 0 (autoclean) [snd-emux-synth]
> snd-seq-virmidi 3256 0 (autoclean) [snd-emux-synth]
> snd-seq-oss 28896 0 (unused)
> snd-seq-midi-event 3048 0 [snd-seq-midi snd-seq-virmidi
> snd-seq-oss]
> snd-seq 36176 2 [snd-seq-midi snd-emux-synth
> snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event]
> snd-pcm-oss 38532 0 (unused)
> snd-mixer-oss 13304 0 [snd-pcm-oss]
> snd-emu10k1 70884 0 [snd-emu10k1-synth]
> snd-pcm 59684 0 [snd-pcm-oss snd-emu10k1]
> snd-timer 14276 0 [snd-seq snd-pcm]
> snd-hwdep 5088 0 [snd-emu10k1]
> snd-util-mem 1264 0 [snd-emux-synth snd-emu10k1]
> snd-page-alloc 4956 0 [snd-emu10k1 snd-pcm]
> snd-rawmidi 13440 0 [snd-seq-midi snd-seq-virmidi
> snd-emu10k1]
> snd-seq-device 4208 0 [snd-seq-midi snd-emu10k1-synth
> snd-emux-synth snd-seq-oss snd-seq snd-emu10k1 snd-rawmidi]
> snd-ac97-codec 39400 0 [snd-emu10k1]
> snd 29892 3 [snd-seq-midi snd-emux-synth
> snd-seq-virmidi snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss
> snd-mixer-oss snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem
> snd-rawmidi snd-seq-device snd-ac97-codec]
>
> But starting any program that uses the also modules gives
> segmentation fault, e.g. alsamixer, and some entries in the kernel
> log:
> <1>Unable to handle kernel NULL pointer dereference at virtual
> address 00000000
> printing eip:
> c0116f63
> *pde = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<c0116f63>] Tainted: P
> EFLAGS: 00010097
> eax: dee8b584 ebx: dee8b584 ecx: 00000000 edx: 00000003
> esi: dee8b588 edi: 00000001 ebp: ce4adf2c esp: ce4adf14
> ds: 0018 es: 0018 ss: 0018
> Process alsamixer (pid: 865, stackpage=ce4ad000)
> Stack: cf9a5b80 d574f7c0 dee8b400 dee8b588 00000286 00000003 dee8b54c
> e08884d5
> dd111700 00000282 dee8b55c d0c8cb80 dee8b55c d0c8cb80 e0889d4d
> dee8b400
> d574f7c0 00000000 d0c8cba0 dee8b55c d574f7c0 dd111700 c158d300
> dcf183c0
> Call Trace: [<e08884d5>] [<e0889d4d>] [<c013698c>] [<c0135945>]
> [<c0135993>]
> [<c0108807>]
>
> Code: 8b 01 85 45 fc 74 4c 31 c0 9c 5e fa c7 01 00 00 00 00 83 79
That is a kernel oops. From 'man ksymoops':
ksymoops extracts kernel Oops reports from the Oops.file and uses
various sources of symbol information to convert the addresses
and code
to meaningful text. Reporting a kernel Oops is meaningless on
its own
because other people do not know what your kernel looks like,
you need
to feed the Oops text through ksymoops then send the ksymoops
output as
part of your bug report.
Oh, and report the ALSA version you are using.
> Stopping also (/etc/init.d/alsa stop) let's the computer freeze.
> Also, manually trying to unload the modules with "rmmod -r $(lsmod |
> grep ^snd | awk '{print $1}')" freezes the computer.
>
> Hopefully I just made some simple mistake, but once again I'm stuck
> and have no idea where to start fixing this...
> Except of that I switched to ext3 during this stuff, as I always had
> to reset the computer and fsck takes so long...
>
> Best regards,
> Elmar
HTH,
-Frans
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
