From owner-freebsd-current Wed Apr 17 10:39:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21690 for current-outgoing; Wed, 17 Apr 1996 10:39:18 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21674 for ; Wed, 17 Apr 1996 10:39:11 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id KAA05218; Wed, 17 Apr 1996 10:39:32 -0700 Date: Wed, 17 Apr 1996 10:39:31 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Tony Kimball cc: current@freefall.freebsd.org Subject: Re: EtherExpress16 problems In-Reply-To: <199604171728.MAA24785@compound.Think.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Apr 1996, Tony Kimball wrote: > > Recently, I began getting > /kernel: ix0: device timeout > messages on my main box. I also (although not invariably) > get > ixintr without being inited!! > at boot time (q.v. dmesg log attached below). Is it possible Hm. I don't like this line: > ix0 at 0x210-0x21f irq 4 maddr 0xd0000 msize 32768 on isa > ix0: address 00:aa:00:37:06:87 IRQ 4?!? I've never used that. Try 5 instead. 4 is probably being used by something else. > ixintr without being inited!! That should solve this too. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major