"Ouch, part reset..." error has been discussed on Users at length.
Check my last email here (but see the complete thread):
http://lists.digium.com/pipermail/asterisk-users/2005-April/104390.html
Now I get that error once a month or less, down from once or twice a week.
Some say it is related with the revision of the TDM400 card, I bet yours is
E/F. H is supposed to be good.
----- Original Message -----
From: Staffan Ulfberg
To: [email protected]
Sent: Thursday, June 02, 2005 2:57 AM
Subject: [Asterisk-bsd] zaptel problem with TDM11B
Hello,
Sometimes (maybe once a week), my zaptel (TDM11B, i.e., TDM400P with
one FXS and one FXO module) driver (the lastest svn version of wcfxs
from the zaptel-bsd repository) "hangs": My analog phone connected to
the fxs interface does not work anymore. The fxo interface is not
used at all, and is not even configured in zaptel.conf.
When this happens, a lot of information is repeatedly logged in my
syslog (and dmesg) -- about once a second the following is output:
Jun 2 01:45:37 multivac kernel: Ouch, part reset, quickly restoring reality
(0)
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW_0_PEAK iREG 0 = 0 should
be
55c2
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW_1_PEAK iREG 1 = 0 should
be
51e6
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW2_PEAK iREG 2 = 0 should
be 4
b85
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW3_PEAK iREG 3 = 0 should
be 4
937
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_COL1_PEAK iREG 4 = 0 should
be 3
333
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_FWD_TWIST iREG 5 = 0 should
be 2
02
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_RVS_TWIST iREG 6 = ff37
should b
e 202
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW_RATIO_TRES iREG 7 = 0
should
be 198
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_COL_RATIO_TRES iREG 8 = 0
should
be 198
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_ROW_2ND_ARM iREG 9 = 2
should be
611
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_COL_2ND_ARM iREG a = 0
should be
202
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_PWR_MIN_TRES iREG b = 0
should b
e e5
Jun 2 01:45:37 multivac kernel: !!!!!!! DTMF_OT_LIM_TRES iREG c = 2
should be
a1c
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC1_COEF iREG d = 0 should be
7b30
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC1X iREG e = 0 should be 63
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC1Y iREG f = 1c should be 0
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC2_COEF iREG 10 = 0 should be
7870
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC2X iREG 11 = 0 should be 7d
Jun 2 01:45:37 multivac kernel: !!!!!!! OSC2Y iREG 12 = 70 should be 0
Jun 2 01:45:37 multivac kernel: !!!!!!! RING_OSC iREG 14 = 0 should be
7ef0
Jun 2 01:45:37 multivac kernel: !!!!!!! RING_X iREG 15 = 0 should be 160
Jun 2 01:45:37 multivac kernel: !!!!!!! PULSE_ENVEL iREG 17 = 0 should be
200
0
Jun 2 01:45:37 multivac kernel: !!!!!!! PULSE_X iREG 18 = 0 should be
2000
Jun 2 01:45:37 multivac kernel: !!!!!!! RECV_DIGITAL_GAIN iREG 1a = 0
should
be 2000
Jun 2 01:45:37 multivac kernel: !!!!!!! XMIT_DIGITAL_GAIN iREG 1b = 0
should
be 4000
Jun 2 01:45:37 multivac kernel: !!!!!!! LOOP_CLOSE_TRES iREG 1c = 0
should be
1000
Jun 2 01:45:37 multivac kernel: !!!!!!! RING_TRIP_TRES iREG 1d = 0 should
be
3600
Jun 2 01:45:37 multivac kernel: !!!!!!! COMMON_MIN_TRES iREG 1e = 0
should be
1000
Jun 2 01:45:37 multivac kernel: !!!!!!! COMMON_MAX_TRES iREG 1f = 0
should be
200
Jun 2 01:45:37 multivac kernel: !!!!!!! PWR_ALARM_Q1Q2 iREG 20 = 0 should
be
7c0
Jun 2 01:45:37 multivac kernel: !!!!!!! PWR_ALARM_Q3Q4 iREG 21 = 0 should
be
2600
Jun 2 01:45:37 multivac kernel: !!!!!!! PWR_ALARM_Q5Q6 iREG 22 = 0 should
be
1b80
Jun 2 01:45:37 multivac kernel: !!!!!!! LOOP_CLOSURE_FILTER iREG 23 = 0
shoul
d be 8000
Jun 2 01:45:37 multivac kernel: !!!!!!! RING_TRIP_FILTER iREG 24 = 80
should
be 320
Jun 2 01:45:37 multivac kernel: !!!!!!! TERM_LP_POLE_Q1Q2 iREG 25 = 0
should
be 8c
Jun 2 01:45:37 multivac kernel: !!!!!!! TERM_LP_POLE_Q3Q4 iREG 26 = 0
should
be 100
Jun 2 01:45:37 multivac kernel: !!!!!!! TERM_LP_POLE_Q5Q6 iREG 27 = 8c
should
be 10
Jun 2 01:45:37 multivac kernel: !!!!!!! CM_BIAS_RINGING iREG 28 = 0
should be
c00
Jun 2 01:45:37 multivac kernel: !!!!!!! DCDC_MIN_V iREG 29 = 0 should be
c00
Jun 2 01:45:37 multivac kernel: !!!!!!! DCDC_XTRA iREG 2a = 0 should be
1000
Jun 2 01:45:37 multivac kernel: !!!!!!! LOOP_CLOSE_TRES_LOW iREG 2b = 0
shoul
d be 1000
Jun 2 01:45:37 multivac kernel: !!!!! Init Indirect Registers
UNSUCCESSFULLY.
Jun 2 01:45:37 multivac kernel: Indirect Registers failed verification.
When this happens, I can unload the kernel module, and reload it, and
operation resumes to normal.
I've seen this since I started using Asterisk a few months ago. Has
anyone else seen the problem?
Staffan
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
