From owner-freebsd-current@FreeBSD.ORG Wed Jun 23 17:52:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F07FB16A4CE for ; Wed, 23 Jun 2004 17:52:35 +0000 (GMT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E71643D39 for ; Wed, 23 Jun 2004 17:52:35 +0000 (GMT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id ADAC54BA56; Wed, 23 Jun 2004 14:52:34 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id ABBE84B803 for ; Wed, 23 Jun 2004 14:52:34 -0300 (ADT) Date: Wed, 23 Jun 2004 14:52:34 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-current@freebsd.org In-Reply-To: <20040622230547.F845@ganymede.hub.org> Message-ID: <20040623145003.K845@ganymede.hub.org> References: <20040622230547.F845@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: rl0: watchdog timeout with 5.2.1-RELEASE ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2004 17:52:36 -0000 'k, got a suggestion offlist from someone about this, mainly IRQ issue ... so watched the reboot, and POST(?) is reporting the network controller is on IRQ 10 ... dmesg is reporting it on IRQ 22 ... nothing else on the system is using IRQ 10, according to either POST or dmesg ... so, how do I force the OS to see it on the same IRQ that the hardware appears to think it should be? Thanks ... On Tue, 22 Jun 2004, Marc G. Fournier wrote: > > Just installed the above on a new machine, and shortly after reboot, I start > getting the timeout and can no longer access the network ... the board is an > AX4SPE-UN board, onboard LAN, but I've tried several other Realtek based > cards I have in the office, and all do the same thing ... > > Is there a known bug with the above RELEASE that is fixed in a later kernel? > Anything I can do to compensate for the problem? Or do I have to just give > up on the Realtek chipset and move onto something else? > > Thanks ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664