[asterisk-bugs] [DAHDI-linux 0016233]: Linux Crash on time change

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16233 
====================================================================== 
Reported By:                apsaras
Assigned To:                qwell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   16233
Category:                   dahdi_dummy
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
JIRA:                        
Reviewboard Link:            
Resolution:                 duplicate
Duplicate:                  15647
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-11-12 12:30 CST
Last Modified:              2009-11-12 12:39 CST
====================================================================== 
Summary:                    Linux Crash on time change
Description: 
I have a system with dahdi_dummy (Celeron M, 512Mb RAM, CentOS 5.4 32bit).
Every time I try to change the system time the linux is crashing complaning
about dadhi_dummy. The same problem appears if the ntp server tries to
change the time.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0015647 Server crash after I do ntpdate -u ntp....
====================================================================== 

---------------------------------------------------------------------- 
 (0113732) sruffell (administrator) - 2009-11-12 12:39
 https://issues.asterisk.org/view.php?id=16233#c113732 
---------------------------------------------------------------------- 
This is a duplicate of 15647. The update will be in the soon to be released
2.2.1.  Could you try the head of the 2.2 branch to make sure you don't
experience this issue? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-12 12:39 sruffell       Note Added: 0113732                          
2009-11-12 12:39 sruffell       Duplicate ID             0 => 15647          
2009-11-12 12:39 sruffell       Status                   closed => resolved  
2009-11-12 12:39 sruffell       Resolution               fixed => duplicate  
2009-11-12 12:39 sruffell       Status                   resolved => closed  
======================================================================