Error loading DAHDI

Hey guys, I´m updating from Zaptel to DAHDI drivers, I have an TDM400 and a TDM2400 … I´ve installed the dahdi current, with no errors on compilation, when I restarted my server, i got this error when trying to load DAHDI:

dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.2.0.2
tormenta2 0000:02:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
Invalid Xilinx 8 bit Base resource
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [] free_tor+0xb/0x4b [tor2]
*pde = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/class/bdi/8:16/uevent
Modules linked in: tor2(+) dahdi piix

Pid: 821, comm: modprobe Not tainted (2.6.30.5 #2)
EIP: 0060:[] EFLAGS: 00010293 CPU: 0
EIP is at free_tor+0xb/0x4b [tor2]
EAX: 00000000 EBX: 00000000 ECX: c18076d0 EDX: 00000000
ESI: f7088000 EDI: 00000000 EBP: 00002000 ESP: f6b0dc60
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 821, ti=f6b0c000 task=f71346e0 task.ti=f6b0c000)
Stack:
f7088000 f70a1800 f70893dc f81cf413 f6aae600 f6aae660 c01aa7dc 00000000
f81d0be0 f6cc2d70 f6b0dcac c0184cc3 f6cc2d70 c01aa9dd 00000000 f6aae600
f70a1800 f81e1e80 ffffffed c028c6a3 c02310ac c02310c2 f81e1e80 f70a1800
Call Trace:
[] ? tor2_probe+0x6d1/0x6de [tor2]
[] ? sysfs_add_one+0x12/0xb9
[] ? iput+0x21/0x45
[] ? sysfs_addrm_finish+0x3b/0x80
[] ? __driver_attach+0x0/0x5b
[] ? local_pci_probe+0xb/0xc
[] ? pci_call_probe+0x15/0x19
[] ? __pci_device_probe+0x2e/0x3f
[] ? pci_device_probe+0x1b/0x2d
[] ? really_probe+0x67/0xdb
[] ? __driver_attach+0x40/0x5b
[] ? bus_for_each_dev+0x38/0x59
[] ? driver_attach+0x11/0x13
[] ? __driver_attach+0x0/0x5b
[] ? bus_add_driver+0xc9/0x183
[] ? kset_find_obj+0x2f/0x52
[] ? driver_register+0x72/0x92
[] ? __pci_register_driver+0x32/0x66
[] ? tor2_init+0x0/0x26 [tor2]
[] ? tor2_init+0x15/0x26 [tor2]
[] ? do_one_initcall+0x4c/0x14c
[] ? number+0x14d/0x28e
[] ? sub_alloc+0x59/0x12d
[] ? idr_get_empty_slot+0x10d/0x11d
[] ? ida_get_new_above+0xec/0x16a
[] ? idr_get_empty_slot+0x10d/0x11d
[] ? sysfs_find_dirent+0x15/0x27
[] ? __sysfs_add_one+0x55/0x5d
[] ? sysfs_add_one+0x12/0xb9
[] ? sysfs_addrm_start+0x31/0x83
[] ? sysfs_addrm_finish+0xe/0x80
[] ? sysfs_add_file_mode+0x48/0x66
[] ? create_files+0x73/0xb9
[] ? add_partial+0xe/0x40
[] ? __slab_free+0x5a/0x94
[] ? __vunmap+0x7c/0x8a
[] ? kfree+0xa2/0xab
[] ? __vunmap+0x7c/0x8a
[] ? load_module+0x921/0x9ca
[] ? tracepoint_module_notify+0x21/0x24
[] ? notifier_call_chain+0x37/0x65
[] ? __blocking_notifier_call_chain+0x37/0x40
[] ? sys_init_module+0x87/0x188
[] ? syscall_call+0x7/0xb
Code: 81 44 24 04 ac 01 00 00 83 44 24 08 08 83 7c 24 14 03 0f 8e a6 fd ff ff 83 c4 18 5b 5e 5f 5d c3 57 31 ff 56 89 c6 53 31 db eb 0d <8b> 04 98 85 c0 74 05 e8 b5 4f fa c7 43 83 be d0 13 00 00 02 8b
EIP: [] free_tor+0xb/0x4b [tor2] SS:ESP 0068:f6b0dc60
CR2: 0000000000000000
—[ end trace 8ae928cdd697383b ]—

My kernel is 2.6.30.5…

Any ideas? Thanks!

maybe your kernel is too new.

Same problem. I ran an update yesterday and now my Asterisk in not operational. Anytime it does anything with a call it disconnects.

How do I downgrade my kernel?

Depends on your OS. For CentOS, assuming that the earlier kernel was ever installed, edit the grub configuration to make the earlier kernel the default.

Is .30. beta or released? There was a recent Asterisk issue that was rejected on the grounds that they would not adapt the code for a beta kernel. However, if this is a release kernel, you should raise a bug report.

I have had this system installed for over a year. All of a sudden it starts to fail. I have dahdi installed but it fails at start up.

You are contradicting yourself.

No. the system has been installed for over a year. I do a yum update every week. The last one seems to have made dahdi not work.