https://bugzilla.kernel.org/show_bug.cgi?id=199033
Advertising
--- Comment #38 from Mika Westerberg (mika.westerb...@linux.intel.com) --- Indeed, now it looks like it is actually doing something: [ 1.273211] wdat_wdt wdat_wdt: Running action 0x20 [ 1.273216] wdat_wdt wdat_wdt: Read 0xfe from RTC 0x45 [ 1.273217] wdat_wdt wdat_wdt: Running action 0x21 [ 1.273221] wdat_wdt wdat_wdt: Read 0xfe from RTC 0x45 [ 1.273226] wdat_wdt wdat_wdt: Wrote 0xfe to RTC 0x45 [ 1.273227] wdat_wdt wdat_wdt: Running action 0x8 [ 1.273231] wdat_wdt wdat_wdt: Read 0x1800 from 0x00001868 [ 1.273232] wdat_wdt wdat_wdt: Running action 0x11 [ 1.273235] wdat_wdt wdat_wdt: Read 0x8 from 0x0000186a [ 1.273239] wdat_wdt wdat_wdt: Wrote 0x8 to 0x0000186a The instructions 0x20 and 0x21 that use RTC also look to do the right thing (e.g clear bit 0, which is already cleared). So in general I think this should work. One additional test if you don't mind. Can you check if the watchdog is able to reset the system? You can do this: # echo foo > /dev/watchdog and it should reset the system within 60s or so (depending on the default timeout). -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
