[asterisk-bugs] [DAHDI-linux 0013205]: [patch] bad master selection
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Mar 6 13:48:09 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13205
======================================================================
Reported By: biohumanoid
Assigned To: kpfleming
======================================================================
Project: DAHDI-linux
Issue ID: 13205
Category: dahdi (the module)
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 2008-07-31 00:11 CDT
Last Modified: 2009-03-06 13:48 CST
======================================================================
Summary: [patch] bad master selection
Description:
Current dahdi master handling work in the following way:
The first SPAN become a master
If a new registered !!! SPAN is preferred , it is the new master
If a span is unregistered - the new master is the first available span
If master SPAN is in alarm state - the new master is the first non in
alarm state SPAN
So
1. dahdi-dummy once loaded will be the master forever.
2. even not-running SPAN can be a master
3. master implementation is ugly...
======================================================================
----------------------------------------------------------------------
(0101315) sruffell (administrator) - 2009-03-06 13:48
http://bugs.digium.com/view.php?id=13205#c101315
----------------------------------------------------------------------
I'm also wondering out loud, with the cards that do not have such stringent
requirements for interrupt to isr latency, whether the sync_tick method
could be used to allow a board to mask off it's interrupt and be polled
along with the other hardware. I know there have been some discussion
about this subject that predates my involvement with the project.
But, for example, if a wcte12xp or wctdm24xxp supported card is not the
master span, it could implement the sync_tick function and then disable
interrupts on it's interface and then poll in the sync_tick function.
Issue History
Date Modified Username Field Change
======================================================================
2009-03-06 13:48 sruffell Note Added: 0101315
======================================================================
More information about the asterisk-bugs
mailing list