SPA 112

[mdharriscisco]

Hi There Everyone,

I am getting this output from a customers ATA - SPA112. Can anyone tell me what it means ?

<3>Jan  1 00:00:05 aklpuk1SPA112 [17179569.416000] physmap-flash physmap-flash.0: map_probe failed

<3>Jan  1 00:00:05 aklpuk1SPA112 [17179571.400000] ksz8873 0-005f: failed with status -1

<3>Jan  1 00:00:05 aklpuk1SPA112 [17179579.536000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

<27>Jan  1 00:00:06 aklpuk1SPA112 dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory

<3>Jan  1 00:00:18 aklpuk1SPA112 [17179595.936000]  Created coma thread for processing coma control message

<3>Jan  1 00:00:27 aklpuk1SPA112 [17179604.924000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

<27>Jan  1 00:00:32 aklpuk1SPA112 system[1]: notify add wan1 interface(br0)

<27>Jan  1 00:00:32 aklpuk1SPA112 system[1]: start 0 vlan-id... ok

<27>Jan  1 00:00:32 aklpuk1SPA112 dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory

Kind Regard,

Michael

[Dan Lukes]

Syslog&debug output emited during device boot. I see nothing suspicious nor uncommon in it.

By the way, no model like SPA110 exist. The output in question is from SPA112.

[aleksandar.ristovski1]

I have the same problem. It seems like a hardware issue. After several hours of normal operation, the following is captured in the log and after that nothing works. The line is practically dead. Reboot restores operation until this happens again. Sevral hours in between.

Faulty flash? Thermal issues? It definitely looks like a hardware issue.

Nov 30 16:05:25 SPA112 kern.err [17179569.420000] physmap-flash physmap-flash.0: map_probe failed
Nov 30 16:05:25 SPA112 kern.err [17179571.088000] ksz8873 0-005f: failed with status -1
Nov 30 16:05:25 SPA112 kern.err [17179580.076000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Nov 30 16:05:27 SPA112 daemon.err dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory
Nov 30 16:05:44 SPA112 kern.err [17179603.176000]  Created coma thread for processing coma control message
Nov 30 16:06:01 SPA112 kern.err [17179620.012000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Nov 30 16:06:02 SPA112 daemon.err system[1]: notify add wan1 interface(br0)
Nov 30 16:06:02 SPA112 daemon.err system[1]: start 0 vlan-id... ok
Nov 30 16:06:02 SPA112 daemon.err system[1]: add vlan-interface(SYSTEM_VLAN_INTERFACE_ADD) fail(-1)
Nov 30 16:06:02 SPA112 daemon.err dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory
Nov 30 23:25:38 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:25:39 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:25:41 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:25:45 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:25:51 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:25:53 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:26:09 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4
Nov 30 23:26:18 SPA112 daemon.err mDNSResponder: ERROR: getOptRdata - unknown opt 4

[Dan Lukes]

No way to have same problem, as mdharriscisco  has reported no problem. He just asked about meaning of some log records.

following is captured in the log and after that nothing works

So you seems to believe the issue is related to "mDNSResponder: ERROR: getOptRdata - unknown opt 4" message (as others are so old).

"The line is practically dead" is so vague description to make conclusions so I can neither confirm nor reject your hypothesis. You may consider to describe your issue in details. Note as you mentioned no firmware version I assume you are using the most recent one (1.4.1).

As a blind shot, I don't expect the message in question is related to a issue. Despite of it you may consider to disable Bonjour (protocol the message is related to). Use the Administration > Management > Bonjour page to disable Bonjour if you wish.

Related:

• WAP121 - mDNSResponder ERROR: getOptRdata - unknown opt 4
• ERROR: getOptRdata - unknown opt 4

[aleksandar.ristovski1]

Firmware: 1.4.1, I upgraded yesterday. Before that it was 1.3.1 with the same issue/symptomps.

I just disabled Bonjour. It will take some time to see if it made any difference.

"The line is practically dead": No incoming calls can go through. It is usually reported on e.g. cell phones as "network unreachable". When this happens my router seems to work just fine as other devices on the network have normal Internet access. Power-cycling the adapter resolves it.

It appears that the log I showed gets generated on every reboot, so a red herring. Here is log just after a reboot (this is after bonjour was disabled):

Dec  1 16:44:51 SPA112 kern.err [17179569.420000] physmap-flash physmap-flash.0: map_probe failed
Dec  1 16:44:51 SPA112 kern.err [17179571.088000] ksz8873 0-005f: failed with status -1
Dec  1 16:44:51 SPA112 kern.err [17179580.072000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Dec  1 16:44:53 SPA112 daemon.err dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory
Dec  1 16:45:12 SPA112 kern.err [17179604.284000]  Created coma thread for processing coma control message
Dec  1 16:45:22 SPA112 kern.err [17179614.912000] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Dec  1 16:45:26 SPA112 daemon.err system[1]: notify add wan1 interface(br0)
Dec  1 16:45:26 SPA112 daemon.err system[1]: start 0 vlan-id... ok
Dec  1 16:45:26 SPA112 daemon.err dnsmasq[147]: failed to load names from /etc/hosts: No such file or directory

[Dan Lukes]

There's nothing uncommon or suspicious on the log you disclosed.

No incoming calls can go through.

Still not so much detrails.  "No call can go trough" may mean the SPA112 is unreachable in the terms of IP connectivity, or it may have IP working, but Voice application doesn't respond incomming SIP requests, or it responds requests, but refuse to accept the call ...

Capture SIP packets flowing between SPA and upstream SIP proxy. Consider ask a skilled local network administrator for help.

[peter.thomas]

Hi Dan,

Sorry to open a year old issue however we are seeing the same in syslog and it sounds like the same experience. Whenever the ATA device receives a call/fax it loses registration to the SIP provider and is unresponsive until a reboot takes place.

I can confirm the version of firmware being used is 1.41

User-Agent: Cisco/SPA112-1.4.1(002)

I will see if I can get you a packet capture between us and the ITSP.
I have a good working relationship with them and will be able to get any information you think will be helpful in regards to getting this device working again.

I have tried a factory reset a number of times.
This device has worked in the past.


Yours,

Peter Thomas

[Dan Lukes]

Same issue => same advice. We need logs to analyze. Even if you are unable to capture SPA112,->ITSP packets, capture syslog&debug at least. A mean syslog of voice application running on SPA112, not the kernel log of SPA112. Follow Debug and syslog Messages from SPA1x2 and SPA232D ATA

But you should create new thread for it - this thread has been originally dedicated to no issue.