Skip to contentSkip to conversation

0.9.7c, cs4236b and kernel oops

DISCUSSION Dennis Veatch 2 participants 8 messages Oct 15, 2003 – Oct 16, 2003

lore
Share & tools
lore
#0 lore raw

This is a Dell GX1 with a cs4236b integrated sound card. Running kernel version 2.4.20. I have tried recompiling the kernel any number of ways making the sound stuff modules and part of the kernel all with the same results. I have wiped out /lib/modules and /usr/src/linux entirely, re-downloaded all the kernel stuff and still had the same results. If I use the 0.9.6 version of alsa-driver there are no problems.

During boot up it does show the cs4236b being detected correctly. I can install Mandrake 9.1 on this box and there is not kernel oops.

If I comment out the alsa line in /etc/modules.conf the system will boot. Then if I modprobe soundcore, things are still fine. If I try modprobing the snd-cs4236, boom, kernel oops.

Up until alsa-driver version 0.9.6 the sound card worked fine. No problems. So I am reasonable sure this has nothing to do with the kernel.

Since versions 0.9.7a, b and c any attempt to load the cs4236 stuff causes a kernel oops. Below is some of the oops.

I have looked over the alsa web site and googled on this issue only to find some what dated information that leads me to believe this was an issue at one time but was supposed to have been corrected by now.
_______________________________________________________
Staring sound driver: snd-cs4236 Unable to handle kernel NULL point dereference at virtual address 00000060
printing eip:
f887752b
*pde = 00000000

Oops: 0000

.
.
.
.
.
.

and ends with;

<0>Kernel panis: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Signature · 14 lines
Registered Linux user 193414
http://counter.li.org

"Trying"? My contribution was much closer to a "feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work."



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
#1 lore raw

At Tue, 14 Oct 2003 21:24:56 -0400,

Quoted 7 lines · Dennis Veatch

This is a Dell GX1 with a cs4236b integrated sound card. Running kernel version 2.4.20. I have tried recompiling the kernel any number of ways making the sound stuff modules and part of the kernel all with the same results. I have wiped out /lib/modules and /usr/src/linux entirely, re-downloaded all the kernel stuff and still had the same results. If I use the 0.9.6 version of alsa-driver there are no problems.

is it a pnp device or non-pnp?

there are no big changes in the cs423x codes.
so the problem must be in either pnp layer or the change in the core part.

if it's pnp card, please try to replace snd-pnp.o with the old one in 0.9.6.

Takashi

Quoted 31 lines

During boot up it does show the cs4236b being detected correctly. I can install Mandrake 9.1 on this box and there is not kernel oops.

If I comment out the alsa line in /etc/modules.conf the system will boot. Then if I modprobe soundcore, things are still fine. If I try modprobing the snd-cs4236, boom, kernel oops.

Up until alsa-driver version 0.9.6 the sound card worked fine. No problems. So I am reasonable sure this has nothing to do with the kernel.

Since versions 0.9.7a, b and c any attempt to load the cs4236 stuff causes a kernel oops. Below is some of the oops.

I have looked over the alsa web site and googled on this issue only to find some what dated information that leads me to believe this was an issue at one time but was supposed to have been corrected by now.
_______________________________________________________
Staring sound driver: snd-cs4236 Unable to handle kernel NULL point dereference at virtual address 00000060
printing eip:
f887752b
*pde = 00000000

Oops: 0000

.
.
.
.
.
.

Quoted 24 lines

and ends with;

<0>Kernel panis: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Signature · 18 lines
Registered Linux user 193414
http://counter.li.org

"Trying"? My contribution was much closer to a "feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work."



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

#2 lore raw
Quoted 10 lines · Takashi Iwai

At Tue, 14 Oct 2003 21:24:56 -0400,

Quoted 6 lines · Dennis Veatch

This is a Dell GX1 with a cs4236b integrated sound card. Running kernel version 2.4.20. I have tried recompiling the kernel any number of ways making the sound stuff modules and part of the kernel all with the same results. I have wiped out /lib/modules and /usr/src/linux entirely, re-downloaded all the kernel stuff and still had the same results. If I use the 0.9.6 version of alsa-driver there are no problems.

Quoted 10 lines

is it a pnp device or non-pnp?

there are no big changes in the cs423x codes.
so the problem must be in either pnp layer or the change in the core part.

if it's pnp card, please try to replace snd-pnp.o with the old one in 0.9.6.

Actually I am not sure if its pnp or not. During boot it says "isapnp: Card 'CS4236B' so I assume its pnp?

There is definitely something different in snd-pnp.o between version 0.9.6 and 0.9.7 on up. Tried your suggestion of copying snd-pnp.o (version 0.9.60) over the same of version 0.9.7c and there was no Oops.

One thing I forgot to mention about 0.9.6. As said it boots fine and all. During the install of snd-cs4236 there is a non-fatal error that says;

