dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2951
share rss forum feed

baess

join:2011-01-28

DPC2100 new firmware

At 1:45 PM today my modem rebooted and new firmware was put on.

It is now dpc2100rx-v202r1256-120710Uas. Anyone else?

I hope this doesn't have the Watchdog Timer.

Set up page is now different too. Maybe Dan can comment, please.

Body Count

join:2010-09-11
Columbus, OH

clocks11

join:2002-05-06
00000
reply to baess
No update here, but maybe the DPX takes different firmware.

WebSTAR DPX2100
v2.0.1r1142-050302(dpx2100-v201r1142-050302a.bin)

baess

join:2011-01-28

2 edits
reply to Body Count
I'm aware. I had this firmware in August and alerted Dan to the fact that the watchdog timer was rebooting too often. He acknowledged a problem and moved me and a few others back to the -060303 and no more problems.

So in August WOW knew this firmware and it's watchdog timer was too sensitive.

baess

join:2011-01-28

2 edits
reply to baess
Well I've already had one reboot and the log says Watchdog Timer.

With the previous firmware my modem would go months with no reboots, no issues whatsoever.

WOW knew the watchdog timer was too sensitive and I thought they were going to fix it before releasing this firmware. To quote WOW_Dan from August:

We are investigating what to do with the watchdog timer. It gets triggered by your modem losing connectivity briefly, the modem will reboot to resolve the issue. This was a new feature of the DPC2100 firmware, and it doesn't seem to be working exactly as it should. I see yours rebooted once on 8/27 and once on 8/29, so it's not happening too often, but it is something we're already looking into.

Hoping Dan will comment.

slyphoxj

join:2002-06-23
Brook Park, OH
kudos:1
reply to baess
Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.

LWC

join:2006-08-24
Roseville, MI
said by slyphoxj:

Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.

Same here.
Whats all this mean?
Wed Oct 31 07:46:28 2012 Error (4) DCC-ACK not received
Wed Oct 31 06:55:00 2012 Notice (6) TLV-11 - unrecognized OID
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Oct 31 06:53:48 2012 Critical (3) Reset due to expiration of watchdog timer
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Oct 31 01:10:38 2012 Critical (3) Reset due to expiration of watchdog timer

baess

join:2011-01-28
said by LWC:

said by slyphoxj:

Yep, I got the new firmware again... AND the @#%$#in Watchdog Timer issue AGAIN.

Same here.
Whats all this mean?

Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Oct 31 06:53:48 2012 Critical (3) Reset due to expiration of watchdog timer
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Oct 31 01:10:38 2012 Critical (3) Reset due to expiration of watchdog timer

It means your modem is disconnecting and rebooting. The new firmware is causing it.

I wonder what benefits, if any, this new firmware has that made WOW want to roll it out when they knew their customers would have the rebooting problem?


unregwow

@wowway.com
reply to baess
Dan brought this to my attention. The timer has been removed from the configuration, in the event your modem should reset again, it should no longer have this option set.

baess

join:2011-01-28
said by unregwow :

Dan brought this to my attention. The timer has been removed from the configuration, in the event your modem should reset again, it should no longer have this option set.

No watchdog timers that I can tell since the first one. So not sure how the timer would have been removed but I'm at 2.5 days with no resets.

Thanks to you (oh unnamed WOW employee) and Dan .

cincy4852000

join:2004-10-29
I am on the same firmware and I have been having tremendous problems since the last 3-4 days. I dont know if its related to firmware or 'service problems'

I have been on hold for over 75 minutes now

Here is the log
Sat Nov 03 20:37:55 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Nov 03 20:14:07 2012 Notice (6) TLV-11 - unrecognized OID
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Nov 03 17:36:46 2012 Critical (3) DHCP FAILED - Requested Info not supported.
Sat Nov 03 17:36:30 2012 Critical (3) No Ranging Response received - T3 time-out
Sat Nov 03 17:36:17 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Nov 03 17:29:46 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Nov 03 11:28:52 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.
Time Not Established Critical (3) DHCP FAILED - Request sent, No response
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Nov 03 11:17:40 2012 Critical (3) TFTP failed - configuration file NOT FOUND

baess

join:2011-01-28
reply to baess
I did have another watchdog timer. Sure hope it is the last.

slyphoxj

join:2002-06-23
Brook Park, OH
kudos:1
reply to baess
I haven't gotten a watchdog timer expiration since Friday morning. My DPC2100 has been up over 3 days and 19 hours now.

.

LWC

join:2006-08-24
Roseville, MI
My last one was Saturday morning.
Still seeing this in the log though:
Tue Nov 06 01:29:30 2012 Error (4) DCC-ACK rejected unknown transaction ID
Tue Nov 06 01:29:28 2012 Error (4) DCC-ACK not received
Mon Nov 05 04:35:23 2012 Error (4) DCC-ACK rejected unknown transaction ID
Mon Nov 05 04:35:21 2012 Error (4) DCC-ACK not received
Sun Nov 04 18:29:39 2012 Error (4) DCC-ACK rejected unknown transaction ID
Sun Nov 04 18:29:37 2012 Error (4) DCC-ACK not received
Sun Nov 04 06:44:35 2012 Error (4) DCC-ACK rejected unknown transaction ID
Sun Nov 04 06:44:35 2012 Error (4) DCC-ACK not received
Sun Nov 04 02:30:14 2012 Error (4) DCC-ACK rejected unknown transaction ID
Sun Nov 04 02:30:12 2012 Error (4) DCC-ACK not received

baess

join:2011-01-28
said by LWC:

Still seeing this in the log though:
Tue Nov 06 01:29:30 2012 Error (4) DCC-ACK rejected unknown transaction ID
Tue Nov 06 01:29:28 2012 Error (4) DCC-ACK not received

Seeing the same.

Always got the DCC-ACK not received.

DCC-ACK rejected unknown transaction ID is new since yesterday for me.

Dan?

cincy4852000

join:2004-10-29
reply to cincy4852000
WOW technician came in and said my modem was bad. This is a modem I have owned and has been working for over 3-4 years.

He replaced it with another dpc2100 with firmware version that lower. It works now.

But I am not happy with WOW. While I dont disagree that electronic items can go bad, I dont think thats what happened here. I think this is a case of bad firmware causing the issue.