dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
17

Phibian
join:2009-06-01
Ottawa, ON

Phibian to JenSuisUn

Member

to JenSuisUn

Re: [DSL] Cellpipe random reboots / loss of sync (Check logs ple

Hi Martin,

Yes the modem reboots without any RJ11 connected.

My test case is:
Open shipping box from Bell.
Remove modem from box.
Plug in one ethernet cable to a PC (only used to access web GUI on modem - no other traffic).
Plug in power and turn on modem.
Connect to web GUI and clear the system log.
Wait 30 hours (Pattern is a reboot sometime between 5 minutes and 30 hours).
Connect to web GUI and view log - note that there are now entries in the log showing that it went through a boot cycle.
Repeat as desired.

No changes are made to the modem other than clearing the log.
No RJ11 cable is plugged in.
No traffic from PC other than to view web GUI on modem.
Every single one of the modems I've had (about 10 of them now) have exhibited this behaviour.

I would be happy to discuss with Bell/whomever.
They can come and see the logs here.
They can have my modem (I currently have one extra that I haven't sent back yet).
I am happy to help them reproduce the issue in whatever way they want.

The only reason the remote is being mentioned is because the firmware in question is what you get if you are on that remote (as opposed to the other IKNS stinger remote where you get the same cellpipe modem but with different firmware that seems to actually works - but of course only with that remote not the one we are on).
abcxyz123
join:2012-01-17
k2k0h2

abcxyz123

Member

Is there anyway they can get Phibian a modem loaded with the same version of the firmware the Bell contractor gave to me to see if it resolves his issue? I have not had the issue since Jan 9th when I got the swap out.

Rather than going through the shipping department process again, send the tech with the 1.0.4.3EF-ISAM firmware. He said that is the firmware on the modems that they give to the Bell customers, and it is the one they send to the contractors.

Model 1.0.4.3EF-ISAM
It has the 7330 remote sticker on it.
Loaded with 1.0.4.3EF-ISAM firmware.

JenSuisUn
Premium Member
join:2006-02-23
Chatham, ON

JenSuisUn

Premium Member

I've sent my Bell contact that request. Maybe we can... we'll have to see what he says.
Bhruic
join:2002-11-27
Toronto, ON

Bhruic to Phibian

Member

to Phibian
said by Phibian:

Wait 30 hours (Pattern is a reboot sometime between 5 minutes and 30 hours).

I'm wondering about that pattern you mentioned before - while I've had 3-4 reboots in a single day, currently I've got:

Connection Uptime 3 days, 09:21:41

So mine, at least, seems capable of going well over 30 hours without a reboot. Well, unless it's spontaneously fixed itself (I checked, the firmware hasn't changed).
swiftex
join:2008-05-10
Toronto, ON

swiftex

Member

You had issues with v1.0.4.4R3WH also?

lleader
join:2011-01-01
Mississauga, ON

1 edit

lleader

Member

said by swiftex:

You had issues with v1.0.4.4R3WH also?


From CellPipe:

v1.0.4.4R3WH
2011/09/16 12:00

From router (just relevant lines):

Jan 27 02:05:03 unknown daemon.info pppd[24482]: No response to 5 echo-requests
Jan 27 02:05:03 unknown daemon.notice pppd[24482]: Serial link appears to be disconnected.
Jan 27 02:05:03 unknown daemon.info pppd[24482]: Connect time 1520.6 minutes.
---------------------------------------------------------------------------------- ---------
Jan 27 06:32:36 unknown daemon.info pppd[26443]: Connect time 252.6 minutes.
---------------------------------------------------------------------------------- ---------
Jan 27 19:12:01 unknown daemon.info pppd[26937]: Connect time 758.2 minutes.
---------------------------------------------------------------------------------- ---------
Jan 31 04:37:57 unknown daemon.info pppd[27530]: Connect time 4885.1 minutes.
---------------------------------------------------------------------------------- ---------
Feb 1 00:34:35 unknown daemon.info pppd[28453]: Connect time 1195.7 minutes.
---------------------------------------------------------------------------------- ---------
Feb 1 16:02:19 unknown daemon.info pppd[28965]: Connect time 926.8 minutes.
---------------------------------------------------------------------------------- ---------
Feb 1 16:39:17 unknown daemon.info pppd[29526]: Connect time 36.1 minutes.
---------------------------------------------------------------------------------- ---------
Feb 2 03:10:07 unknown daemon.info pppd[30007]: Connect time 629.3 minutes.
---------------------------------------------------------------------------------- ---------
Feb 3 11:48:41 unknown daemon.info pppd[30546]: Connect time 1957.3 minutes.
---------------------------------------------------------------------------------- ---------
Feb 4 15:42:43 unknown daemon.info pppd[31260]: Connect time 1672.6 minutes.
---------------------------------------------------------------------------------- ---------
Feb 6 11:20:22 unknown daemon.info pppd[31900]: Connect time 2616.2 minutes.
---------------------------------------------------------------------------------- ---------
Feb 8 05:48:20 unknown daemon.info pppd[32600]: Connect time 2546.6 minutes.
---------------------------------------------------------------------------------- ---------
Feb 10 14:49:43 unknown daemon.info pppd[816]: Connect time 3419.9 minutes.
---------------------------------------------------------------------------------- ---------
Feb 10 16:16:58 unknown daemon.info pppd[1596]: Connect time 86.3 minutes.
---------------------------------------------------------------------------------- ---------
Feb 11 07:11:17 unknown daemon.info pppd[2087]: Connect time 892.9 minutes.
---------------------------------------------------------------------------------- ---------
Feb 11 14:51:17 unknown daemon.info pppd[2643]: Connect time 458.7 minutes.
---------------------------------------------------------------------------------- ---------
Feb 12 12:21:38 unknown daemon.info pppd[3097]: Connect time 1289.7 minutes.
---------------------------------------------------------------------------------- ---------
Feb 12 12:58:57 unknown daemon.info pppd[3716]: Connect time 35.7 minutes.
---------------------------------------------------------------------------------- ---------
Feb 13 10:23:07 unknown daemon.info pppd[4175]: Connect time 1283.0 minutes.
---------------------------------------------------------------------------------- ---------
Feb 15 14:11:08 unknown daemon.info pppd[7347]: Connect time 2193.9 minutes.
---------------------------------------------------------------------------------- ---------
Feb 15 14:40:17 unknown daemon.info pppd[8101]: Connect time 27.9 minutes.
---------------------------------------------------------------------------------- ---------
Feb 15 21:55:53 unknown daemon.info pppd[8517]: Connect time 434.8 minutes.
---------------------------------------------------------------------------------- ---------
Feb 16 20:12:14 unknown daemon.info pppd[9056]: Connect time 1334.9 minutes.
---------------------------------------------------------------------------------- ---------
Feb 17 12:22:04 unknown daemon.info pppd[9656]: Connect time 968.3 minutes.
---------------------------------------------------------------------------------- ---------
Feb 18 20:47:52 unknown daemon.info pppd[10209]: Connect time 1944.3 minutes.
---------------------------------------------------------------------------------- ---------
Feb 18 23:44:18 unknown daemon.info pppd[11847]: Connect time 83.0 minutes.
---------------------------------------------------------------------------------- ---------
Feb 19 12:08:37 unknown daemon.info pppd[12335]: Connect time 742.8 minutes.
---------------------------------------------------------------------------------- ---------

Longest connect was 81 hours, shortest was 28 minutes.

Phibian
join:2009-06-01
Ottawa, ON

Phibian

Member

The 5 minutes to 30 hours thing is not exact by any means. It jus represents a rough average. Three days is a long time to go without a reboot but it seems so random that I guess it is not impossible. Maybe it is saving them up

I've got pingdom recording things so I guess that by now I might have enough data to be statistically sound. I should take a look...
Bhruic
join:2002-11-27
Toronto, ON

Bhruic

Member

said by Phibian:

The 5 minutes to 30 hours thing is not exact by any means. It jus represents a rough average. Three days is a long time to go without a reboot but it seems so random that I guess it is not impossible. Maybe it is saving them up

Well, I made it to just over 4 days. Did I win anything?

Phibian
join:2009-06-01
Ottawa, ON

Phibian

Member

Well you beat me.

I ran some numbers and this is what I've got for February (for one of the modems).

In 19 days I've got 28 reboots (1.47 reboots per day).

Shortest uptime: 35.9 minutes
Longest uptime: 56 hours (2.3 days)
Average uptime: 15.8 hours

So in general we are looking at a reboot within 24 hours but there is certainly some variation.

Looking at the distribution over the day it seems to be pretty even. A very slight bias towards the morning but that could well be the limited data set.

In terms of frequency I'm seeing no discernible patterns. Sometimes there is a group of longer periods of uptime, sometimes there are groups of shorter periods but in general it seems to be pretty random.
Phibian

Phibian to Bhruic

Member

to Bhruic
Ok new record: 5.5 days before a reboot.
NLZ
join:2009-03-20
Hamilton, ON

NLZ

Member

Mine has been rebooting without it showing anything in the logs all of a sudden, strange.

HiVolt
Premium Member
join:2000-12-28
Toronto, ON

HiVolt

Premium Member

said by NLZ:

Mine has been rebooting without it showing anything in the logs all of a sudden, strange.

Haha, Bell fixed it so you can't track the reboots! LOL.
Pinworm45
join:2008-06-01
Ottawa, ON

Pinworm45

Member

said by HiVolt:

Haha, Bell fixed it so you can't track the reboots! LOL.

This honestly wouldn't surprise me in the slightest..

Still getting reboots.
swiftex
join:2008-05-10
Toronto, ON
Asus RT-AC66
SmartRG SR505N

swiftex to Phibian

Member

to Phibian
said by Phibian:

Ok new record: 5.5 days before a reboot.

You got a new modem? Details?

STINGER REMOTE CONNECTED

I've since switched out the following:

v1.0.4.4R3WH

REASON

1. Held a sync but web pages wouldn't load (a few instances for a period of 3 weeks),

2. Losing connection to the nic card,

3. Seemed like DNS resolving issues,

REMEDY

Popped in the other Cell-Pipe with the Stinger firmware,

Only 6 hours and no issues yet.

Phibian
join:2009-06-01
Ottawa, ON

Phibian

Member

The 5.5 days was the cellpipe. It was so long that I was starting to wonder if bell had remotely updated it. Then it rebooted. Just shows how random it is.
Ting Tong
join:2012-02-29

Ting Tong

Member

Still got a reboot today (Feb 29). Nothing has been fixed. Haven't heard a word back from TSI.

5 weeks of this internet purgatory now.
swiftex
join:2008-05-10
Toronto, ON

swiftex to Phibian

Member

to Phibian
You on a 7330 remote?

My understanding was the 7330 remotes were in Ottawa.
chex383
join:2003-03-13
Victoria, BC

chex383 to Phibian

Member

to Phibian
" Status Connected
Connection Uptime 3 days, 22:00 hrs "

Ive been up for almost 4 days now, this is a record for me.

-- Stefan in Montreal
said by Phibian:

The 5.5 days was the cellpipe. It was so long that I was starting to wonder if bell had remotely updated it. Then it rebooted. Just shows how random it is.

swiftex
join:2008-05-10
Toronto, ON
Asus RT-AC66
SmartRG SR505N

swiftex to Ting Tong

Member

to Ting Tong
said by Ting Tong:

Still got a reboot today (Feb 29). Nothing has been fixed. Haven't heard a word back from TSI.

5 weeks of this internet purgatory now.

Location?

Remote type?

Firmware version?
morisato
join:2008-03-16
Oshawa, ON

morisato

Member

Likewise i got a reboot this morning in oshawa on a 7330 with the affected f/w

Phibian
join:2009-06-01
Ottawa, ON

Phibian to swiftex

Member

to swiftex
Yup I'm on a 7330 and I am in Ottawa.

The reboots probably follow some complex formula involving the phase of the moon and Bell's current profit multiplied by the number of times the CRTC has said something absurd in the last six months divided by the time since TSI last told us something plus a pseudo random number seeded with your current monthly bill.
morisato
join:2008-03-16
Oshawa, ON

morisato

Member

Well when i was interviewing Yesterday with BTS the Director of Recruitment for Ontario when i mentioned the 7330 remote said they were still trialing them and That the cabinets were climate controlled and they had Issues with 7330 power problems also was surprised anyone got a cell-pipe as it was a Nightmare modem. In his words P:), then he said On your with Teksavvy well that makes sense we don;t care about third party's anyways
Ting Tong
join:2012-02-29

