From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001520]: Soundchip was not detected
Date: Mon, 6 Feb 2006 09:34:47 +0100 [thread overview]
Message-ID: <7cdf1bc7d542924e6aa4c691b7a37af8@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1520>
======================================================================
Reported By: Henne
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1520
Category: ISA - cs4236
Reproducibility: always
Severity: feature
Priority: normal
Status: new
Distribution: Slackware 9.0
Kernel Version: 2.6.14-rc4
======================================================================
Date Submitted: 11-01-2005 10:35 CET
Last Modified: 02-06-2006 09:34 CET
======================================================================
Summary: Soundchip was not detected
Description:
I have an HP Omnibook 5700 CTX with some CS423x chip onboard, which is not
detected by alsaconf. I did not find the ids in cs4236.c so I think the
Pnp ID's
must added to this file.
======================================================================
----------------------------------------------------------------------
Henne - 11-15-05 10:10
----------------------------------------------------------------------
I didn't give you the whole information.
1.
I compiled alsa-driver-1.10.rc3 again -with-debug=full , to see if this
brings more info to the screen.
dmesg tells now after:
ALSA (path to cs423x) cs4236.c:179: CS4232 WSS PnP manual resources are
invalid, using auto config
a new message:
ALSA (path to cs423x) cs4231_lib.c:386: cs4231_mce_down - auto calibration
time out (1)
The noise from the speaker sounds like a farth (I think that hint is very
usefull!!!)
2.
Whne I try to unload the module (modprobe -r snd-cs4232) the kernel says:
Unable to handle kernel NULL pointer dereference at virtual address
00000184 printing eip:
c2865ab9
*pde = 00000000
Ooops: 0000 [#1]
PREEMPT
Modules linked in: snd_cs4232 snd_opl3_lib snd_hwdep snd_cs4231_lib
snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi
snd_seq_device snd soundcore pcmcia firmware_class yenta_socket
rerc_nonstatic pcmcia_core rtc
CPU: 0
EIP: 0060:[<c2865ab9>] Not tainted VLI
EFLAGS: 00010202 (2.6.14-kj1)
EIP is at snd_card_disconntect+0x19/0x250 [snd]
eax: 00000000 ebx: c1836000 ecx: 00000001 edx: c10ad438
esi: c10ad400 edi: c283aa14 ebp: c283aa5c esp: c1837ed4
ds: 00fb es: 007b ss: 0068
rocess modprobe (pid: 1147, threadinfo=c1836000 task=c1c9aa50)
Stack: c10ad438 c1836000 c10ad42c c02cc8f2 00000000 c10ad400 c283aa14
c283aa5c
c2838821 00000000 c10ad400 c01d0f43 c10ad400 c10ad468 c01fa823
c10ad400
c10ad400 c1836000 c283aa14 c01fa8cb c10ad400 c283aa14 c28388b0
00000000
Call Trace:
[<c02cc8f2>] klist_dec_and_del+0x12/0x20
[<c2838821>] snd_cs4232_pnpbios_remove+0x11/0x20 [snd_cs4232]
[<c01d0f43>] pnp_device_remove+0x33/0x40
[<c01fa823>] __device_release_driver+0x63/0x70
[<c01fa8cb>] driver_detach+0x6b/0x93
[<c28388b0>] alsa_card_cs423x_exit+0x0/0x36 [snd_cs4232]
[<c01fa2b2>] bus_remove_driver+0x42/0x70
[<c01fab9b>] driver_unregister+0xb/0x20
[<c28388c7>] alsa_card_cs423x_exit+0x17/0x36 [snd_cs4232]
[<c012cd10>] sys_delete_module+0x150/0x190
[<c0148131>] do_munmap+0xd1/0x100
[<c0102b69>] syscall_call+0x7/0xb
Code: 26 00 b8 28 00 00 00 c3 8d 76 00 8d bc 27 00 00 00 00 55 57 56 53 bb
00 e0 ff ff 83 ec 10 21 e3 8b 4b 14 41 89 4b 14 8b 44 24 24 <8b> 90 84 01
00 00 85 d2 74 20 8b 43 14 48 89 43 14 8b 43 08 83
<6>note: modprobe[1147] exited with preempt_count 1
----------------------------------------------------------------------
Henne - 02-06-06 09:34
----------------------------------------------------------------------
Here I'am again!
I'm now using kernel 2.6.16-rc2 and nothing changed, but I found out, that
the oss driver works well, so I try to look what he's doing, look what the
alsa-driver isn't doing and then make the alsa driver doing this.
Issue History
Date Modified Username Field Change
======================================================================
11-01-05 10:35 Henne New Issue
11-01-05 10:35 Henne Distribution => Slackware 9.0
11-01-05 10:35 Henne Kernel Version => 2.6.14-rc4
11-08-05 18:48 tiwai Note Added: 0006637
11-08-05 21:00 Henne Note Added: 0006643
11-12-05 19:33 Henne Note Added: 0006688
11-15-05 10:10 Henne Note Added: 0006729
02-06-06 09:34 Henne Note Added: 0007944
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-02-06 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 8:34 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 13:59 [ALSA - driver 0001520]: Soundchip was not detected bugtrack
2006-04-23 22:27 bugtrack
2006-03-17 17:42 bugtrack
2006-03-17 11:14 bugtrack
2006-03-16 12:57 bugtrack
2005-11-15 9:10 bugtrack
2005-11-12 18:33 bugtrack
2005-11-08 20:00 bugtrack
2005-11-08 17:48 bugtrack
2005-11-01 9:35 bugtrack
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=7cdf1bc7d542924e6aa4c691b7a37af8@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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