Over the last few days, ISDN connection would disconnect with just a few seconds of inactivity even though disconnect is set at 300 seconds. Often, clear int bri0 was required to reconnect. Follosing is part of message with the clear command:
PANIC! Dumping old buffered faults.
PANIC! Dumping fault causing the panic.
Memory Protection Violation:
epc =0x001AB388, location of fault eva =Ox00000???, write fault address
error=0x00000080, illegal address pti 0x00000000 pte =OXFFFFF100
== Flushing messages (05:50:16 central Thu Dec 8 2005)
Queued messages: 23:08:50: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
23:08:214748364800: %SYS-3-MGDTIMER: NZ prey pointer but not running, timer = 6B 4210.
-Process= “ISDN”, ipl= 6, pid= 42
-Traceback= 1AA874 1AB3D8 1AB560 4BA86C 4D1B94 4D38A0 4AF8B4 4AF884
Data TLB Error Exception (0x1400)! CPU Register Context: VEC = 0x00001400 PC = 0x0O1AB388 MSR = 0x00009032 CR = 0x33000030
Finally, the bri interface has died. Following are the last few lines of a log:
LINK-3-UPDOWN: Interface BRI0:2, changed state to down
2005-12-09 01:45:00 Local7.Error 192.168.0.1 92: 04:03:188985410468: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
2005-12-09 01:45:11 Local7.Error 192.168.0.1 93: 04:03:236224735096: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
2005-12-09 01:45:23 Local7.Error 192.168.0.1 94: 04:04:34366587812: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
2005-12-09 01:50:45 Local7.Error 192.168.0.1 95: 04:09:128855868244: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
2005-12-09 01:53:33 Local7.Error 192.168.0.1 96: 04:12:77310945144: %LINK-3-UPDOWN: Interface BRI0:2, changed state to down
2005-12-09 01:54:00 Local7.Error 192.168.0.1 97: 04:12:188980094840: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
2005-12-09 02:05:37 Local7.Error 192.168.0.1 98: 04:24:21: %SYS-3-MGDTIMER: NZ prev pointer but not running, timer = 6B4210.
2005-12-09 02:05:37 Local7.Error 192.168.0.1 99: -Process= "ISDN L2 Process", ipl= 6, pid= 52
2005-12-09 02:05:37 Local7.Error 192.168.0.1 100: -Traceback= 1AA874 1AAC94 1AF3D0 4BB1E0 3203C
And finally, console messages as the interface died today:
518BD8 handle 0
00:08:28: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 66 changed to uponfiguration:
00:08:30: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 67 changed to down
00:08:39: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 67 changed to up
00:08:39: event = 0x1403
00:08:39: %ISDN-6-NO_TIMER: No Free Timer Entry, caller 0x5185A0, timers used 41
00:08:39: %ISDN-6-INVALID_TIMER: LIF_StartTimer: Invalid Timer Handle, caller 0x518BD8 handle 0
00:08:40: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 68 changed to up
00:08:40: event = 0x1403
00:08:40: %ISDN-6-NO_TIMER: No Free Timer Entry, caller 0x5185A0, timers used 41
00:08:40: %ISDN-6-INVALID_TIMER: LIF_StartTimer: Invalid Timer Handle, caller 0x518BD8 handle 0
00:09:55834615808: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BRI0, TEI 67 changed to down
00:09:13: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 67 changed to down
00:09:55834615808: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BRI0, TEI 68 changed to down
00:09:13: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 68 changed to down
00:09:13: %SYS-3-MGDTIMER: NZ prev pointer but not running, timer = 6B4210.
-Process= "ISDN L2 Process", ipl= 6, pid= 53
-Traceback= 1AA874 1AAC94 1AF3D0 4BB1E0 3203C
I know that I need to run some debugs but I'm on the road, so thought someone may save me some time by at least pointing me to the more likely direct problem.
Telco switches were checked and everything is ok on their end.
