Kernel traces with Billion Tiny USB TA
Dirk Gouders <[email protected]> Fri, 16 Apr 2010 17:12:02 +0200
| Newsgroups | gmane.linux.isdn |
|---|---|
| Message-ID | <[email protected]> |
Hello, I am coworking on an asterisk channel driver (chan_mISDNv2) which Karsten Keil may have heard about. Although the channel driver still needs a lot of work I am wondering that it is able to cause regular kernel traces: Apr 16 12:14:39 mx10 kernel: ------------[ cut here ]------------ Apr 16 12:14:39 mx10 kernel: WARNING: at kernel/softirq.c:143 local_bh_enable+0x3c/0x87() Apr 16 12:14:39 mx10 kernel: Hardware name: MCP7A Apr 16 12:14:39 mx10 kernel: Modules linked in: coretemp rfcomm l2cap crc16 snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss virtio_net virtio_pci virtio_ring virtio_blk virtio kvm_intel kvm snd_hda_codec_nvhdmi nvidia(P) snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm hfcsusb snd_timer mISDN_core snd snd_page_alloc i2c_nforce2 mcs7830 usbnet Apr 16 12:14:39 mx10 kernel: Pid: 2026, comm: mISDN_HFC-S_USB Tainted: P 2.6.33-gentoo #5 Apr 16 12:14:39 mx10 kernel: Call Trace: Apr 16 12:14:39 mx10 kernel: [<ffffffff81034738>] ? warn_slowpath_common+0x76/0x8c Apr 16 12:14:39 mx10 kernel: [<ffffffff81039c11>] ? local_bh_enable+0x3c/0x87 Apr 16 12:14:39 mx10 kernel: [<ffffffff813c68a6>] ? sk_filter+0x6e/0x7c Apr 16 12:14:39 mx10 kernel: [<ffffffff813b194c>] ? sock_queue_rcv_skb+0x36/0x136 Apr 16 12:14:39 mx10 kernel: [<ffffffffa0038806>] ? mISDN_send+0x5b/0x7f [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003c45b>] ? l2_got_ui+0x0/0x51 [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003b40e>] ? l2up+0x27/0x4d [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003785a>] ? mISDN_FsmEvent+0x8a/0xcc [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003e44c>] ? l2_send+0x638/0x825 [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003ff5b>] ? mgr_bcast+0x82/0x124 [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffffa003a640>] ? mISDNStackd+0x2b2/0x5d6 [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffff8104c69d>] ? autoremove_wake_function+0x0/0x2a Apr 16 12:14:39 mx10 kernel: [<ffffffffa003a38e>] ? mISDNStackd+0x0/0x5d6 [mISDN_core] Apr 16 12:14:39 mx10 kernel: [<ffffffff8104c285>] ? kthread+0x75/0x7d Apr 16 12:14:39 mx10 kernel: [<ffffffff81002c54>] ? kernel_thread_helper+0x4/0x10 Apr 16 12:14:39 mx10 kernel: [<ffffffff8104c210>] ? kthread+0x0/0x7d Apr 16 12:14:39 mx10 kernel: [<ffffffff81002c50>] ? kernel_thread_helper+0x0/0x10 Apr 16 12:14:39 mx10 kernel: ---[ end trace 23270bc2373a8c4d ]--- It seems that the worst case is an incoming ISDN-call that asterisk tries to forward to a SIP address but the remote site hangs up before the call gets connected. It would help me if someone could point me to a direction how I can track down this problem. Thanks, Dirk -- To unsubscribe from this list: send the line "unsubscribe linux-isdn" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html