El 13/10/13 16:57, Bastian Bittorf escribió:
>>> the board is ok, no need for replacing it. we have several 1000
>>> boards,
>>> and we see that everyday some of them are hanging in this situation
>>> (right after nightly reboot). statistically that means:
>>>
>>> if you reboot a board ever night,
> > the board is ok, no need for replacing it. we have several 1000
> > boards,
> > and we see that everyday some of them are hanging in this situation
> > (right after nightly reboot). statistically that means:
> >
> > if you reboot a board ever night, than it will 'hang' once a year.
> > also rea
2013/10/13 Bastian Bittorf :
> * Sergey Ryazanov [13.10.2013 12:29]:
>> Can be easier to replace the hanging board instead of inventing
>> workarounds for loader? Board hang has their causes.
>
> the board is ok, no need for replacing it. we have several 1000 boards,
> and we see that everyday som
* Sergey Ryazanov [13.10.2013 12:29]:
> If you would a full reboot, then try to set AR71XX_RESET_FULL_CHIP bit
> in register AR71XX_RESET_REG_RESET_MODULE or
[...] thank you for this information, very useful!
> Can be easier to replace the hanging board instead of inventing
> workarounds for loa
Hi Bastian,
2013/10/10 Bastian Bittorf :
> for doing a full reboot in this stage (i think) we have to call
> somehow 'machine_restart(args)' - but where can i find the
> board-specific code/headers?
>
If you would a full reboot, then try to set AR71XX_RESET_FULL_CHIP bit
in register AR71XX_RESET_
* Bastian Bittorf [08.10.2013 09:24]:
> Decompressing kernel... failed, data error!
>
> System halted!
>
>
> it's clear, that in this stage we cannot make use of
> kernel features (e.g. panic_on_oops), because there is
> no kernel yet 8-) IMHO we should enforce a reboot in this
nearly every day we see a hanging router after reboot.
today we could nail it down via serial console:
(see also attached the full log)
###
Autobooting in 1 seconds## Booting image at bf02 ...
Uncompressing Kernel Image ... OK
Starting kernel ...
OpenWrt kernel loader for AR
