[asterisk-bugs] [DAHDI-linux 0015647]: Server crash after I do ntpdate -u ntp.nasa.gov

Tue Aug 4 10:54:01 CDT 2009

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15647 
====================================================================== 
Reported By:                missnebun
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15647
Category:                   dahdi_dummy
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-08-03 22:14 CDT
Last Modified:              2009-08-04 10:54 CDT
====================================================================== 
Summary:                    Server crash after I do ntpdate -u ntp.nasa.gov
Description: 
I compile the last version ... the same ...
I do ntpdate -u ntpnasa.gov takes like few min with the error and then
crash.

Aug  3 22:44:34 pbx1 kernel: BUG: soft lockup - CPU#1 stuck for 10s!
[swapper:0]
Aug  3 22:44:34 pbx1 kernel:
Aug  3 22:44:34 pbx1 kernel: Pid: 0, comm:              swapper
Aug  3 22:44:34 pbx1 kernel: EIP: 0060:[<c060f4d8>] CPU: 1
Aug  3 22:44:34 pbx1 kernel: EIP is at _spin_unlock_irqrestore+0x8/0x9
Aug  3 22:44:34 pbx1 kernel:  EFLAGS: 00000246    Tainted: G      
(2.6.18-128.2.1.el5PAE https://issues.asterisk.org/view.php?id=1)
Aug  3 22:44:34 pbx1 kernel: EAX: f8f737f0 EBX: 00000002 ECX: 00000246
EDX: 00000200
Aug  3 22:44:34 pbx1 kernel: ESI: 00000001 EDI: f8f819e0 EBP: 00000000 DS:
007b ES: 007b
Aug  3 22:44:34 pbx1 kernel: CR0: 8005003b CR2: b7d54000 CR3: 0072c000
CR4: 000006f0
Aug  3 22:44:34 pbx1 kernel:  [<f8f69b90>] dahdi_receive+0x755/0x776
[dahdi]
Aug  3 22:44:34 pbx1 kernel:  [<f8f6d147>] dahdi_transmit+0x11/0x48d
[dahdi]
Aug  3 22:44:34 pbx1 kernel:  [<f8efd26b>] dahdi_dummy_timer+0x8b/0xcc
[dahdi_dummy]
Aug  3 22:44:34 pbx1 kernel:  [<f8efd1e0>] dahdi_dummy_timer+0x0/0xcc
[dahdi_dummy]
Aug  3 22:44:34 pbx1 kernel:  [<c042c5b1>] run_timer_softirq+0xfb/0x151
Aug  3 22:44:34 pbx1 kernel:  [<c0429047>] __do_softirq+0x87/0x114
Aug  3 22:44:34 pbx1 kernel:  [<c04073d7>] do_softirq+0x52/0x9c
Aug  3 22:44:34 pbx1 kernel:  [<c04059d7>] apic_timer_interrupt+0x1f/0x24
Aug  3 22:44:34 pbx1 kernel:  [<c0403bb0>] default_idle+0x0/0x59
Aug  3 22:44:34 pbx1 kernel:  [<c0403be1>] default_idle+0x31/0x59
Aug  3 22:44:34 pbx1 kernel:  [<c0403ca8>] cpu_idle+0x9f/0xb9
Aug  3 22:44:34 pbx1 kernel:  =======================
Aug  3 22:44:44 pbx1 kernel: BUG: soft lockup - CPU#1 stuck for 10s!
[swapper:0]
Aug  3 22:44:44 pbx1 kernel:
Aug  3 22:44:44 pbx1 kernel: Pid: 0, comm:              swapper
Aug  3 22:44:44 pbx1 kernel: EIP: 0060:[<c060f4d8>] CPU: 1
Aug  3 22:44:44 pbx1 kernel: EIP is at _spin_unlock_irqrestore+0x8/0x9
Aug  3 22:44:44 pbx1 kernel:  EFLAGS: 00000246    Tainted: G      
(2.6.18-128.2.1.el5PAE https://issues.asterisk.org/view.php?id=1)
Aug  3 22:44:44 pbx1 kernel: EAX: f8f737f0 EBX: 00000002 ECX: 00000246
EDX: 00000200
Aug  3 22:44:44 pbx1 kernel: ESI: 00000001 EDI: f8f819e0 EBP: 00000000 DS:
007b ES: 007b
Aug  3 22:44:44 pbx1 kernel: CR0: 8005003b CR2: b7d54000 CR3: 0072c000
CR4: 000006f0
Aug  3 22:44:44 pbx1 kernel:  [<f8f69b90>] dahdi_receive+0x755/0x776
[dahdi]
Aug  3 22:44:44 pbx1 kernel:  [<f8f69bad>] dahdi_receive+0x772/0x776
[dahdi]
Aug  3 22:44:44 pbx1 kernel:  [<f8efd26b>] dahdi_dummy_timer+0x8b/0xcc
[dahdi_dummy]
Aug  3 22:44:44 pbx1 kernel:  [<f8efd1e0>] dahdi_dummy_timer+0x0/0xcc
[dahdi_dummy]
Aug  3 22:44:44 pbx1 kernel:  [<c042c5b1>] run_timer_softirq+0xfb/0x151
Aug  3 22:44:44 pbx1 kernel:  [<c0429047>] __do_softirq+0x87/0x114
Aug  3 22:44:44 pbx1 kernel:  [<c04073d7>] do_softirq+0x52/0x9c
Aug  3 22:44:44 pbx1 kernel:  [<c04059d7>] apic_timer_interrupt+0x1f/0x24
Aug  3 22:44:44 pbx1 kernel:  [<c0403bb0>] default_idle+0x0/0x59
Aug  3 22:44:44 pbx1 kernel:  [<c0403be1>] default_idle+0x31/0x59
Aug  3 22:44:44 pbx1 kernel:  [<c0403ca8>] cpu_idle+0x9f/0xb9
Aug  3 22:44:44 pbx1 kernel:  =======================
Aug  3 22:44:54 pbx1 kernel: BUG: soft lockup - CPU#1 stuck for 10s!
[swapper:0]
Aug  3 22:44:54 pbx1 kernel:
Aug  3 22:44:54 pbx1 kernel: Pid: 0, comm:              swapper
Aug  3 22:44:54 pbx1 kernel: EIP: 0060:[<c060f4d8>] CPU: 1
Aug  3 22:44:54 pbx1 kernel: EIP is at _spin_unlock_irqrestore+0x8/0x9
Aug  3 22:44:54 pbx1 kernel:  EFLAGS: 00000246    Tainted: G      
(2.6.18-128.2.1.el5PAE https://issues.asterisk.org/view.php?id=1)
Aug  3 22:44:54 pbx1 kernel: EAX: f8f737f0 EBX: 00000002 ECX: 00000246
EDX: 00000200
Aug  3 22:44:54 pbx1 kernel: ESI: 00000001 EDI: f8f859f0 EBP: 00000000 DS:
007b ES: 007b
Aug  3 22:44:54 pbx1 kernel: CR0: 8005003b CR2: b7d54000 CR3: 0072c000
CR4: 000006f0
Aug  3 22:44:54 pbx1 kernel:  [<f8f69b90>] dahdi_receive+0x755/0x776
[dahdi]
Aug  3 22:44:54 pbx1 kernel:  [<f8f69440>] dahdi_receive+0x5/0x776
[dahdi]
Aug  3 22:44:54 pbx1 kernel:  [<f8efd26b>] dahdi_dummy_timer+0x8b/0xcc
[dahdi_dummy]
Aug  3 22:44:54 pbx1 kernel:  [<f8efd1e0>] dahdi_dummy_timer+0x0/0xcc
[dahdi_dummy]
Aug  3 22:44:54 pbx1 kernel:  [<c042c5b1>] run_timer_softirq+0xfb/0x151
Aug  3 22:44:54 pbx1 kernel:  [<c0429047>] __do_softirq+0x87/0x114
Aug  3 22:44:54 pbx1 kernel:  [<c04073d7>] do_softirq+0x52/0x9c
Aug  3 22:44:54 pbx1 kernel:  [<c04059d7>] apic_timer_interrupt+0x1f/0x24
Aug  3 22:44:54 pbx1 kernel:  [<c0403bb0>] default_idle+0x0/0x59
Aug  3 22:44:54 pbx1 kernel:  [<c0403be1>] default_idle+0x31/0x59
Aug  3 22:44:54 pbx1 kernel:  [<c0403ca8>] cpu_idle+0x9f/0xb9
Aug  3 22:44:54 pbx1 kernel:  =======================

====================================================================== 

---------------------------------------------------------------------- 
 (0108599) sruffell (administrator) - 2009-08-04 10:54
 https://issues.asterisk.org/view.php?id=15647#c108599 
---------------------------------------------------------------------- 
I'll have an update for this later today.  My current hypothesis is that
since dahdi dummy uses the actual passage of time to know how many times to
tick dahdi, that after you run ntpdate, dahdi thinks that it has many many
ticks it needs to call in order to catch up.  So....I'll fix dahdi_dummy to
place an upper limit on the number of times it tries to catch up (which I
should have had in there to begin with).

My guess is that you could also resolve this by ensuring that ntp is
started before dahdi in your init scripts on system boot. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-04 10:54 sruffell       Note Added: 0108599                          
======================================================================