|
|
|
|
|
|
|
|
|
|
xen-bugs
[Xen-bugs] [Bug 87] New: zaptel driver generates kernel dump in Xen0
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=87
Summary: zaptel driver generates kernel dump in Xen0
Product: Xen
Version: unstable
Platform: x86
OS/Version: Linux-2.6
Status: NEW
Severity: major
Priority: P2
Component: Unspecified
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: deon@xxxxxxxxxx
I'm running the stock standard FC4 as released just recently.
I use the zaptel drivers to run my Digium TDM400 card. Under a Xen0 kernel, it
generates a dump(?) - a dump trace goes to syslog anyway.
Digium looked at the kernel dump and believe its a xen issue.
I downloaded their latest CVS code and compiled it under the default FC4 kernel,
and it loads fine:
[root@router zaptel]# insmod ./wctdm.ko opermode=AUSTRALIA fxshonormode=1
boostringer=1
Jun 30 07:44:45 router kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 11
Jun 30 07:44:45 router kernel: ACPI: PCI Interrupt 0000:01:01.0[A] -> Link
[LNKF] -> GSI 11 (level, low) -> IRQ 11
[root@router zaptel]# Jun 30 07:44:48 router kernel: Freshmaker version: 73
Jun 30 07:44:48 router kernel: Freshmaker passed register test
Jun 30 07:44:48 router kernel: Boosting ringinger on slot 1 (89V peak)
Jun 30 07:44:48 router kernel: Module 0: Installed -- AUTO FXS/DPO
Jun 30 07:44:48 router kernel: Boosting ringinger on slot 2 (89V peak)
Jun 30 07:44:48 router kernel: Module 1: Installed -- AUTO FXS/DPO
Jun 30 07:44:48 router kernel: Module 2: Installed -- AUTO FXO (AUSTRALIA mode)
Jun 30 07:44:48 router kernel: Module 3: Installed -- AUTO FXO (AUSTRALIA mode)
Jun 30 07:44:48 router kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4
modules)
When I recompile the drivers under a Dom0 kernel and load it, I get the
following dump:
Jun 29 23:30:02 router kernel: Zapata Telephony Interface Registered on
major 196
Jun 29 23:30:02 router kernel: PCI: Obtained IRQ 21 for device 0000:01:01.0
Jun 29 23:30:15 router kernel: Freshmaker version: 73
Jun 29 23:30:15 router kernel: Freshmaker passed register test
Jun 29 23:30:15 router kernel: Boosting ringinger on slot 1 (89V peak)
Jun 29 23:30:15 router kernel: Module 0: Installed -- AUTO FXS/DPO
Jun 29 23:30:15 router kernel: Boosting ringinger on slot 2 (89V peak)
Jun 29 23:30:15 router kernel: Module 1: Installed -- AUTO FXS/DPO
Jun 29 23:30:15 router kernel: BUG: soft lockup detected on CPU#0!
Jun 29 23:30:15 router kernel:
Jun 29 23:30:15 router kernel: Pid: 2547, comm: modprobe
Jun 29 23:30:15 router kernel: EIP: 0061:[<d8c6c515>] CPU: 0
Jun 29 23:30:15 router kernel: EIP is at wctdm_init_voicedaa+0x223/0x760
[wctdm]
Jun 29 23:30:15 router kernel: EFLAGS: 00000287 Not tainted
(2.6.11-1.1369_FC4xen0)
Jun 29 23:30:15 router kernel: EAX: ffffabec EBX: 00000000 ECX: fbffc000
EDX: ffffac20
Jun 29 23:30:15 router kernel: ESI: 00000014 EDI: 00000000 EBP: d1abc168
DS: 007b ES: 007b
Jun 29 23:30:15 router kernel: [<d8c6e5d1>]
wctdm_hardware_init+0x336/0x44a [wctdm]
Jun 29 23:30:15 router kernel: [<d8c6e912>] wctdm_init_one+0x205/0x4c3
[wctdm]
Jun 29 23:30:15 router kernel: [<d8c6a892>] wctdm_interrupt+0x0/0xc0f
[wctdm]
Jun 29 23:30:15 router kernel: [<c0201e25>]
pci_device_probe_static+0x45/0x50
Jun 29 23:30:15 router kernel: [<c0201e6b>] __pci_device_probe+0x3b/0x60
Jun 29 23:30:15 router kernel: [<c0201ebc>] pci_device_probe+0x2c/0x50
Jun 29 23:30:15 router kernel: [<c02441ef>] driver_probe_device+0x2f/0x80
Jun 29 23:30:15 router kernel: [<c0244369>] driver_attach+0x59/0x90
Jun 29 23:30:15 router kernel: [<c02448ff>] bus_add_driver+0xaf/0x100
Jun 29 23:30:15 router kernel: [<c0201fe0>] pci_device_shutdown+0x0/0x30
Jun 29 23:30:15 router kernel: [<c020214e>] pci_register_driver+0x7e/0xa0
Jun 29 23:30:15 router kernel: [<d89ea065>] wctdm_init+0x65/0xbc [wctdm]
Jun 29 23:30:16 router kernel: [<c013fb3e>] sys_init_module+0xfe/0x250
Jun 29 23:30:16 router kernel: [<c0109473>] syscall_call+0x7/0xb
Jun 29 23:30:16 router kernel: [<c014851a>] softlockup_tick+0x8a/0xb0
Jun 29 23:30:16 router kernel: [<c010be10>] timer_interrupt+0xe0/0x610
Jun 29 23:30:16 router kernel: [<d8c6c50e>]
wctdm_init_voicedaa+0x21c/0x760 [wctdm]
Jun 29 23:30:16 router kernel: [<c0129bed>] __mod_timer+0x12d/0x150
Jun 29 23:30:16 router kernel: [<c0129bed>] __mod_timer+0x12d/0x150
Jun 29 23:30:16 router kernel: [<c0133aab>]
__rcu_process_callbacks+0x8b/0x130
Jun 29 23:30:16 router kernel: [<c014877d>] handle_IRQ_event+0x3d/0xb0
Jun 29 23:30:16 router kernel: [<c01488da>] __do_IRQ+0xea/0x170
Jun 29 23:30:16 router kernel: [<c010dafd>] do_IRQ+0x1d/0x30
Jun 29 23:30:16 router kernel: [<c0106372>] evtchn_do_upcall+0x72/0xa0
Jun 29 23:30:16 router kernel: [<c010969d>] hypervisor_callback+0x31/0x3c
Jun 29 23:30:16 router kernel: [<d8c6c515>]
wctdm_init_voicedaa+0x223/0x760 [wctdm]
Jun 29 23:30:16 router kernel: [<d8c6e5d1>]
wctdm_hardware_init+0x336/0x44a [wctdm]
Jun 29 23:30:16 router kernel: [<d8c6e912>] wctdm_init_one+0x205/0x4c3
[wctdm]
Jun 29 23:30:16 router kernel: [<d8c6a892>] wctdm_interrupt+0x0/0xc0f
[wctdm]
Jun 29 23:30:16 router kernel: [<c0201e25>]
pci_device_probe_static+0x45/0x50
Jun 29 23:30:16 router kernel: [<c0201e6b>] __pci_device_probe+0x3b/0x60
Jun 29 23:30:16 router kernel: [<c0201ebc>] pci_device_probe+0x2c/0x50
Jun 29 23:30:16 router kernel: [<c02441ef>] driver_probe_device+0x2f/0x80
Jun 29 23:30:16 router kernel: [<c0244369>] driver_attach+0x59/0x90
Jun 29 23:30:16 router kernel: [<c02448ff>] bus_add_driver+0xaf/0x100
Jun 29 23:30:16 router kernel: [<c0201fe0>] pci_device_shutdown+0x0/0x30
Jun 29 23:30:16 router kernel: [<c020214e>] pci_register_driver+0x7e/0xa0
Jun 29 23:30:16 router kernel: [<d89ea065>] wctdm_init+0x65/0xbc [wctdm]
Jun 29 23:30:16 router kernel: [<c013fb3e>] sys_init_module+0xfe/0x250
Jun 29 23:30:16 router kernel: [<c0109473>] syscall_call+0x7/0xb
Jun 29 23:30:16 router kernel: Module 2: Installed -- AUTO FXO
(AUSTRALIA mode)
Jun 29 23:30:16 router kernel: Module 3: Installed -- AUTO FXO
(AUSTRALIA mode)
Jun 29 23:30:16 router kernel: Found a Wildcard TDM: Wildcard TDM400P
REV I (4 modules)
Is this bad?
Im happy to give remote access to this system if somebody wants to login and try
anything to fix this.
...deon
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-bugs] [Bug 87] New: zaptel driver generates kernel dump in Xen0,
deon <=
|
|
|
|
|