Hi,
On Fri, 4 Mar 2016 16:26:59 +0100 Romain Izard wrote:
> Hi Lothar,
>
> 2016-03-04 15:59 GMT+01:00 Lothar Waßmann :
> >> > I also check the WDT_MR register before and after enabling
> >> > watchdog, the WDV and WDD fields are correct.
> >> >
> >> > Can you check it again? thank
Hi Lothar,
2016-03-04 15:59 GMT+01:00 Lothar Waßmann :
>> > I also check the WDT_MR register before and after enabling
>> > watchdog, the WDV and WDD fields are correct.
>> >
>> > Can you check it again? thank you.
>> >>>
>> >>>
>> >>> Working case:
>> >>> MR on kernel startup: 0
Hi,
On Fri, 4 Mar 2016 05:56:20 -0800 Guenter Roeck wrote:
> On 03/04/2016 05:26 AM, Romain Izard wrote:
> > 2016-03-04 14:09 GMT+01:00 Guenter Roeck :
> >> On 03/04/2016 01:06 AM, Romain Izard wrote:
> >>> 2016-03-04 6:23 GMT+01:00 Guenter Roeck :
> On 03/03/2016 05:35 PM, Yang, Wenyou wrote
On 03/04/2016 05:26 AM, Romain Izard wrote:
2016-03-04 14:09 GMT+01:00 Guenter Roeck :
On 03/04/2016 01:06 AM, Romain Izard wrote:
2016-03-04 6:23 GMT+01:00 Guenter Roeck :
On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
On 2016/3/3 18:29, Romain Izard wrote:
If the internal counter is not refr
2016-03-04 14:09 GMT+01:00 Guenter Roeck :
> On 03/04/2016 01:06 AM, Romain Izard wrote:
>> 2016-03-04 6:23 GMT+01:00 Guenter Roeck :
>>> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
On 2016/3/3 18:29, Romain Izard wrote:
>
> If the internal counter is not refreshed when the watchdog is
On 03/04/2016 01:06 AM, Romain Izard wrote:
Hi Wenyou, Guenter,
2016-03-04 6:23 GMT+01:00 Guenter Roeck :
On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
On 2016/3/3 18:29, Romain Izard wrote:
If the internal counter is not refreshed when the watchdog is
started for the first time, the watchdog
Hi Wenyou, Guenter,
2016-03-04 6:23 GMT+01:00 Guenter Roeck :
> On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
>> On 2016/3/3 18:29, Romain Izard wrote:
>>>
>>> If the internal counter is not refreshed when the watchdog is
>>> started for the first time, the watchdog will trigger very rapidly.
>>> Fo
On 03/03/2016 05:35 PM, Yang, Wenyou wrote:
Hi Romain,
On 2016/3/3 18:29, Romain Izard wrote:
If the internal counter is not refreshed when the watchdog is started
for the first time, the watchdog will trigger very rapidly. For example,
opening /dev/watchdog without writing in it will immediate
Hi Romain,
On 2016/3/3 18:29, Romain Izard wrote:
If the internal counter is not refreshed when the watchdog is started
for the first time, the watchdog will trigger very rapidly. For example,
opening /dev/watchdog without writing in it will immediately trigger a
reboot, instead of waiting for t
On Thu, Mar 03, 2016 at 01:53:47PM +0100, Romain Izard wrote:
> Hi Guenter,
>
> 2016-03-03 13:10 GMT+01:00 Guenter Roeck :
> > On 03/03/2016 02:29 AM, Romain Izard wrote:
> >>
> >> If the internal counter is not refreshed when the watchdog is started
> >> for the first time, the watchdog will trig
Hi Guenter,
2016-03-03 13:10 GMT+01:00 Guenter Roeck :
> On 03/03/2016 02:29 AM, Romain Izard wrote:
>>
>> If the internal counter is not refreshed when the watchdog is started
>> for the first time, the watchdog will trigger very rapidly. For
>> example, opening /dev/watchdog without writing in i
On 03/03/2016 02:29 AM, Romain Izard wrote:
If the internal counter is not refreshed when the watchdog is started
for the first time, the watchdog will trigger very rapidly. For example,
opening /dev/watchdog without writing in it will immediately trigger a
reboot, instead of waiting for the dela
If the internal counter is not refreshed when the watchdog is started
for the first time, the watchdog will trigger very rapidly. For example,
opening /dev/watchdog without writing in it will immediately trigger a
reboot, instead of waiting for the delay to expire.
To avoid this problem, reload th
13 matches
Mail list logo
