Note the work-around for this bug is not in the GIT repository for the
watchdog package as:
http://sourceforge.net/p/watchdog/code/ci/0d156df287656d1031389cac99caa9fa94c2d204/
Hopefully a release of version 5.15 soon will make that more widely
available.
--
You received this bug notification be
** Tags added: bios-outdated-f9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about this bug go to:
https://bugs.launchp
Well I guess no one is going to fix the it87_wdt module any time soon :(
As a work-around, my own version of the watchdog daemon (update #117 or
later) now detects if it is reported as "IT87 WDT" when queried and re-
sets the time-out on each refresh, rather then writing '\0' to the
device. It app
Looking through the code in it87_wdt.c it appears that the open/close of
the timer is performed by writing to the configuration registers that
Cinquero identified, however, that is not how the refresh is performed!
Looking at this part of the code:
/* watchdog timer handling */
static void wdt_k
What is odd is that I can set the time-out OK, and I can stop the
watchdog OK and it no longer reboots, but it is the simple "refresh"
that appears not to work!
NOTE: Stopping using "pkill watchdog" as that closes the device, where
as "service watchdog stop" swaps to the wd_keepalive daemon that
p
This problem is also showing up with our new PCs using the IT8728
(motherboard is Gigabyte Z87-D3HP). The watchdog is armed and the time-
out can be set, but the "refresh" is not working so the machine reboots
after the chip's time-out period.
Jul 2 16:57:04 kernel: [ 346.256483] it87_wdt: Chip
@Cinquero,
I removed the "patch" flag on your attachment because it isn't a fix for
this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
T
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about th
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
Tried that patch, but didn't help.
** Patch added: "74h-73h-reorder-patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/932381/+attachment/2758812/+files/linux-3.2.0.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Tags removed: kernel-request-3.2.0-17.26
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
T
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver
It is not a new issue.
Just tested http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.3-rc4-precise/ and it is still ignoring the watchdog
daemon.
Looking at
https://github.com/torvalds/linux/blob/v3.3-rc4/drivers/watchdog/it87_wdt.c#L240
could give the answer: LSB (73h) gets updated before MSB
o you know if this issue happened in a previous version of Ubuntu, or is
this a new issue?
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the la
apport crashes here:
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=WJ21wGmBrhnGSKkBlnNw&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue
apport information
** Tags added: apport-collected
** Description changed:
The watchdog daemon resets the driver via /dev/watchdog, but the machine
nonetheless resets after 60 seconds.
$ modprobe it87_wdt
$ dmesg | tail -n 1
[173619.473716] IT87 WDT: Chip IT8720 revision 8 initial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
IT87 watchdog timer driver not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
** Attachment added: "image002.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/932381/+attachment/2740029/+files/image002.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932381
Title:
It seems the kernel driver does not update using the correct order.
Here is what ITE sent me (including the two attachments):
1.If you wanted WDT to stop, you will need to set ¡§index 74(HWB)¡¨ and
¡§index 73h(LSB)¡¨ to 00h
2.If you wanted WDT to restart. You will need to first
22 matches
Mail list logo