Starting sound driver: snd-cs4236 CS4236+ WSS PnP configure failed for WSS (out of resources?)
isapnp detection failed and probing for CS4236+ is not supported.

Signature · 14 lines
Registered Linux user 193414
http://counter.li.org

"Trying"? My contribution was much closer to a "feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work."



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
#3 lore raw

At Wed, 15 Oct 2003 09:20:53 -0400,

Quoted 18 lines · Dennis Veatch
Quoted 16 lines · Takashi Iwai

At Tue, 14 Oct 2003 21:24:56 -0400,

Quoted 6 lines · Dennis Veatch

This is a Dell GX1 with a cs4236b integrated sound card. Running kernel version 2.4.20. I have tried recompiling the kernel any number of ways making the sound stuff modules and part of the kernel all with the same results. I have wiped out /lib/modules and /usr/src/linux entirely, re-downloaded all the kernel stuff and still had the same results. If I use the 0.9.6 version of alsa-driver there are no problems.

is it a pnp device or non-pnp?

there are no big changes in the cs423x codes.
so the problem must be in either pnp layer or the change in the core part.

Quoted 7 lines
Quoted 4 lines

if it's pnp card, please try to replace snd-pnp.o with the old one in 0.9.6.

Actually I am not sure if its pnp or not. During boot it says "isapnp: Card 'CS4236B' so I assume its pnp?

yes.

Quoted 3 lines

There is definitely something different in snd-pnp.o between version 0.9.6 and 0.9.7 on up. Tried your suggestion of copying snd-pnp.o (version 0.9.60) over the same of version 0.9.7c and there was no Oops.

ok, it looks like the pnp layer is the cause.
i'll take a look.

Takashi

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

#4 lore raw

At Wed, 15 Oct 2003 16:21:57 +0200,

Quoted 29 lines · 私 wrote:

At Wed, 15 Oct 2003 09:20:53 -0400,

Quoted 18 lines · Dennis Veatch
Quoted 16 lines · Takashi Iwai

At Tue, 14 Oct 2003 21:24:56 -0400,

Quoted 6 lines · Dennis Veatch

This is a Dell GX1 with a cs4236b integrated sound card. Running kernel version 2.4.20. I have tried recompiling the kernel any number of ways making the sound stuff modules and part of the kernel all with the same results. I have wiped out /lib/modules and /usr/src/linux entirely, re-downloaded all the kernel stuff and still had the same results. If I use the 0.9.6 version of alsa-driver there are no problems.

is it a pnp device or non-pnp?

there are no big changes in the cs423x codes.
so the problem must be in either pnp layer or the change in the core part.

Quoted 7 lines
Quoted 4 lines

if it's pnp card, please try to replace snd-pnp.o with the old one in 0.9.6.

Actually I am not sure if its pnp or not. During boot it says "isapnp: Card 'CS4236B' so I assume its pnp?

Quoted 8 lines

yes.

Quoted 3 lines

There is definitely something different in snd-pnp.o between version 0.9.6 and 0.9.7 on up. Tried your suggestion of copying snd-pnp.o (version 0.9.60) over the same of version 0.9.7c and there was no Oops.

ok, it looks like the pnp layer is the cause.
i'll take a look.

could you try the attached patch?

Takashi

#5 lore raw

At Thu, 16 Oct 2003 13:22:37 +0200,

Quoted 2 lines · I wrote:

could you try the attached patch?

found one more potential bug. use this one instead.

Takashi

author
#6 lore raw
Quoted 9 lines · Takashi Iwai

At Thu, 16 Oct 2003 13:22:37 +0200,

Quoted 1 line · I wrote:

could you try the attached patch?

found one more potential bug. use this one instead.

Takashi

Glad I waited. Is it, move to /usr/src/alsa-driver-0.9.7c/support/pnp and "patch -p1 < file"? Another dumb question, how do I get patch not to ask about skipping it and do it anyway? The reason is I have a script that automates the build.

Signature · 14 lines
Registered Linux user 193414
http://counter.li.org

"Trying"? My contribution was much closer to a "feeble wave in the general 
direction of something that might lead you one step closer to a solution 
if you squint really hard and do all of the work."



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
#7 lore raw

At Thu, 16 Oct 2003 08:46:38 -0400,

Quoted 7 lines · Stumbles
Quoted 5 lines · Takashi Iwai

At Thu, 16 Oct 2003 13:22:37 +0200,

Quoted 1 line · I wrote:

could you try the attached patch?

Quoted 7 lines
Quoted 4 lines

found one more potential bug. use this one instead.

Takashi

Glad I waited. Is it, move to /usr/src/alsa-driver-0.9.7c/support/pnp and "patch -p1 < file"?

/usr/src/alsa-driver-0.9.7c, if you use -p1.

Quoted 3 lines

Another dumb question, how do I get patch not to ask
about skipping it and do it anyway? The reason is I have a script that automates the build.

patch asks to skip if the corresponding file is not found. that is, something is wrong, e.g. the wrong path.

Takashi

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php