Re: Persistent 3G connection fails, not sure why

2011-11-03 Thread Alexander Karlstad 

Den 31. okt. 2011 19:28, skrev Alexander Karlstad:

Den 28. okt. 2011 13:59, skrev David Pfeffer:

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.


Indeed. I hope someone is willing to have a look at it, if it's not
being done already. If 3G internet doesn't work very well with
network-manager in Linux, how is it going to compete with Windows and
Mac? :-(



Any takers? Anyone at all?

:-(

--
Alexander Karlstad
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Persistent 3G connection fails, not sure why

2011-10-31 Thread Alexander Karlstad 

Den 28. okt. 2011 13:59, skrev David Pfeffer:

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.


Indeed. I hope someone is willing to have a look at it, if it's not 
being done already. If 3G internet doesn't work very well with 
network-manager in Linux, how is it going to compete with Windows and 
Mac? :-(


--
Alexander Karlstad
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Persistent 3G connection fails, not sure why

2011-10-28 Thread David Pfeffer 
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

2011-10-27 Thread richter 
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

Re: Persistent 3G connection fails, not sure why

2011-10-27 Thread Alexander Karlstad 

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

Re: Persistent 3G connection fails, not sure why

2011-10-27 Thread David Pfeffer 
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: 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:

Re: Persistent 3G connection fails, not sure why

2011-10-27 Thread 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.

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/
> [2]: 
> https://bugs.launchpad.net/**ubuntu/+source/linux/+bug/**789508
> [3]: https://bugs.launchpad.net/**ubuntu/+source/network-**
> manager/+bug/566812
>
> --
> Alexander Karlstad
> launchpad.net/~carestad 
>
> __**_
> 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

2011-10-27 Thread Alexander Karlstad 

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/
[2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/789508
[3]: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/566812

--
Alexander Karlstad
launchpad.net/~carestad
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Persistent 3G connection fails, not sure why

2011-10-26 Thread 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?

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: 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: c

Re: Persistent 3G connection fails, not sure why

2011-10-20 Thread Andrew Bird (Sphere Systems) 
Hi David,
So is the harddisk device that complains the storage device on the 3G 
stick itself, or a different device altogether? If it's the same device I'd 
suspect that the 3G stick is resetting itself and momentarily disappearing 
from the system.


Best regards,


Andrew

On Thursday 20 October 2011, David Pfeffer wrote:
> (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

2011-10-20 Thread David Pfeffer 
(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

2011-10-20 Thread David Pfeffer 
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

2011-10-20 Thread Andrew Bird (Sphere Systems) 
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

2011-10-20 Thread David Pfeffer 
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
>> 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]

Persistent 3G connection fails, not sure why

2011-10-17 Thread David Pfeffer 
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