Watchdog and NO_REBOOT on Hardy

Asked by Ola Ekedahl

I cannot use reboot/restart, not from Gnome or from the terminal.

I have a Dell Optiplex 745 with Ubuntu 8.04/Hardy and this is what the syslog says after boot:

May 30 08:31:40 kp113 kernel: [ 25.947204] iTCO_vendor_support: vendor-support=0
May 30 08:31:40 kp113 kernel: [ 25.969213] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
May 30 08:31:40 kp113 kernel: [ 25.969267] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
May 30 08:31:40 kp113 kernel: [ 25.969273] iTCO_wdt: No card detected

What might be wrong?

Best regards

Question information

Language:
English Edit question
Status:
Needs information
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Bhavani Shankar (bhavi) said :
#1

Hello

Try looking here, It seems to be an old bug.. There should be a workaround here too I think..

https://bugs.launchpad.net/ubuntu/+bug/102982

Regards

Bhavani Shankar.

Revision history for this message
Ola Ekedahl (olaeke) said :
#2

Thanks! I saw that thread, I tried one of the work arounds, the one commenting out lines in a config-file i.e. not blacklisting.
It doesnt feel right blacklisting things like that.

One more thing, I have been running 7.10 on the same computer, without this problem. It appeared after installing 8.04...

Best regards

Revision history for this message
Bhavani Shankar (bhavi) said :
#3

OK creating a bug task... Please feel free to add your comments there in the thread..

Regards

Revision history for this message
Ola Ekedahl (olaeke) said :
#4

It does not seem to be related to the intel_rng "bug". The syslog doesnt say anything about intel_rng, and blacklisting intel_rng does not help either.

Revision history for this message
Shahar Or (mightyiam) said :
#5

Is this solved by a newer version, Ola?

Can you help with this problem?

Provide an answer of your own, or ask Ola Ekedahl for more information if necessary.

To post a message you must log in.