Comment 7 for bug 67868

On Wed, Feb 09, 2005 at 07:22:31PM +0100, Michael Meskes wrote:
>On Fri, Aug 20, 2004 at 10:28:12PM +0200, David Härdeman wrote:
>> I can still see this behavious (5 years later), with a recent (2.6.8.1)
>> kernel and hardware watchdog (i8xx-tco).
>
>Do you still see the bug? Do you have any time to debug it a little bit?
>I still cannot reproduce it.
>
>Michael

I'm sorry, as I said later in that bug, I cannot reproduce it. It turned
out that my problems where misconfigurations (such as machine setup to
ping itself while at the same time not replying to pings, overly
restrictive firewalling etc).

This is also indicated by the error message which I got from watchdog
(101 = ENETUNREACH = Network is unreachable). Now, the bug reporter got
106, which is probably EISCONN = Transport endpoint is already
connected, which I've only seen either when calling connect twice on a
socket, or when using sendto with a destination address on a
connect():ed socket.

I've been through the latest sources trying to find something fishy that
would cause the problems reported. The only thing I found which looks a
bit weird is this:

watchdog.c, line 562, setsockopt uses hold as an argument, but hold has
not been initialized, which might mean that broadcast packets are in
fact not enabled, right?

That shouldn't account for the 106 error though, maybe the original bug
has been fixed since it was reported?

Re,
David