Opened 5 years ago

Last modified 4 years ago

#13341 new defect

OM2P random reboots - ATTITUDE ADJUSTMENT (12.09, r36088)

Reported by: warren@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Attitude Adjustment 12.09 Beta
Keywords: Cc:


hardware: OM2P / IC 3616C-OM2P
Using the latest factory .bin ATTITUDE ADJUSTMENT (12.09, r36088)
BusyBox v1.19.4 (2013-03-14 11:28:31 UTC) built-in shell (ash)

filename: openwrt-ar71xx-generic-om2p-squashfs-factory.bin

OM2P device reboots after (approximately) every 7 minutes. I can't grab logs just yet, but CPU loads are minimal and RAM usage is low just before the device reboots.

I have also tried flashing (Attitude Adjustment, r35947) and the rebooting is still occurring.

Wondering is this random rebooting happening other folk?


Attachments (0)

Change History (7)

comment:1 Changed 5 years ago by fon@…

I'm seeing this too.
@Warren - have you found a workaround?

comment:2 Changed 5 years ago by fon@…

It's still happening with the nightly build r36939, after clean install.

comment:3 Changed 4 years ago by angus

OM2P-HS has same trouble with build r36088.

Last edited 4 years ago by angus (previous) (diff)

comment:4 Changed 4 years ago by dirkvanderwalt@…

Hi Guys,

I experience the same as you. I did a build a few weeks back using the latest trunk then (r38994) and this one worked fine.

Yesterday I've created a build again with the latest trunk (r39185) and the rebooting is back :-(

So on my device it lasts JUST under 5 minutes, and is always consistent. It seems there is a precise timeout that is reached and then the device is rebooted.


comment:5 Changed 4 years ago by angus

Check r40465 out and thanks to juhosg!

Last edited 4 years ago by angus (previous) (diff)

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:7 Changed 4 years ago by cmonroe

It took me a bit to figure out, but the pattern was so consistent I knew it had to be some type of timer or watchdog firing. I was having the same issues described above using an OM2P unit. Turns out the barrier breaker branch does not include the om-watchdog tool in the default builds for some reason (it used to). Long story short the temporary fix is:

opkg update
opkg install om-watchdog
/etc/init.d/om-watchdog enable
/etc/init.d/om-watchdog boot

This is all easily doable within the 5-7min window after boot but ideally this package should be included by default. The above installs the dog keeper, adds a symlink to /etc/rc.d, then starts it immediately. Once started the device should not reboot again (mine has been active 2+ hrs as of now).

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.