Ting Tong to swiftex

Member

to swiftex
Toronto
Cellpipe with v1.0.4.4R3WH
Dunno
NLZ
join:2009-03-20
Hamilton, ON

NLZ to swiftex

Member

to swiftex
What remote are the people that live in Toronto/Hamilton on?
chex383
join:2003-03-13
Victoria, BC

chex383

Member

" Status Connected
Connection Uptime 0 days, 00:00:53 "

Mine just rebooted, after being up for 4 days..

squircle
join:2009-06-23
OTWAON10

squircle to swiftex

Member

to swiftex
said by swiftex:

You on a 7330 remote?

My understanding was the 7330 remotes were in Ottawa.

There are 7330s elsewhere, too (like down the street from me here in Oakville).
EvoMaStA
join:2002-07-11
Stoney Creek, ON
Sagemcom F@st 5689
Plume Pod
Grandstream HT502

EvoMaStA to chex383

Member

to chex383
said by chex383:

" Status Connected
Connection Uptime 0 days, 00:00:53 "

Mine just rebooted, after being up for 4 days..

Mine also went down for about an hour after being up 4 days strait , Might have been some kind of hiccup in the pppoe login server, because my DSL light was on during the whole downtime.

Phibian
join:2009-06-01
Ottawa, ON

Phibian to squircle

Member

to squircle
I'm pretty sure from what I've read that all new rollouts of VDSL2 remotes are 7330s. Ottawa is pretty much all new (didn't really have much before end of 2011 since Bell was stalling on deploying in Ottawa for political reasons (or so I've heard). Toronto on the other hand had a much longer rollout period so they've got a mix with probably more Stingers than 7330s but that will shift as time goes on. I don't think that Bell is installing any more Stingers at this point.

squircle
join:2009-06-23
OTWAON10

squircle

Member

said by Phibian:

I'm pretty sure from what I've read that all new rollouts of VDSL2 remotes are 7330s. Ottawa is pretty much all new (didn't really have much before end of 2011 since Bell was stalling on deploying in Ottawa for political reasons (or so I've heard). Toronto on the other hand had a much longer rollout period so they've got a mix with probably more Stingers than 7330s but that will shift as time goes on. I don't think that Bell is installing any more Stingers at this point.

Yeah, you're probably right. There is only one 7330 around here, but it's on the other side of the JWI from a Stinger. I only wish I was connected to a 7330.

Phibian
join:2009-06-01
Ottawa, ON

Phibian

Member

Ah but then you would be stuck with the rebooting modem from BHell.