| Summary: | DAHLIN-00091: loading dahdi_dummy crashes CentOS-xen kernel | ||
| Reporter: | Ask Bjørn Hansen (ask) | Labels: | |
| Date Opened: | 2009-04-13 08:04:30 | Date Closed: | 2009-04-29 12:48:35 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | dahdi_dummy |
| Versions: | 2.1.0.4 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Everytime i load dahdi_dummy (2.1.0.4) under 2.6.18-128.1.6.el5xen (latest RHEL/CentOS kernel) I get the following panic: Kernel BUG at kernel/timer.c:331 invalid opcode: 0000 [1] SMP last sysfs file: /class/dahdi/dahdi!ctl/dev CPU 0 Modules linked in: dahdi_dummy(U) wcfxo(U) wctdm24xxp(U) wcte12xp(U) wct4xxp(U) dahdi(U) crc_ccitt bluetooth autofs4 i2c_dev i2c_core sunrpc ipv6 xfrm_nalgo crypto_api ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables dm_multipath scsi_dh scsi_mod parport_pc lp parport xennet pcspkr dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 4362, comm: modprobe Tainted: G 2.6.18-128.1.6.el5xen #1 RIP: e030:[<ffffffff8021cac7>] [<ffffffff8021cac7>] __mod_timer+0x19/0xbe RSP: e02b:ffff88000bbd5e18 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffffffff806f7b20 RCX: 0000000100136490 RDX: 00000000000000fa RSI: 0000000100136495 RDI: ffffffff806f7b20 RBP: ffff88001230e000 R08: ffffffff804e5928 R09: 0000000000001e87 R10: 0000000000000000 R11: 0000000000000000 R12: 000000000002ea10 R13: 0000000100136495 R14: 0000000016c540f8 R15: 00002ae63e1fb010 FS: 00002ae63e1fa240(0000) GS:ffffffff805ba000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process modprobe (pid: 4362, threadinfo ffff88000bbd4000, task ffff880013bfe040) Stack: 000000000002ea10 00002ae63e1fb010 0000000000000000 ffff88001230e000 000000000002ea10 00002ae63e1fb010 0000000016c540f8 ffffffff80393d3a ffff8800172c4180 0000000000000400 Call Trace: [<ffffffff80393d3a>] rtc_do_ioctl+0x1c5/0x701 [<ffffffff802f4f0f>] proc_register+0x7d/0x115 [<ffffffff802f542d>] create_proc_entry+0x90/0xa6 [<ffffffff88324333>] :dahdi:dahdi_register+0x1a3/0x2ca [<ffffffff883fc318>] :dahdi_dummy:init_module+0x1db/0x257 [<ffffffff802a01c8>] sys_init_module+0xaf/0x1e8 [<ffffffff8025f2f9>] tracesys+0xab/0xb6 Code: 0f 0b 68 63 a3 48 80 c2 4b 01 48 8d 74 24 08 48 89 df 45 31 RIP [<ffffffff8021cac7>] __mod_timer+0x19/0xbe RSP <ffff88000bbd5e18> <0>Kernel panic - not syncing: Fatal exception | ||
| Comments: | By: Ask Bjørn Hansen (ask) 2009-04-13 08:07:17 FWIW, after patching with "patch 3" from DAHLIN-60 I can load dahdi_dummy. By: Jason Parker (jparker) 2009-04-13 11:02:43 Excellent. I was going to ask you to test that patch before reading your comment. I've posted a note to DAHLIN-60 pointing to this issue, so that hopefully it can be committed. I know that Xen testing was one of the big things holding that back. By: Digium Subversion (svnbot) 2009-04-29 12:48:34 Repository: dahdi Revision: 6524 U linux/trunk/drivers/dahdi/dahdi_dummy.c ------------------------------------------------------------------------ r6524 | sruffell | 2009-04-29 12:48:28 -0500 (Wed, 29 Apr 2009) | 12 lines dahdi_dummy: Remove real-time clock support. This removes support for using the real-time clock as a timing source in dahdi_dummy. Instead, the normal kernel timers method is now more accurate since it keeps track of how much real time has passed to determine how many times to call dahdi_receive and dahdi_transmit. This method was originally suggested by bmd. (closes issue DAHLIN-60) (closes issue DAHLIN-91) Reported by: tzafrir Tested by: dbackeberg, ask ------------------------------------------------------------------------ http://svn.digium.com/view/dahdi?view=rev&revision=6524 | ||