| Summary: | Franklin Wireless S600c Loses Connection After Indeterminate Period | ||
|---|---|---|---|
| Product: | ModemManager | Reporter: | exovaria |
| Component: | general | Assignee: | ModemManager bug user <modemmanager> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 1.6 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
ModemManager and syslog
54 hrs of logs |
||
The logs provided only show a connection that lasts ~40s. We would need to see debug logs during the whole period where it gets disconnected by the network, to see if we get any AT command indication reporting that issue. Created attachment 135570 [details]
54 hrs of logs
Okay, I ran ModemManager in debug for about 54 hours. The Pi never went into a low power mode as I had a screensaver running for this entire period. When I attempted to use the network before pulling the logs, there was no ppp0 connection in ifconfig. Attempting to ping a host resulted in destination host unreachable. Network Manager still showed the connection as active and still had an option to disconnect. Attempting to click the ttyACM0 connection again did not change the state of the connection. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/75. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 135476 [details] ModemManager and syslog Using a Franklin Wireless S600c Sprint EVDO modem on Raspbian Stretch running kernel 4.9.59-v7+. Modem was correctly detected by ModemManager after ModemManager/NetworkManager were installed to Raspbian. Modem correctly connects to Sprint network and has expected network performance. After an indeterminate period overnight, the modem claimed to be connected but was no longer sending or receiving data. Ping failed to resolve host, Chromium stated "internet disconnected". NetworkManager still showed RSSI bars and connected state. Restarting Raspberry Pi fixed issue after reboot. These modems will be used in an M2M application and it would be great if there was a way to determine why the modem went offline and did not recover. Attached are ModemManager log and syslog.