From owner-freebsd-isdn Wed Oct 27 7:29:33 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from ixori.demon.nl (ixori.demon.nl [195.11.248.5]) by hub.freebsd.org (Postfix) with ESMTP id 6D10F14C92 for ; Wed, 27 Oct 1999 07:29:22 -0700 (PDT) (envelope-from bart@ixori.demon.nl) Received: from ixori.demon.nl (localhost.ixori.demon.nl [127.0.0.1]) by ixori.demon.nl (8.9.3/8.9.1) with ESMTP id QAA04555; Wed, 27 Oct 1999 16:32:00 +0200 (CEST) (envelope-from bart@ixori.demon.nl) Message-ID: <38170CE0.869476E6@ixori.demon.nl> Date: Wed, 27 Oct 1999 16:32:00 +0200 From: Bart van Leeuwen Reply-To: bart@ixori.demon.nl Organization: IxorI X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: hm@hcs.de Cc: webbasan@muc.de, freebsd-isdn@freebsd.org Subject: Re: Trouble after installing i4b 0.83: "xl0: watchdog timeout" References: <19991027140415.9E40038D6@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Funny thing is that I have seen that same watchdog timeout message on xl0 for quite a while now. again) In my case it looks like this had to do with xl0 and the miibus in FreeBSD 4.0-CURRENT. Besides a message each boot there wasn't any serious problem that prevented me from using the setup, and lack of time stopped me from figuring out what exactly caused this. Anyway, for the case of the discussion, I saw this on a machine without any i4b running. The machine was runing a very recent 4.0-CURRENT, and the message has been there for a few months (as far as I am aware since the mii bus stuff), and has been gone since last weekend's make buildworld ;-) The system I have is based on an Asus P2B system board with 2x pII 333 cpu, 256 megs of memory, 2x 3com 3c905 100mbit,on board scsi, matrox g400 graphics card. running FreeBSD 4.0-CURRENT, usually not older then 2-3 weeks. Anyway, if the problem discussed here occured on 4.0-CURRENT I don't think it has anything to do with i4b, tho the hw combination of course may trigger it. -- Bart van Leeuwen - bart@ixori.demon.nl - http://www.ixori.demon.nl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message