Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: snd-es1968 (+ snd-cs4236) trouble
Date: Sat, 10 Dec 2005 21:13:20 +0100	[thread overview]
Message-ID: <439B36E0.3090709@keyaccess.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

Hi Takashi.

I have two soundcards in my machine; a snd-cs46xx card and a snd-cs4236 
card, which has always worked nicely. Today though I tried swapping the 
snd-cs46xx one for a snd-es1968 one, and this does not work.

The second I modprobe snd-es1968, snd-cs4236 stops working. If I'm 
listening to snd-cs4236 at the time I get the last second or so repeated 
over and over again. Killing the app that was playing via kill -9 works 
and stops the repeating sound but does not repair things: when I try to 
use snd-cs4236 again after that, it's still the same -- I only get the 
first second or so repeated over and over.

ALSA code is kernel 2.6.14.3 (1.0.10rc1). I just now tried checking 
standalone ALSA 1.0.10, but unfortunately its snd-cs4236 won't load at 
all. The machine oopses on "modprobe snd-cs4236" with the attached 
backtrace.

That last one seems a problem in snd-cs4236, but the earlier problem is 
likely in snd-es1968 -- as said, snd-cs4236 + snd-cs46xx work fine 
together. Moreover, I could swear earlier snd-cs46xx crashed in the same 
way as snd-cs4236 does when inserting snd-es1968, although I can't seem 
to reproduce this right now.

Thanks in advance for any probing...

Rene.




[-- Attachment #2: cs4236-1.0.10.oops --]
[-- Type: text/plain, Size: 2423 bytes --]

pnp: the driver 'cs423x' has been registered
pnp: match found with the PnP device '01:01.00' and the driver 'cs423x'
pnp: match found with the PnP device '01:01.02' and the driver 'cs423x'
pnp: match found with the PnP device '01:01.03' and the driver 'cs423x'
pnp: Device 01:01.00 activated.
pnp: Device 01:01.02 activated.
pnp: Device 01:01.03 activated.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
00000000
*pde = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: snd_cs4236 snd_opl3_lib snd_hwdep snd_cs4236_lib snd_mpu401_uart snd_rawmidi snd_seq_device snd_cs4231_lib snd_pcm snd_timer snd soundcore snd_page_alloc nfsd exportfs lockd sunrpc nls_iso8859_1 nls_cp437 vfat fat nls_base
CPU:    0
EIP:    0060:[<00000000>]    Not tainted VLI
EFLAGS: 00010286   (2.6.14.3-local-wc) 
EIP is at 0x0
eax: ef2daa14   ebx: ef2daa1c   ecx: 00000008   edx: f094a494
esi: 00000000   edi: f094a494   ebp: c01b30e8   esp: ee8c2e3c
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1516, threadinfo=ee8c2000 task=ef113a90)
Stack: f093f00c c01b3097 ee8c2e54 00000000 ef2daa1c c01b2a75 c0299458 c0299458 
       f094a4ec c016d676 ef2daa1c ef2daa1c c0299360 00000000 c01b3127 c01b30e8 
       ef2daa84 c01b2b77 ef2daa84 ef2daa1c ef2daac6 00000000 c01b2022 c0299240 
Call Trace:
 [<f093f00c>] snd_platform_driver_probe+0xc/0xd [snd]
 [<c01b3097>] driver_probe_device+0x31/0x82
 [<c01b2a75>] bus_for_each_drv+0x35/0x59
 [<c016d676>] create_files+0x27/0x51
 [<c01b3127>] device_attach+0x3a/0x4d
 [<c01b30e8>] __device_attach+0x0/0x5
 [<c01b2b77>] bus_add_device+0x20/0x6f
 [<c01b2022>] device_add+0x97/0xf8
 [<c01b41d9>] platform_device_register+0xb5/0x103
 [<f08f7995>] snd_cs4231_pm_suspend+0x0/0x15 [snd_cs4231_lib]
 [<f09404b2>] snd_generic_device_register+0x64/0x81 [snd]
 [<f08f79aa>] snd_cs4231_pm_resume+0x0/0x15 [snd_cs4231_lib]
 [<f0940682>] snd_card_set_generic_pm_callback+0x13/0x2f [snd]
 [<f08f7e63>] snd_cs4231_create+0x28a/0x29e [snd_cs4231_lib]
 [<f09593a2>] snd_cs4236_create+0x70/0x2b1 [snd_cs4236_lib]
 [<f09784e6>] snd_card_cs423x_probe+0x14c/0x30c [snd_cs4236]
 [<f09786d0>] snd_cs423x_pnp_detect+0x2a/0x4c [snd_cs4236]
 [<c0192e39>] card_probe+0x3b/0x85
 [<c01933f0>] pnp_register_card_driver+0x7a/0x86
 [<f08e103d>] alsa_card_cs423x_init+0x3d/0x62 [snd_cs4236]
 [<c0126e59>] sys_init_module+0xae/0x1a5
 [<c01024d1>] syscall_call+0x7/0xb
Code:  Bad EIP value.

             reply	other threads:[~2005-12-10 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10 20:13 Rene Herman [this message]
2005-12-11  9:08 ` snd-es1968 (+ snd-cs4236) trouble Sergey Vlasov
2005-12-11 15:16   ` Rene Herman
2005-12-12 11:58 ` Takashi Iwai
2005-12-12 22:53   ` Rene Herman
2005-12-13  7:09     ` Rene Herman
2005-12-13 11:04       ` Takashi Iwai
2005-12-13 20:24         ` Rene Herman
2005-12-14  4:55           ` Rene Herman
2005-12-14 12:00             ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=439B36E0.3090709@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox