From owner-freebsd-hackers Fri Oct 25 14:10:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15027 for hackers-outgoing; Fri, 25 Oct 1996 14:10:56 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15022 for ; Fri, 25 Oct 1996 14:10:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id OAA08906; Fri, 25 Oct 1996 14:10:45 -0700 (PDT) Message-Id: <199610252110.OAA08906@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Steve Passe cc: hackers@freefall.freebsd.org Subject: Re: ed0 timeouts In-reply-to: Your message of "Fri, 25 Oct 1996 14:47:45 MDT." <199610252047.OAA17045@clem.systemsix.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 25 Oct 1996 14:10:45 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I currently am using: > >ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa >ed0: address 00:00:c0:e6:59:48, type WD8013EPC (16 bit) > >I also tried an 8216C Ultra with the same results. >I am using the "hard config" jumper, I also tried a soft config @ IRQ5, 0xD8000 > >my current debug counters show: > > 0x2cbe calls to ed_xmit() > 0x2xb7 tx INTs received > 7 watchdog timeouts > >in an uptime of 1 hour, 37 minutes > >There is still some possibility that the 8254 clock is being mishandled. >The APIC straps it to IRQ2 and ALOT of the kernel code believes it >is at IRQ0, I could have missed one of these points. Is there anything >possible as reguards 8254 problems??? I'd be VERY surprised if the problem was 8254 related. It sounds much more like a problem acking ISA interrupts, or perhaps a bug in the handling of the interrupt masks. Are you only having this problem when running two processors, or does this also occur with just one? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project