From owner-freebsd-bugs Tue Apr 18 04:39:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA01117 for bugs-outgoing; Tue, 18 Apr 1995 04:39:13 -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 EAA01107 for ; Tue, 18 Apr 1995 04:39:05 -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 EAA26148; Tue, 18 Apr 1995 04:39:03 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id EAA00249; Tue, 18 Apr 1995 04:39:02 -0700 Message-Id: <199504181139.EAA00249@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 "Tue, 18 Apr 95 13:23:01 +0200." <199504181123.NAA03844@qwerty.Germany.EU.net> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 18 Apr 1995 04:39:02 -0700 Sender: bugs-owner@FreeBSD.org Precedence: bulk > currently is could affect the problem at all (the interrupt should occur i > n > less than 100ms no matter what happens). > >Hmm. Very strange, indeed. Note, however, that the kernel reported the >problems in the exact sequence given above, i.e. >first stray irq 11 and then ed0 timeout; both at a snap of a finger's time >from ifconfig ed0 up. > >It works now with the watchdog at 20; I've re-tried the original kernel with a >watchdog set to 2, and that failed. > >Is there anything I should do in order to help track this down, or just set >the watchdog to 20 which doesn't make sense but works (note: there wasn't even >a two second latency in accessing the ethernet) ? What about other values? ...such as 3? Also, should I assume that your ed0 is on irq 11? -DG