https://bugzilla.kernel.org/show_bug.cgi?id=199033
--- Comment #27 from Mika Westerberg (mika.westerb...@linux.intel.com) --- There is something wrong. If you have the patch applied you should see at least when the driver is probed. On my system there are entries like: [ 4.811109] wdat_wdt wdat_wdt: Running action 0x20 [ 4.811111] wdat_wdt wdat_wdt: Read 0x0 from 0x3ca0eb18 [ 4.811112] wdat_wdt wdat_wdt: Running action 0x21 [ 4.811113] wdat_wdt wdat_wdt: Read 0x0 from 0x3ca0eb18 [ 4.811114] wdat_wdt wdat_wdt: Wrote 0x0 to 0x3ca0eb18 in dmesg. Can you run following command and paste the output here? # grep -H . /sys/class/watchdog/watchdog0/* On my local system the output looks like: /sys/class/watchdog/watchdog0/bootstatus:0 /sys/class/watchdog/watchdog0/dev:249:0 /sys/class/watchdog/watchdog0/identity:wdat_wdt /sys/class/watchdog/watchdog0/nowayout:0 /sys/class/watchdog/watchdog0/state:inactive /sys/class/watchdog/watchdog0/status:0x0 /sys/class/watchdog/watchdog0/timeleft:0 /sys/class/watchdog/watchdog0/timeout:0 /sys/class/watchdog/watchdog0/uevent:MAJOR=249 /sys/class/watchdog/watchdog0/uevent:MINOR=0 /sys/class/watchdog/watchdog0/uevent:DEVNAME=watchdog0 You may need to enable CONFIG_WATCHDOG_SYSFS in your .config to see all the attributes. -- 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
