Modify

Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#2146 closed defect (wontfix)

AR7 watchdog doesn't works

Reported by: rootkit85@… Owned by: nico
Priority: normal Milestone: Kamikaze 8.09 RC1
Component: kernel Version:
Keywords: Cc:

Description

The watchdog simply doesn't reboots the machine after the timeout, so it's just useless:

[/]# watchdog -t 10 /dev/watchdog &
[/]# kill %1
[1] + Done                       watchdog -t 10 /dev/watchdog
[/]# date
Sat Jul 28 13:47:33 UTC 2007
[/]# dmesg |fgrep ar7_wdt
ar7_wdt: disabling watchdog timer
ar7_wdt: timer margin 59 seconds (prescale 65535, change 57180, freq 62500000)
ar7_wdt: enabling watchdog timer
ar7_wdt: watchdog device closed unexpectedly, will not disable the watchdog timer
[/]# date
Sat Jul 28 13:49:53 UTC 2007

Attachments (2)

watchdog-fixed-regs1.patch (721 bytes) - added by Axel Gembe 11 years ago.
watchdog-fixed-regs2.patch (721 bytes) - added by Axel Gembe 11 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 11 years ago by nabcore

I see this as well on the Netgear DG834G v2

comment:2 Changed 11 years ago by nico

  • Milestone set to Afterburner 7.09
  • Owner changed from developers to nico
  • Status changed from new to assigned

comment:3 Changed 11 years ago by florian

  • Resolution set to fixed
  • Status changed from assigned to closed

Should be fixed with [8280]

comment:4 Changed 11 years ago by rootkit85@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

No, it still doesn't works:

[/]# dmesg |fgrep ar7_wdt
ar7_wdt: disabling watchdog timer
ar7_wdt: failed to unlock WDT disable reg
ar7_wdt: failed to unlock WDT prescale reg
ar7_wdt: failed to unlock WDT change reg
ar7_wdt: timer margin 59 seconds (prescale 65535, change 57180, freq 62500000)
[/]#  > /dev/watchdog
[/]# dmesg |fgrep ar7_wdt
ar7_wdt: disabling watchdog timer
ar7_wdt: failed to unlock WDT disable reg
ar7_wdt: failed to unlock WDT prescale reg
ar7_wdt: failed to unlock WDT change reg
ar7_wdt: timer margin 59 seconds (prescale 65535, change 57180, freq 62500000)
ar7_wdt: enabling watchdog timer
ar7_wdt: failed to unlock WDT disable reg
ar7_wdt: failed to unlock WDT kick reg
ar7_wdt: watchdog device closed unexpectedly, will not disable the watchdog timer

after 5 min the system is still running

comment:5 Changed 11 years ago by Axel Gembe

Can you try both of the attached patches please?

Changed 11 years ago by Axel Gembe

Changed 11 years ago by Axel Gembe

comment:6 Changed 11 years ago by rootkit85@…

watchdog-fixed-regs1.patch:

ar7_wdt: failed to unlock WDT disable reg
ar7_wdt: failed to unlock WDT prescale reg
ar7_wdt: failed to unlock WDT change reg
ar7_wdt: timer margin 59 seconds (prescale 65535, change 57180, freq 62500000)
ar7_wdt: failed to unlock WDT disable reg 14:13:48 CEST) multi-call binary
ar7_wdt: failed to unlock WDT kick reg

watchdog-fixed-regs2.patch:

ar7_wdt: failed to unlock WDT disable reg
ar7_wdt: failed to unlock WDT prescale reg
ar7_wdt: failed to unlock WDT change reg
ar7_wdt: timer margin 59 seconds (prescale 65535, change 57180, freq 62500000)
ar7_wdt: failed to unlock WDT disable reg 14:13:48 CEST) multi-call binary
ar7_wdt: failed to unlock WDT kick reg

comment:7 Changed 11 years ago by loswillios

I can confirm that it doesn't work with neither of the patches on a W701V (TNETD7200). First patch doesn't change anything, but watchdog-fixed-regs2.patch produces the following:

io scheduler noop registered
io scheduler deadline registered (default)
3{ôËoloÄ
        ÃKC
           û´óÃû;»ô
                   hk
                     ;
                      3ÃKDK{Ë

comment:8 Changed 10 years ago by nico

  • Resolution set to wontfix
  • Status changed from reopened to closed

watchdog has been disabled in [8422] until we can make it work as expected

comment:9 Changed 10 years ago by anonymous

Is this still disabled ?

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.