Yes. I create a testing account and did not get server reboot with 30
minutes operation. If I use root account, it will reboot within 2~3
minutes. But, I saw lots of permission denied since I did not grant full
permission for the test account.
--
You received this bug notification because you
Hi Colin,
I was operating the command with root account.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464073
Title:
iTCO_wdt: Unexpected close, not stopping watchdog
To manage notifications
Thanks for help, Colin. You really give us a big help here. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464073
Title:
iTCO_wdt: Unexpected close, not stopping watchdog
To manage
HI Colin,
Only run stress-ng. Once while it's executed, the system will reboot after done
for few cycles.
I can easily duplicate the problem in most of Haswell platform boards.
If I disable iTCO_wdt or rmmod iTCO_wdt driver from kernel, the problem goes
away.
Sinc TCO is not controlled by BIOS,
HI Colin,
Yes. From trying the parameter --sysfs 1, iTCO_wdt is not been triggered and
the server does not reboot self anymore. Appreciate the support. Any question
is on sysfs 1, what does this mean for? Any reason for having such problem if
I did not add sysfs?
--
You received this bug
Public bug reported:
Running stress-ng test and system will auomatically reboot after 60s. From the
dmesg, there is one error shown “iTCO_wdt: Unexpected close, not stopping
watchdog”.
However, I already disabled IPMI and the problem still persists. From system
BIOS saying, BIOS does not fully
