SPA112 goes catatonic, crashes, no dialtone - Page 2

sgtpanties · ‎10-26-2012

Hi, I am a home user and ex-programmer. I'm using the Cisco SPA112 with the latest firmware 1.2.1 (004). Every two or three days the ATA crashes. Here are the symptoms:

a) no dial tone

b) line 1 LED is ON (as normal)

c) ATA is PINGable

d) IVR is unresponsive

e) web setup URL does not respond, can not get to the setup page

f) The reset button does not respond.

My only recourse now is the check if I have a dialtone every morning and, if not, pull and reinsert the power plug. The cold boot of course results in the local log being lost. Here is the log right after boot up.

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] Machine: NXP PNX8181

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] Memory policy: ECC disabled, Data cache writeback

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: D VIVT write-back cache

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

Jan 1 00:00:04 SPA112 kern.warning [ 0.000000] CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets

Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 7874

Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] PID hash table entries: 128 (order: 7, 512 bytes)

Jan 1 00:00:04 SPA112 kern.warning [17179569.184000] Console: colour dummy device 80x30

Jan 1 00:00:04 SPA112 kern.warning [17179569.260000] Mount-cache hash table entries: 512

Jan 1 00:00:04 SPA112 kern.warning [17179569.264000] Board HW MODEL : 0x3

Jan 1 00:00:04 SPA112 kern.warning [17179569.336000] squashfs: LZMA suppport for slax.org by jro

Jan 1 00:00:04 SPA112 kern.warning [17179569.384000] [ip3912] : Bridge Mode...

Jan 1 00:00:04 SPA112 kern.err [17179569.408000] physmap-flash physmap-flash.0: map_probe failed

Jan 1 00:00:04 SPA112 kern.warning [17179569.416000] Using Full Image\'s RootFS

Jan 1 00:00:04 SPA112 kern.warning [17179569.420000] Using static partition definition

Jan 1 00:00:04 SPA112 kern.warning [17179569.424000] !!! do adler32 checksum !!!

Jan 1 00:00:04 SPA112 kern.warning [17179571.260000] File system image checksum OK

Jan 1 00:00:04 SPA112 kern.err [17179571.344000] ksz8873 0-005f: failed with status -1

Jan 1 00:00:04 SPA112 kern.warning [17179571.348000] ksz8873: probe of 0-005f failed with error -1

Jan 1 00:00:04 SPA112 kern.warning [17179571.352000] PNX8181 watchdog timer: timer margin 16 sec

Jan 1 00:00:04 SPA112 kern.warning [17179571.372000] GACT probability on

Jan 1 00:00:04 SPA112 kern.warning [17179571.376000] Mirror/redirect action on

Jan 1 00:00:04 SPA112 kern.warning [17179571.380000] u32 classifier

Jan 1 00:00:04 SPA112 kern.warning [17179571.384000] Performance counters on

Jan 1 00:00:04 SPA112 kern.warning [17179571.388000] input device check on

Jan 1 00:00:04 SPA112 kern.warning [17179571.392000] Actions configured

Jan 1 00:00:04 SPA112 kern.warning [17179571.396000] Netfilter messages via NETLINK v0.30.

Jan 1 00:00:04 SPA112 kern.warning [17179571.400000] nf_conntrack version 0.5.0 (1024 buckets, 4096 max)

Jan 1 00:00:04 SPA112 kern.warning [17179571.412000] ipt_time loading

Jan 1 00:00:04 SPA112 kern.warning [17179571.464000] VFS: Mounted root (squashfs filesystem) readonly.

Jan 1 00:00:04 SPA112 kern.warning [17179576.144000] ***** LED_DRV init *****

Jan 1 00:00:04 SPA112 kern.warning [17179576.148000] ***** LED_DRV end *****

Jan 1 00:00:04 SPA112 kern.warning [17179576.176000] *** sys event driver initialized ***

Jan 1 00:00:04 SPA112 kern.err [17179579.184000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

Jan 1 00:00:04 SPA112 kern.warning [17179580.880000] Empty flash at 0x00069454 ends at 0x00069600

Jan 1 00:00:05 SPA112 daemon.err dnsmasq[136]: failed to load names from /etc/hosts: No such file or directory

Jan 1 00:00:23 SPA112 kern.err [17179600.844000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

Jan 1 00:00:27 SPA112 daemon.err system[1]: notify add wan1 interface(br0)

Jan 1 00:00:27 SPA112 daemon.err system[1]: start 0 vlan-id... ok

Jan 1 00:00:39 SPA112 daemon.err dnsmasq[136]: failed to load names from /etc/hosts: No such file or directory

Here are some things I have tried on my own, to no effect:

a) Tried running with Provisioning/Firmware Upgrade/Upgrade set to false.

b) Reloaded the firmware with IE. Before, I did it with FireFox.

c) Did a factory reset and re-entered the settings suggested for my ATA from Callcentric.

How should I proceed?

Patrick Born · ‎11-02-2012

Hi Tom,

I'd like to work with you to better understand the issues you're experiencing and hopefully improve your SPA112 experience. Please contact me directly at paborn@cisco.com

Regards,

Patrick

----------

mananna01 · ‎11-03-2012

Patrick:

Another user of a SPA112-2 having the same issues as mentioned by T Walter & R Buchko. Also a CallCentric client and also had to wait until the DDoS simmered down and power was restored to their facility to assure myself that it was the unit and not CallCentric.

As mentioned I've had basically the same experience, although not due to voice mail, just uptime for approximately two to three days and then a hard lockup which is evidenced by no dial tone and no web access to the unit until a power down and reboot. I would also note that this has happened repeatedly over the month that I've had the unit operating. The unit is new in my hands and was purchased from NewEgg approximately a month and a half ago.

