It appears so, yes. It also occurs on incoming calls. Here are the two
core dumps.
Incoming:
Oops: 0000 [#1] PREEMPT
Modules linked in: binfmt_misc aes_i586 aes_generic xt_tcpudp
iptable_nat nf_nat xt_TCPMSS ipt_LOG ipt_REJECT iptable_mangle
iptable_filter xt_multiport xt_state xt_limit xt_conntrack
nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack ip_tables x_tables
pc87360 hwmon_vid hwmon dummy dahdi_vpmadt032_loader(P) wctdm24xxp
dahdi_voicebus dahdi sha512_generic sha256_generic deflate
zlib_deflate arc4 ecb sha1_generic blowfish des_generic cbc cryptosoft
cryptodev(P) ocf(P) geodewdt geode_rng geode_aes crypto_blkcipher
via_rhine rtc cs5535_gpio
Pid: 0, comm: swapper Tainted: P (2.6.27.29-astlinux #1)
EIP: 0060:[<00000000>] EFLAGS: 00010046 CPU: 0
EIP is at 0x0
EAX: df263760 EBX: 00000000 ECX: 00000000 EDX: 00000000
ESI: de600000 EDI: 00000001 EBP: de600094 ESP: c035def4
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Process swapper (pid: 0, ti=c035c000 task=c033a2e0 task.ti=c035c000)
Stack: e0880871 00000069 de600088 00000004 00000282 de60d718 de60d700 0000001c
e08bf739 e08bb5ef de601b80 00000293 0000000a 00000000 df240e00 00000000
dee66000 e08bbe6b df98d800 de601b80 00000008 de601800 df240e00 00000000
Call Trace:
[<e0880871>] __dahdi_ec_chunk+0x114/0x305 [dahdi]
[<e08bf739>] handle_transmit+0x600/0x1235 [wctdm24xxp]
[<e08bb5ef>] cmd_decipher+0xf1/0x109 [wctdm24xxp]
[<e08bbe6b>] handle_receive+0x2ae/0x2de [wctdm24xxp]
[<e0871819>] vb_deferred+0x13c/0x159 [dahdi_voicebus]
[<e0871e85>] vb_isr+0x30/0x118 [dahdi_voicebus]
[<c0134ca6>] handle_IRQ_event+0x1a/0x3f
[<c0135bbe>] handle_level_irq+0x6d/0xcd
[<c01049bf>] do_IRQ+0x48/0x5d
[<c01039cb>] common_interrupt+0x23/0x28
[<c01076e8>] default_idle+0x28/0x3b
[<c0102821>] cpu_idle+0x37/0x67
=======================
Code: Bad EIP value.
EIP: [<00000000>] 0x0 SS:ESP 0068:c035def4
Kernel panic - not syncing: Fatal exception in interrupt
Outgoing:
Oops: 0000 [#1] PREEMPT
Modules linked in: binfmt_misc aes_i586 aes_generic xt_tcpudp
iptable_nat nf_nat xt_TCPMSS ipt_LOG ipt_REJECT iptable_mangle
iptable_filter xt_multiport xt_state xt_limit xt_conntrack
nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack ip_tables x_tables
pc87360 hwmon_vid hwmon dummy dahdi_vpmadt032_loader(P) wctdm24xxp
dahdi_voicebus dahdi sha512_generic sha256_generic deflate
zlib_deflate arc4 ecb sha1_generic blowfish des_generic cbc cryptosoft
cryptodev(P) ocf(P) geodewdt geode_rng geode_aes crypto_blkcipher
via_rhine rtc cs5535_gpio
Pid: 0, comm: swapper Tainted: P (2.6.27.29-astlinux #1)
EIP: 0060:[<00000000>] EFLAGS: 00010046 CPU: 0
EIP is at 0x0
EAX: df265760 EBX: 00000000 ECX: 00000008 EDX: 00000000
ESI: de602000 EDI: 00000001 EBP: de602094 ESP: c035def4
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Process swapper (pid: 0, ti=c035c000 task=c033a2e0 task.ti=c035c000)
Stack: e0880871 00000069 de602088 00080004 00000282 df26bf18 df26bf00 0000001c
fd901d00 e08bb5ef de603380 00000293 0000000a 00000000 df22ee00 00000000
dfada000 e08bbe6b df98f800 de603380 00000008 de603000 df22ee00 00000000
Call Trace:
[<e0880871>] __dahdi_ec_chunk+0x114/0x305 [dahdi]
[<e08bb5ef>] cmd_decipher+0xf1/0x109 [wctdm24xxp]
[<e08bbe6b>] handle_receive+0x2ae/0x2de [wctdm24xxp]
[<e0871819>] vb_deferred+0x13c/0x159 [dahdi_voicebus]
[<e0871e85>] vb_isr+0x30/0x118 [dahdi_voicebus]
[<c0134ca6>] handle_IRQ_event+0x1a/0x3f
[<c0135bbe>] handle_level_irq+0x6d/0xcd
[<c01049bf>] do_IRQ+0x48/0x5d
[<c01039cb>] common_interrupt+0x23/0x28
[<c01076e8>] default_idle+0x28/0x3b
[<c0102821>] cpu_idle+0x37/0x67
=======================
Code: Bad EIP value.
EIP: [<00000000>] 0x0 SS:ESP 0068:c035def4
Kernel panic - not syncing: Fatal exception in interrupt
To give a few other details, this is a box upgraded from 0.6.8, and
contains a TDM410P, 1 FXO, and the VPMADT032 (or whatever catchy name
it has) echo canceller.
Any thoughts gratefully received.
Thanks
Tom
On Tue, Dec 8, 2009 at 11:39 AM, Darrick Hartman (lists)
<dhart...@djhsolutions.com> wrote:
> On 12/08/2009 05:08 AM, Tom Chadwin wrote:
>> Hello all
>>
>> Trying to get a TDM410P up and running in 0.7-3417. An outgoing call
>> seems to cause a kernel panic:
>>
>> Code: Bad EIP value.
>> EIP: [<00000000>] 0x0 SS:ESP 0068:c035def4
>> Kernel panic - not syncing: Fatal exception in interrupt
>>
>> Can anyone help? As you might gather, I have precisely no experience
>> in debugging anything like this.
>>
>> Thanks
>>
>> Tom
>
> Tom,
>
> I have not run into the same problem. Are you able to reproduce this
> 100% of the time?
>
> Darrick
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> Astlinux-users mailing list
> Astlinux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pay...@krisk.org.
>
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
