From owner-freebsd-bugs  Mon Apr 17 19:29:05 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA10542
          for bugs-outgoing; Mon, 17 Apr 1995 19:29:05 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA10535
          for <freebsd-bugs@freebsd.org>; Mon, 17 Apr 1995 19:28:55 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id TAA25113; Mon, 17 Apr 1995 19:28:51 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA00214; Mon, 17 Apr 1995 19:28:50 -0700
Message-Id: <199504180228.TAA00214@corbin.Root.COM>
To: Bernard.Steiner@germany.eu.net
cc: freebsd-bugs@FreeBSD.org
Subject: Re: couple of bugs in 2.0R 
In-reply-to: Your message of "Mon, 17 Apr 95 19:18:50 +0200."
             <199504171719.TAA03159@qwerty.Germany.EU.net> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 17 Apr 1995 19:28:49 -0700
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>Sorry if one or both of these have been mentioned before...
>
>The watchdog timer in i386/isa/if_ed.c gets set to 2, which appears not to be
>enough (on my system, that is). I increased the value to 20 (as an ad-hoc
>solution), and now I don't get any more of those
>stray irq 11
>ed0 timeout
>messages. Unless solved, can we get a flag for ed that sort of increases the
>watchdog timer significantly ?

   Umm, that would increase the timeout to 20 seconds. This is not desireable
and should never be necessary. I don't see how increasing it above what it
currently is could affect the problem at all (the interrupt should occur in
less than 100ms no matter what happens).

-DG