Log reports are fine for the uptime and then disappear as a result of the hard power down and reboot that is required to restore the unit to operational on the day it locks up, i.e. I have the log report for day 1 & 2, nothing for day 3 and then a log continuing on with day 1 & 2 plus the reboot information but skipping the period between the day 2 power down and reboot.

The unit is connected behind a Cisco E4200, with QOS enabled for voip, and the SPA112-2 is set up according to the CallCentric parameters for the unit.

Both the E4200 and the SPA112-2 have been updated to the latest non-beta firmware releases and both were updated before signing up with CallCentric.

Although I don't believe my computer is causing any problems with the unit I'll mention that I run either Win 7 Pro 64bit and Suse Linux 12.2 64bit in a dual boot situation as I need access to both at various times during the day or night.

Thanks for any help you can render.

Peter

nathanmeyers · ‎11-03-2012

Patrick,

I have also been experiencing the lockup issues, with the 1.2.1 (004) firmware. I can't add anything to the descriptions you've already received - my symptoms are identical.

By unhappy coincidence, I updated to that firmware around the time of the Callcentric DDOS attacks, so didn't realize I had taken on a Cisco problem at the same time - but evidently I did. This is clearly a widespread problem.

Nathan

elight942 · ‎11-13-2012

I have 24 SPA112 units (hardware 1.0.0, firmware 1.2.1(004), initially - 1.0.1.022) with same problem - no reaction after 3-6 days uptime even with zero calls activity (only registration on local Asterisk server). Tried different network settings, routers, switches with no luck.

Wrote a script to reboot them via http every midnight - so far so good.

Tell me if you need some debug information or testing.

Patrick Born · ‎11-13-2012

Hi Alex,

Please contact me at paborn@cisco.com and I'll get you some test firmware if you're still willing to help.

Thanks,

Patrick

-----------

bryanosborne · ‎11-05-2012

I am also having the same issue with my SPA112 running 1.2.1 firmware as described...no dial tone...IVR won't respond...and the only way to "fix" it is to unplug and plug back in, and it is only a day or so before it is messed up again. Could sure use a fix for this. ;-(

Patrick Born · ‎11-05-2012

Hi Peter, Nathan, and Bryan,

Please contact me at paborn@cisco.com and I'll try my best to help out.

Rest of community: I've had limited success with duplicating this issue in my lab and am testing out a firmware fix that will be officially pubished ASAP.

Regards,

Patrick

----------

mananna01 · ‎11-05-2012

Patrick:

I've just sent you an email responding to your post above. If not received please advise and I'll post the contents here.

Thanks,

Peter

danbuchko · ‎11-07-2012

For those who have received the engineering build 1.3.0 (016) of the firmware from Patrick, have you also noticed decreased call quality? I am finding the sound very choppy, often have to get people to repeat themselves. Have done both local and international calls with the new firmware but all seem to have the degraded sound, am curious to know if others are experiencing the same?

(I've also e-mailed Patrick directly about this issue, and sent him the log file.)

Regards,

Dan

mananna01 · ‎11-07-2012

Daniel:

My phone is not that active but yes to your query and like you I've sent my logs and an email to Patrick Born.

As I mentioned in an earlier post I'm using CallCentric, which had been good, but they may still be fighting the remains of Sandy as well as the month long DDoS attack which might be a contributing factor in my case.

Unfortunately I've also experienced two freezes of the unit since receiving and installing the new firmware but was able to reboot using the web interface and did not have to power down. I've been up on the new firmware since early this a.m. and if it holds true to form based on earlier today activity the unit may go down in the next hour or so. Keeping my fingers crossed. (g)

However, the above not withstanding, I'm appreciative of the quick response from Patrick Born, as well as the Cisco team behind him, and do hope they can isolate the issue(s?) and get them fixed ASAP. Bug patrol is not easy nor is it fun and a slip of the finger can easily introduce another issue which may, or may not, show up when they recompile the code.

Peter

mananna01 · ‎11-08-2012

This is just an update to my post of yesterday in response to DB.

The SPA112-2 ran through the night with no lockup and with CallCentric registration maintained.

Garbled voice and shutdowns experienced yesterday were apparently caused by CallCentric issues as they are, apparently, still experiencing a DDoS attack and are also still doing modifications to their software to fight the attack.

Peter

danbuchko · ‎11-08-2012

I'm not 100% convinced the garbled voice is a CallCentric issue, although it could be. I downgraded my firmware back to the August release, and just got off a long call (100+ minutes) without any quality issues -- voice was crystal clear.

Patrick Born · ‎11-08-2012

Thanks for the update Peter. The only time we can replicate garbled voice is with compromised line speeds but will continue chasing this.

Regards,

Patrick

----------

danbuchko · ‎12-01-2012

Patrick, a couple weeks ago I re-installed the engineering beta you'd sent me, version 1.3.0(016). Since that time, I have not experienced the call quality issues that I had previously reported, so I now suspect they were indeed a result of Callcentric's problems and not the SPA112 firmware. In addition, the modem has not required rebooting, so I am cautiously optimistic that this build has resolved the major issues.

Regards,

Dan

sgtpanties · ‎11-08-2012

Gentlemen, my mother broke her hip on the 31st so I don't have much time to dabble with this.

I installed the new firmware Tuesday noon-ish. The only problem I have encountered was that the ATA lost registration w/Callcentric Wednesday evening. Unlike the original problem symptoms, it the ATA's web setup pages were accessible and the reset button worked. I didn't check the IVR. Will contribute more as I get a chance.

--tom