Re: Novatel Wireless power cycle
I've obtained it directly from a software engineer at Novatel named Ali Taheri, also included on the email was Charles Wang. I was never asked to sign anything. The SDK is closed source (distributed as a shared object) but can be easily captured using strace. I can definitely get you the sequence for power on as well, I just hadn't bothered yet. On Thu, Oct 11, 2012 at 5:23 PM, Dan Williams wrote: > > On Thu, 2012-10-11 at 16:20 -0500, Dan Williams wrote: > > On Thu, 2012-10-11 at 08:45 -0400, David Pfeffer wrote: > > > Hi all, > > > > > > > > > I noticed in the modemmanager Novatel plugin code there's nothing > > > there to power cycle the modem on disable/enable. This is a problem > > > for me since I've found that one modem in particular, the MC760, it'll > > > sometimes get into this state where the radio always tells the modem > > > there's No Carrier until you power cycle it. > > > > > > > > > I don't know about the GSM devices, but I've been developing for a > > > little while now with the CDMA devices. There's definitely a way to do > > > it. Using strace and the NovaCore SDK (which I have obtained from > > > Novatel's software development department and without signing an NDA), > > > I've found that the following goes out over the QCDM port when you > > > turn the radio off in the SDK: > > > > > > > > > write(4, "K\17\0\0\273`~", 7) = 7 > > > write(4, "K\372\7\0\7\377\377\0\0\344o~", 12) = 12 > > > write(4, "K\17\0\0\273`~", 7) = 7 > > > write(4, ")\1\0001@~", 6) = 6 > > > write(4, "K\17\0\0\273`~", 7) = 7 > > > write(4, "K\17\0\0\273`~", 7) = 7 > > > > They break down like this: > > > > K = DIAG_CMD_SUBSYS > > \17 (decimal 15) = DIAG_SUBSYS_CM (call manager) > > \0\0 = DIAG_SUBSYS_CM_STATE_INFO > > > > K = DIAG_CMD_SUBSYS > > \372 (decimal 250) = DIAG_SUBSYS_RESERVED_OEM_0 > > \7\0 (0x7) = DIAG_SUBSYS_NW_CONTROL_MODEM_SNAPSHOT > > \7 = DIAG_SUBSYS_NW_CONTROL_MODEM_SNAPSHOT_TECH_CDMA_EVDO > > \377\377\0\0 = snapshot mask > > > > ) = DIAG_CMD_CONTROL > > \1 = DM_CONTROL_MODE_OFFLINE > > Forgot to mention the last 3 bytes in all of these are the CRC-16 and > 0x7E. The DM/DIAG packet format is <0x7E>. And > of course everything before the 0x7E is HDLC encoded so that 0x7E never > appears in the body, and thus you can use it as the frame marker. > > Dan > > > So basically it's querying the generic modem state using the Call > > Manager subsystem (see DMCmdSubsysCMStateInfoRsp in libqcdm), and then > > it's asking for the Novatel-specific subsystem state (see > > DMCmdSubsysNwSnapshotRsp and DMCmdSubsysNwSnapshotCdma in libqcdm) and > > then it's telling the modem to go offline. I'll assume at some point it > > tells the modem to go back online too :) > > > > > However, I have no idea what this means -- I can't find any > > > documentation to speak of for QCDM so its just opaque binary to me. > > > > Because there isn't unless you sign NDAs with Qualcomm, and then you > > can't do anything open-source with it. So we've basically reverse > > engineered some stuff we need for ModemManager: > > > > http://cgit.freedesktop.org/ModemManager/ModemManager/tree/libqcdm > > > > and perhaps more specifically: > > > > http://cgit.freedesktop.org/ModemManager/ModemManager/tree/libqcdm/src/dm-commands.h > > > > The actual C API that clients of libqcdm should use is commands.h > > though, since the rest of the stuff is pretty low-level and the > > internals might change around if we discover something new later, which > > is why the commands.h uses the QcdmResult structure instead of hardcoded > > returned parameters. > > > > > If someone is willing to assist me with the QCDM portion or give me > > > some pointers, I'd be happy to reverse engineer power off, power on, > > > and reset, and contribute a patch back. Again this is just for CDMA > > > -- > > > > The CONTROL command works for both GSM and CDMA devices actually. I'm > > just missing the define for "online" so if you can capture that, that > > would be great. I'm pretty sure it'll be something like: > > > > write(4, ")\0\0001@~", 6) or write(4, ")\3\0001@~", 6) > > > > there are a bunch of modes though, but
Where's the bug tracker?
Where's the bug tracker for modem manager? I've discovered that on all of the CDMA devices I've tried, sending the D-Bus Activate method results in modem-manager dieing with a segfault. Thanks, David ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Novatel Wireless power cycle
Hi all, I noticed in the modemmanager Novatel plugin code there's nothing there to power cycle the modem on disable/enable. This is a problem for me since I've found that one modem in particular, the MC760, it'll sometimes get into this state where the radio always tells the modem there's No Carrier until you power cycle it. I don't know about the GSM devices, but I've been developing for a little while now with the CDMA devices. There's definitely a way to do it. Using strace and the NovaCore SDK (which I have obtained from Novatel's software development department and without signing an NDA), I've found that the following goes out over the QCDM port when you turn the radio off in the SDK: write(4, "K\17\0\0\273`~", 7) = 7 write(4, "K\372\7\0\7\377\377\0\0\344o~", 12) = 12 write(4, "K\17\0\0\273`~", 7) = 7 write(4, ")\1\0001@~", 6) = 6 write(4, "K\17\0\0\273`~", 7) = 7 write(4, "K\17\0\0\273`~", 7) = 7 However, I have no idea what this means -- I can't find any documentation to speak of for QCDM so its just opaque binary to me. If someone is willing to assist me with the QCDM portion or give me some pointers, I'd be happy to reverse engineer power off, power on, and reset, and contribute a patch back. Again this is just for CDMA -- the NovaCore SDK *does* support GSM devices but I don't own one. If someone else has one, I can send you the NovaCore SDK to reverse engineer this for GSM modems. Thanks, David ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Persistent 3G connection fails, not sure why
How do we get some attention to this patch and get it applied to the main source? This is a *major* issue for anyone running a persistent 3G connection. As a workaround, is there a way to unmark as invalid after nm decides to mark as invalid, other than disconnecting and reconnecting the device? On Thu, Oct 27, 2011 at 10:56 AM, wrote: > Hi, > > I also have some problems with persistent network connections and adapted > the patch below (you should find the mail in August or September list > archive), but it's solves only a part of my problems, also it makes things > much better, I have still problems from time to time, where I need to > disable and reenable the mobile broadband to get the modem reseted and > didn't found a solution so far... > > Gerald > > > > -Original Message- > > From: alexan...@karlstad.be [mailto:networkmanager-list- > > boun...@gnome.org] On Behalf Of Alexander Karlstad > > Sent: Thursday, October 27, 2011 4:46 PM > > To: networkmanager-list@gnome.org > > Subject: Re: Persistent 3G connection fails, not sure why > > > > Den 27. okt. 2011 14:17, skrev David Pfeffer: > > > Actually, that patch seems to be exactly what's needed. Can this be > > > patched into the main codebase? > > > > > > https://launchpadlibrarian.net/75684426/nm-reconnect.patch > > > > > > I haven't tested it specifically but it solves the problem that seems > > > to be identical to mine. > > > I don't see where you see that they say it didn't work well for them. > > > It seems like everyone was happy with it. > > > > Yup. The people commenting on it seemed happy, but I emailed the guy > > directly and he didn't seem to enthusiastic about it now, but again, he > was > > using a USB modem and not a built-in Mini PCI-e device like mine. > > > > I personally tried applying the patch to the latest network-manager in > > Ubuntu a couple a days ago, but it never compiled. I'm guessing the code > has > > changed a bit since the patch was written. (I think it was the > NMDeviceType > > thing that didn't work.) > > > > If this actually is what it takes, then I hope someone is willing to have > a look > > at it and eventually push it upstream :-) > > > > -- > > Alexander Karlstad > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Persistent 3G connection fails, not sure why
This is a USB modem, model U760 (a Sprint-branded MC760 from Novatel
Wireless).
If this is a bug I'm happy to help resolve it, but I have no experience with
the network manager code-base.
On Thu, Oct 27, 2011 at 2:29 AM, Dan Williams wrote:
> On Mon, 2011-10-17 at 09:49 -0400, David Pfeffer wrote:
> > I maintain a persistent 3G connection on a remote device using network
> > manager. However, every so often, the link fails and then does not
> > restart itself. I managed to identify an occurrence of this in my
> > syslog, but honestly I'm not really sure what I'm looking at. It seems
> > that the machine thinks the device has been unplugged, but there's no
> > corresponding log entry for it actually being unplugged.
>
> ALmost seems like the modem crashed and reset itself. What kind of
> modem is this and what model?
>
> Dan
>
> > Would someone mind looking at the below syslog snip and guiding me in
> > the right direction?
> >
> > Oct 13 22:25:26 tracker pppd[1091]: LCP terminated by peer
> > Oct 13 22:25:26 tracker pppd[1091]: Connect time 206.7 minutes.
> > Oct 13 22:25:26 tracker pppd[1091]: Sent 203306 bytes, received
> 182777 bytes.
> > Oct 13 22:25:26 tracker pppd[1091]: Modem hangup
> > Oct 13 22:25:26 tracker pppd[1091]: Connection terminated.
> > Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1):
> device state change: 8 -> 9 (reason 13)
> > Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged
> Device found; state CONNECTED forced. (see
> http://bugs.launchpad.net/bugs/191889)
> > Oct 13 22:25:26 tracker NetworkManager[333]: Activation
> (ttyUSB1) failed.
> > Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1)
> closing serial port...
> > Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1):
> device state change: 9 -> 3 (reason 0)
> > Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1):
> deactivating device (reason: 0).
> > Oct 13 22:25:26 tracker kernel: [12441.840088] ata1.00: exception
> Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> > Oct 13 22:25:26 tracker kernel: [12441.846744] ata1.00: BMDMA
> stat 0x66
> > Oct 13 22:25:26 tracker kernel: [12441.850446] ata1.00: failed
> command: WRITE DMA
> > Oct 13 22:25:26 tracker kernel: [12441.855020] ata1.00: cmd
> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
> > Oct 13 22:25:26 tracker kernel: [12441.855024] res
> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
> > Oct 13 22:25:26 tracker kernel: [12441.870623] ata1.00: status: {
> DRDY ERR }
> > Oct 13 22:25:26 tracker kernel: [12441.874708] ata1.00: error: {
> ICRC ABRT }
> > Oct 13 22:25:26 tracker kernel: [12441.878820] ata1: soft
> resetting link
> > Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1)
> serial port closed
> > Oct 13 22:25:26 tracker modem-manager[337]: Modem
> /org/freedesktop/ModemManager/Modems/0: state changed (connected ->
> disconnecting)
> > Oct 13 22:25:26 tracker modem-manager[337]: Modem
> /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting ->
> connected)
> > Oct 13 22:25:26 tracker NetworkManager[333]: could not
> read ppp stats: No such device
> > Oct 13 22:25:26 tracker pppd[1091]: Exit.
> > Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged
> Device found; state CONNECTED forced. (see
> http://bugs.launchpad.net/bugs/191889)
> > Oct 13 22:25:26 tracker NetworkManager[333]:
> SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0,
> iface: ppp0)
> > Oct 13 22:25:26 tracker NetworkManager[333]: disconnect
> failed: (32) The serial port is not open.
> > Oct 13 22:25:27 tracker kernel: [12442.048218] ata1.00:
> configured for UDMA/100
> > Oct 13 22:25:27 tracker kernel: [12442.048241] ata1: EH complete
> > Oct 13 22:25:27 tracker kernel: [12442.050941] ata1.00: exception
> Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> > Oct 13 22:25:27 tracker kernel: [12442.057483] ata1.00: BMDMA
> stat 0x66
> > Oct 13 22:25:27 tracker kernel: [12442.061153] ata1.00: failed
> command: WRITE DMA
> > Oct 13 22:25:27 tracker kernel: [12442.065696] ata1.00: cmd
> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
> > Oct 13 22:25:27 tracker kernel: [12442.065699] res
> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
> > Oct 13 22:25:27 tracker kernel: [12442.081273] ata1.00
Re: Persistent 3G connection fails, not sure why
Actually, that patch seems to be exactly what's needed. Can this be patched into the main codebase? https://launchpadlibrarian.net/75684426/nm-reconnect.patch I haven't tested it specifically but it solves the problem that seems to be identical to mine. I don't see where you see that they say it didn't work well for them. It seems like everyone was happy with it. On Thu, Oct 27, 2011 at 3:36 AM, Alexander Karlstad wrote: > Den 27. okt. 2011 08:29, skrev Dan Williams: > > On Mon, 2011-10-17 at 09:49 -0400, David Pfeffer wrote: >> >>> I maintain a persistent 3G connection on a remote device using network >>> manager. However, every so often, the link fails and then does not >>> restart itself. I managed to identify an occurrence of this in my >>> syslog, but honestly I'm not really sure what I'm looking at. It seems >>> that the machine thinks the device has been unplugged, but there's no >>> corresponding log entry for it actually being unplugged. >>> >> >> ALmost seems like the modem crashed and reset itself. What kind of >> modem is this and what model? >> > > I'm having a similar issue on my Thinkpad Edge 13 with the built in Gobi > 2000 WWAN module. Though, my "connection terminated" happens after the > "modem hangup", and it seems to happen very sudden according to the > syslog[1] (last entry in the log was several minutes earlier). > > I found a bug report[2] a while back that /could/ be related but I joined > this list in search for answers. Another bug report[3] contains a possible > patch, but according to the person submitting it, it didn't really work that > well: > > I found afterwards that the patch fixed only >> partially the problem. I saved a log message " disconnect >> failed: (32) The serial port is not open." that eventually happened, >> hoping to further research about the issue later. However, I didn't >> immediately found a way to reproduce the bug in a controlled >> environment. What I was doing for testing the patch before was to kill >> pppd, trying to simulate a modem hangup, but it didn't appear to >> simulate this other condition I was observing. After that I nearly >> stopped using USB modems as I bought an Android mobile phone capable >> of tethering. >> > > Hoping someone could help because I'm getting pretty sick of it. > > [1]: http://pastebin.ubuntu.com/**720446/<http://pastebin.ubuntu.com/720446/> > [2]: > https://bugs.launchpad.net/**ubuntu/+source/linux/+bug/**789508<https://bugs.launchpad.net/ubuntu/+source/linux/+bug/789508> > [3]: https://bugs.launchpad.net/**ubuntu/+source/network-** > manager/+bug/566812<https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/566812> > > -- > Alexander Karlstad > launchpad.net/~carestad <http://launchpad.net/%7Ecarestad> > > __**_ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/**listinfo/networkmanager-list<http://mail.gnome.org/mailman/listinfo/networkmanager-list> > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Persistent 3G connection fails, not sure why
(This thought was furthered by the fact that the USB modem in question is
one that modeswitches, so it does have internal storage. Am I wrong in this
assumption?)
On Thu, Oct 20, 2011 at 8:54 AM, David Pfeffer
wrote:
> The hard disk complaint actually only occurs at the same time as a network
> drop. I assumed they were somehow related to the 3G issue, because this
> occurs on several machines, each with identical hardware and disk image.
>
>
> On Thu, Oct 20, 2011 at 8:53 AM, Andrew Bird (Sphere Systems) <
> a...@spheresystems.co.uk> wrote:
>
>> Hi David,
>>I'd be looking at why the hard disk is complaining first, the
>> connection
>> problem may be an unlikely consequence of failing hardware.
>>
>> Best regards,
>>
>>
>> Andrew
>>
>> On Thursday 20 October 2011, David Pfeffer wrote:
>> > >> Oct 13 22:25:26 tracker kernel: [12441.840088] ata1.00: exception
>> Emask
>> > >> 0x0 SAct 0x0 SErr 0x0 action 0x6 Oct 13 22:25:26 tracker kernel:
>> > >> [12441.846744] ata1.00: BMDMA stat 0x66 Oct 13 22:25:26 tracker
>> kernel:
>> > >> [12441.850446] ata1.00: failed command: WRITE DMA Oct 13 22:25:26
>> > >> tracker kernel: [12441.855020] ata1.00: cmd
>> > >> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out Oct 13
>> 22:25:26
>> > >> tracker kernel: [12441.855024] res
>> > >> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error) Oct
>> 13
>> > >> 22:25:26 tracker kernel: [12441.870623] ata1.00: status: { DRDY ERR }
>> > >> Oct 13 22:25:26 tracker kernel: [12441.874708] ata1.00: error: { ICRC
>> > >> ABRT } Oct 13 22:25:26 tracker kernel: [12441.878820] ata1: soft
>> > >> resetting link
>>
>>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Persistent 3G connection fails, not sure why
The hard disk complaint actually only occurs at the same time as a network
drop. I assumed they were somehow related to the 3G issue, because this
occurs on several machines, each with identical hardware and disk image.
On Thu, Oct 20, 2011 at 8:53 AM, Andrew Bird (Sphere Systems) <
a...@spheresystems.co.uk> wrote:
> Hi David,
>I'd be looking at why the hard disk is complaining first, the
> connection
> problem may be an unlikely consequence of failing hardware.
>
> Best regards,
>
>
> Andrew
>
> On Thursday 20 October 2011, David Pfeffer wrote:
> > >> Oct 13 22:25:26 tracker kernel: [12441.840088] ata1.00: exception
> Emask
> > >> 0x0 SAct 0x0 SErr 0x0 action 0x6 Oct 13 22:25:26 tracker kernel:
> > >> [12441.846744] ata1.00: BMDMA stat 0x66 Oct 13 22:25:26 tracker
> kernel:
> > >> [12441.850446] ata1.00: failed command: WRITE DMA Oct 13 22:25:26
> > >> tracker kernel: [12441.855020] ata1.00: cmd
> > >> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out Oct 13 22:25:26
> > >> tracker kernel: [12441.855024] res
> > >> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error) Oct 13
> > >> 22:25:26 tracker kernel: [12441.870623] ata1.00: status: { DRDY ERR }
> > >> Oct 13 22:25:26 tracker kernel: [12441.874708] ata1.00: error: { ICRC
> > >> ABRT } Oct 13 22:25:26 tracker kernel: [12441.878820] ata1: soft
> > >> resetting link
>
>
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Persistent 3G connection fails, not sure why
Hi all,
I sent this below email a few days ago but it doesn't seem to have made it
to the list.
Would someone kindly be able to offer me some guidance? This is a pretty
critical bug for me as a client of mine has been suffering from intermittent
internet issues for about a week now.
Thanks.
On Mon, Oct 17, 2011 at 9:49 AM, David Pfeffer
wrote:
> I maintain a persistent 3G connection on a remote device using network
> manager. However, every so often, the link fails and then does not restart
> itself. I managed to identify an occurrence of this in my syslog, but
> honestly I'm not really sure what I'm looking at. It seems that the machine
> thinks the device has been unplugged, but there's no corresponding log entry
> for it actually being unplugged.
>
> Would someone mind looking at the below syslog snip and guiding me in the
> right direction?
>
>> Oct 13 22:25:26 tracker pppd[1091]: LCP terminated by peer
>> Oct 13 22:25:26 tracker pppd[1091]: Connect time 206.7 minutes.
>> Oct 13 22:25:26 tracker pppd[1091]: Sent 203306 bytes, received 182777 bytes.
>> Oct 13 22:25:26 tracker pppd[1091]: Modem hangup
>> Oct 13 22:25:26 tracker pppd[1091]: Connection terminated.
>> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): device state
>> change: 8 -> 9 (reason 13)
>> Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged Device found;
>> state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
>> Oct 13 22:25:26 tracker NetworkManager[333]: Activation (ttyUSB1)
>> failed.
>> Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1) closing serial
>> port...
>> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): device state
>> change: 9 -> 3 (reason 0)
>> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): deactivating
>> device (reason: 0).
>> Oct 13 22:25:26 tracker kernel: [12441.840088] ata1.00: exception Emask 0x0
>> SAct 0x0 SErr 0x0 action 0x6
>> Oct 13 22:25:26 tracker kernel: [12441.846744] ata1.00: BMDMA stat 0x66
>> Oct 13 22:25:26 tracker kernel: [12441.850446] ata1.00: failed command:
>> WRITE DMA
>> Oct 13 22:25:26 tracker kernel: [12441.855020] ata1.00: cmd
>> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
>> Oct 13 22:25:26 tracker kernel: [12441.855024] res
>> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
>> Oct 13 22:25:26 tracker kernel: [12441.870623] ata1.00: status: { DRDY ERR }
>> Oct 13 22:25:26 tracker kernel: [12441.874708] ata1.00: error: { ICRC ABRT }
>> Oct 13 22:25:26 tracker kernel: [12441.878820] ata1: soft resetting link
>> Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1) serial port
>> closed
>> Oct 13 22:25:26 tracker modem-manager[337]: Modem
>> /org/freedesktop/ModemManager/Modems/0: state changed (connected ->
>> disconnecting)
>> Oct 13 22:25:26 tracker modem-manager[337]: Modem
>> /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting ->
>> connected)
>> Oct 13 22:25:26 tracker NetworkManager[333]: could not read ppp
>> stats: No such device
>> Oct 13 22:25:26 tracker pppd[1091]: Exit.
>> Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged Device found;
>> state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
>> Oct 13 22:25:26 tracker NetworkManager[333]:SCPlugin-Ifupdown: devices
>> removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
>> Oct 13 22:25:26 tracker NetworkManager[333]: disconnect failed: (32)
>> The serial port is not open.
>> Oct 13 22:25:27 tracker kernel: [12442.048218] ata1.00: configured for
>> UDMA/100
>> Oct 13 22:25:27 tracker kernel: [12442.048241] ata1: EH complete
>> Oct 13 22:25:27 tracker kernel: [12442.050941] ata1.00: exception Emask 0x0
>> SAct 0x0 SErr 0x0 action 0x6
>> Oct 13 22:25:27 tracker kernel: [12442.057483] ata1.00: BMDMA stat 0x66
>> Oct 13 22:25:27 tracker kernel: [12442.061153] ata1.00: failed command:
>> WRITE DMA
>> Oct 13 22:25:27 tracker kernel: [12442.065696] ata1.00: cmd
>> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
>> Oct 13 22:25:27 tracker kernel: [12442.065699] res
>> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
>> Oct 13 22:25:27 tracker kernel: [12442.081273] ata1.00: status: { DRDY ERR }
>> Oct 13 22:25:27 tracker kernel: [12442.085366] ata1.00: error: { ICRC ABRT }
>> Oct 13 22:25:27 tracker kernel: [12442.089488] ata1: soft resetting link
>> Oct 13 22:25:27 tracker kernel: [12442.260206] ata1.00: configured for
>> UDMA/100
>> Oct 13 22:25:27 tracker kernel: [12442.260226] ata1: EH complete
Persistent 3G connection fails, not sure why
I maintain a persistent 3G connection on a remote device using network
manager. However, every so often, the link fails and then does not restart
itself. I managed to identify an occurrence of this in my syslog, but
honestly I'm not really sure what I'm looking at. It seems that the machine
thinks the device has been unplugged, but there's no corresponding log entry
for it actually being unplugged.
Would someone mind looking at the below syslog snip and guiding me in the
right direction?
> Oct 13 22:25:26 tracker pppd[1091]: LCP terminated by peer
> Oct 13 22:25:26 tracker pppd[1091]: Connect time 206.7 minutes.
> Oct 13 22:25:26 tracker pppd[1091]: Sent 203306 bytes, received 182777 bytes.
> Oct 13 22:25:26 tracker pppd[1091]: Modem hangup
> Oct 13 22:25:26 tracker pppd[1091]: Connection terminated.
> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): device state
> change: 8 -> 9 (reason 13)
> Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged Device found;
> state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
> Oct 13 22:25:26 tracker NetworkManager[333]: Activation (ttyUSB1)
> failed.
> Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1) closing serial
> port...
> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): device state
> change: 9 -> 3 (reason 0)
> Oct 13 22:25:26 tracker NetworkManager[333]: (ttyUSB1): deactivating
> device (reason: 0).
> Oct 13 22:25:26 tracker kernel: [12441.840088] ata1.00: exception Emask 0x0
> SAct 0x0 SErr 0x0 action 0x6
> Oct 13 22:25:26 tracker kernel: [12441.846744] ata1.00: BMDMA stat 0x66
> Oct 13 22:25:26 tracker kernel: [12441.850446] ata1.00: failed command: WRITE
> DMA
> Oct 13 22:25:26 tracker kernel: [12441.855020] ata1.00: cmd
> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
> Oct 13 22:25:26 tracker kernel: [12441.855024] res
> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
> Oct 13 22:25:26 tracker kernel: [12441.870623] ata1.00: status: { DRDY ERR }
> Oct 13 22:25:26 tracker kernel: [12441.874708] ata1.00: error: { ICRC ABRT }
> Oct 13 22:25:26 tracker kernel: [12441.878820] ata1: soft resetting link
> Oct 13 22:25:26 tracker modem-manager[337]: (ttyUSB1) serial port
> closed
> Oct 13 22:25:26 tracker modem-manager[337]: Modem
> /org/freedesktop/ModemManager/Modems/0: state changed (connected ->
> disconnecting)
> Oct 13 22:25:26 tracker modem-manager[337]: Modem
> /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting ->
> connected)
> Oct 13 22:25:26 tracker NetworkManager[333]: could not read ppp stats:
> No such device
> Oct 13 22:25:26 tracker pppd[1091]: Exit.
> Oct 13 22:25:26 tracker NetworkManager[333]: Unmanaged Device found;
> state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
> Oct 13 22:25:26 tracker NetworkManager[333]:SCPlugin-Ifupdown: devices
> removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
> Oct 13 22:25:26 tracker NetworkManager[333]: disconnect failed: (32)
> The serial port is not open.
> Oct 13 22:25:27 tracker kernel: [12442.048218] ata1.00: configured for
> UDMA/100
> Oct 13 22:25:27 tracker kernel: [12442.048241] ata1: EH complete
> Oct 13 22:25:27 tracker kernel: [12442.050941] ata1.00: exception Emask 0x0
> SAct 0x0 SErr 0x0 action 0x6
> Oct 13 22:25:27 tracker kernel: [12442.057483] ata1.00: BMDMA stat 0x66
> Oct 13 22:25:27 tracker kernel: [12442.061153] ata1.00: failed command: WRITE
> DMA
> Oct 13 22:25:27 tracker kernel: [12442.065696] ata1.00: cmd
> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
> Oct 13 22:25:27 tracker kernel: [12442.065699] res
> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
> Oct 13 22:25:27 tracker kernel: [12442.081273] ata1.00: status: { DRDY ERR }
> Oct 13 22:25:27 tracker kernel: [12442.085366] ata1.00: error: { ICRC ABRT }
> Oct 13 22:25:27 tracker kernel: [12442.089488] ata1: soft resetting link
> Oct 13 22:25:27 tracker kernel: [12442.260206] ata1.00: configured for
> UDMA/100
> Oct 13 22:25:27 tracker kernel: [12442.260226] ata1: EH complete
> Oct 13 22:25:27 tracker kernel: [12442.268296] ata1.00: exception Emask 0x0
> SAct 0x0 SErr 0x0 action 0x6
> Oct 13 22:25:27 tracker kernel: [12442.274829] ata1.00: BMDMA stat 0x66
> Oct 13 22:25:27 tracker kernel: [12442.278480] ata1.00: failed command: WRITE
> DMA
> Oct 13 22:25:27 tracker kernel: [12442.283022] ata1.00: cmd
> ca/00:02:c4:fb:5b/00:00:00:00:00/e0 tag 0 dma 1024 out
> Oct 13 22:25:27 tracker kernel: [12442.283026] res
> 51/84:00:c4:fb:5b/00:00:00:00:00/e0 Emask 0x30 (host bus error)
> Oct 13 22:25:27 tracker kernel: [12442.298605] ata1.00: status: { DRDY ERR }
> Oct 13 22:25:27 tracker kernel: [12442.302693] ata1.00: error: { ICRC ABRT }
> Oct 13 22:25:27 tracker kernel: [12442.306763] ata1: soft resetting link
> Oct 13 22:25:27 tracker kernel: [12442.476225] ata1.00: configured for
> UDMA/100
> Oct 13 22:25:27 tracker kernel: [12442.476
