Bug 1085759 - System fails to boot when network watchdog enabled
Summary: System fails to boot when network watchdog enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: watchdog
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-09 09:38 UTC by Luca Giuzzi
Modified: 2014-04-10 11:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-10 11:11:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output of the journal for a boot cycle (128.68 KB, text/plain)
2014-04-09 10:03 UTC, Luca Giuzzi
no flags Details

Description Luca Giuzzi 2014-04-09 09:38:03 UTC
Description of problem:

I wanted to enable the watchdog functionality on a machine which is configured by
DHCP; actually I would like to require that if after a given amount of time (say 240 seconds) the network has not been properly configured the computer has to reboot.

However, as soon as I enable the watchdog service the computer starts rebooting every 30 seconds and it never completes the first boot.


Version-Release number of selected component (if applicable):
watchdog-5.13-2.fc20.x86_64
kernel-3.13.9-200.fc20.x86_64

How reproducible:

Enable the watchdog 







Steps to Reproduce:
1. enable the watchdog device with systemctl enable watchdog
2. try to boot the machine
3. wait 30 seconds

Actual results:

Every 30 seconds the computer reboots; as the it takes more than 30 seconds to configure the network interface, the watchdog kicks in and the computer keeps on rebooting


Expected results:

The watchdog reboots the machine after 280 seconds without network connectivity
(per configuration of iTCO_wdt)

Additional info:

The computer is an old(ish) Core 2 Duo E6750 with ICH8 chipset.
In /etc/modprobe.d I have a file watchdog.conf with
options iTCO_wdt heartbeat=240

[dmesg confirms that this setting is picked up]
the only uncommented lines in watchdog.conf are

ping			= 10.22.0.1
interface		= p20p1

[10.22.0.1 is the router which should be picked up via DHCP; the host
actually has a static IP, but it is configured none-the-less by DHCP]

Comment 1 Richard W.M. Jones 2014-04-09 10:02:06 UTC
Note we don't write the watchdog, just package it for Fedora.

If there are bugs in the watchdog it's better to take them upstream.
(In this case it could be a bug in the kernel iTCO_wdt driver.)

http://watchdog.sourceforge.net/

Comment 2 Luca Giuzzi 2014-04-09 10:03:08 UTC
Created attachment 884459 [details]
output of the journal for a boot cycle

Comment 3 Ales Ledvinka 2014-04-10 11:11:34 UTC
Sorry, the code update from November slipped without a new build. Not sure now about the reason why I postponed the build / what else I wanted to fix.

Grab the 5.13.9 from testing once it gets pushed to mirrors.
And see the man page - all the steps to resolve this are there.
Please reopen this if you find the information misleading, wrong or simply have a better idea.

Comment 4 Ales Ledvinka 2014-04-10 11:21:42 UTC
It's going to be 5.13.10 since the 5.13.9 was already automatically discarded.
https://koji.fedoraproject.org/koji/buildinfo?buildID=477008

Comment 5 Fedora Update System 2014-04-10 11:53:20 UTC
watchdog-5.13-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/watchdog-5.13-10.fc20


Note You need to log in before you can comment on or make changes to this bug.