I have lately acquired a TE410P. The problem i face currently is that the span gets(or doesnt gets) UP in an uneven fashion i.e i have to load-unload the modules, wait for sometime and then start the application.... i dont know but this execise works well for me (though not neccassary that this works in first shot, but after retrying it somehow works). It is a tedious exercise and moreover i cannot manage to do it when i ve to use it in an auto-startup way i.e after a reboot the whole thing should come up by itself.
There is no evidence of any strange things happening except for the `Double/missed interrupt detected` shown in dmesg. `zttool` shows that the span status is OK.
Any thoughts on why i m getting such odd problems? Has anyone else faced the same problem (plz reply if u ve managed to fix it)?
Thanx,
Rahul
Mark Spencer wrote:
a.) In an effort to push Linux's poor job of handling interrupt
latancy, which makes it a not so good choice for real time systems
that the TE410 driver is simply pushing the limits a little.
Which is all right by me :)
Well, Zaptel needs to service interrupts once every 1000 microseconds. If not, it misses a sample (not the end of the world, mind you). No driver should leave interrupts disabled for anywhere *near* 1000 microseconds. If you need that long, put it in a bottom-half handler.
b.) The TE410 driver needs a little tweaking to play better
with others and handle it's interrupt requests better.
Which is all right by me too :)
If interrupts are disabled there is nothing we can do, except not interrupt as frequently, but this leads to additional latency.
Mark
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
