Kernel errors when accessing sound

BroX · 06-18-2006, 01:25 PM

Hi list,

when I want to access the soundcard, I get all sorts of kernel warnings/errors, and the sound app hangs. Can still ctrl-c out of it. But no sound.

I have no idea what is wrong, as far as I know nothing has changed since it worked well. It started after I installed a bunch of gnome dependencies from Slack-10.1 install disc. Removing the same packages didn't solve it.

Sound modules are loaded, I rebuilt kernel and alsa-lib, but I am clueless how to solve this.

Please, if anyone can point me in the right direction, or tell me what all this means?

Here is the output from syslog:

Code:

Jun 16 20:28:14 sphritzs kernel: Unable to handle kernel NULL pointer dereference at virtual address 000000b9
Jun 16 20:28:14 sphritzs kernel:  printing eip:
Jun 16 20:28:14 sphritzs kernel: e1bbfdf1
Jun 16 20:28:14 sphritzs kernel: *pde = 00000000
Jun 16 20:28:14 sphritzs kernel: Oops: 0002 [#1]
Jun 16 20:28:14 sphritzs kernel: PREEMPT 
Jun 16 20:28:14 sphritzs kernel: Modules linked in: radeon snd_pcm_oss snd_mixer_oss irtty_sir sir_dev irda crc_ccitt i2c_i80
1 snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc yenta_socket rsrc_nonstatic pcmcia_
core intel_agp hw_random cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpiphp container i2c_al
go_pca i2c_algo_pcf i2c_core ibm_acpi nvram
Jun 16 20:28:14 sphritzs kernel: CPU:    0
Jun 16 20:28:14 sphritzs kernel: EIP:    0060:[<e1bbfdf1>]    Not tainted VLI
Jun 16 20:28:14 sphritzs kernel: EFLAGS: 00010246   (2.6.16.19 #2) 
Jun 16 20:28:14 sphritzs kernel: EIP is at snd_intel8x0_pcm_open+0x11/0x6f [snd_intel8x0]
Jun 16 20:28:14 sphritzs kernel: eax: dd2c8c00   ebx: 00000001   ecx: d919fe08   edx: 000000a9
Jun 16 20:28:14 sphritzs kernel: esi: dec61800   edi: 000000a9   ebp: d8a450c0   esp: d919fe00
Jun 16 20:28:14 sphritzs kernel: ds: 007b   es: 007b   ss: 0068
Jun 16 20:28:14 sphritzs kernel: Process audacious (pid: 5637, threadinfo=d919e000 task=dd6b6550)
Jun 16 20:28:14 sphritzs kernel: Stack: <0>dec61800 00000001 d919fe50 e1bbfe68 dd2c8c00 000000a9 00000000 df9c43c0 
Jun 16 20:28:14 sphritzs kernel:        e1ba6f5e dd2c8c00 dd2c8c00 00000001 fffffff2 c17e7a00 d8a450c0 e1ba70ac 
Jun 16 20:28:14 sphritzs kernel:        d8a450c0 c17e7a00 00000000 d919fe50 00000000 00000000 dd6b6550 c0115b4d 
Jun 16 20:28:14 sphritzs kernel: Call Trace:
Jun 16 20:28:14 sphritzs kernel:  [<e1bbfe68>] snd_intel8x0_playback_open+0x19/0xa7 [snd_intel8x0]
Jun 16 20:28:14 sphritzs kernel:  [<e1ba6f5e>] snd_pcm_open_file+0x8e/0xc5 [snd_pcm]
Jun 16 20:28:14 sphritzs kernel:  [<e1ba70ac>] snd_pcm_open+0xcf/0x18d [snd_pcm]
Jun 16 20:28:14 sphritzs kernel:  [<c0115b4d>] default_wake_function+0x0/0x12
Jun 16 20:28:14 sphritzs kernel:  [<c022fa8b>] kobject_get+0x12/0x17
Jun 16 20:28:14 sphritzs kernel:  [<e1ba6fb5>] snd_pcm_playback_open+0x20/0x24 [snd_pcm]
Jun 16 20:28:14 sphritzs kernel:  [<e1b831b2>] snd_open+0xdb/0x1b2 [snd]
Jun 16 20:28:14 sphritzs kernel:  [<c015ad3d>] chrdev_open+0x163/0x187
Jun 16 20:28:14 sphritzs kernel:  [<c015abda>] chrdev_open+0x0/0x187
Jun 16 20:28:14 sphritzs kernel:  [<c0152a9c>] __dentry_open+0xe1/0x1c9
Jun 16 20:28:14 sphritzs kernel:  [<c0152c5a>] nameidata_to_filp+0x1f/0x31
Jun 16 20:28:14 sphritzs kernel:  [<c0152bb8>] do_filp_open+0x34/0x3c
Jun 16 20:28:14 sphritzs kernel:  [<c0152d02>] get_unused_fd+0x4f/0xb1
Jun 16 20:28:14 sphritzs kernel:  [<c0152e32>] do_sys_open+0x40/0xb6
Jun 16 20:28:14 sphritzs kernel:  [<c0152ebb>] sys_open+0x13/0x17
Jun 16 20:28:14 sphritzs kernel:  [<c0102b09>] syscall_call+0x7/0xb
Jun 16 20:28:14 sphritzs kernel: Code: 5c 8d 14 dd 00 00 00 00 89 d0 31 d2 f7 71 48 89 c1 89 c8 59 5b 5b 5e 5f 5d c3 57 56 53
 8b 44 24 10 8b 7c 24 14 8b 70 5c 8b 58 08 <89> 47 10 8d 86 d0 00 00 00 6a 38 68 80 47 bc e1 50 e8 39 2f 67 
/var/log/syslog lines 2495-2535/2535 (END)

Cheers, Leon.

theoffset · 06-18-2006, 10:58 PM

This is a kernel Oops dump. It could be because of a misconfiguration, a hardware issue or a bug in the kernel (actually in the alsa-drivers).

I don't know how to solve this, but if you were using the Alsa drivers which come with the Kernel, you could try downloading and compiling the ones from Alsa-project (the most recent, stable release is 1.0.11, while the 2.6.16.x kernel has 1.0.11rc2, so chances are that if it's a known bug it's been solved in the lastest stable release). It probably won't fix it, but is worth the try.

If that doesn't help, maybe you should put a bug report to the ALSA developer...

BroX · 06-19-2006, 04:33 AM

Thanks!

I am running alsa-drivers 1.0.11 and 2.6.16.20 kernel. Strange thing is that when I recompiled the latest 2.6.17 kernel, it doesn't happen.

Cheers, Leon.