Date: 14 Aug 2002 16:40:45 +0000 From: Josh Paetzel <friar_josh@webwarrior.net> To: Jim Frost <jimf@frostbytes.com> Cc: Bosko Milekic <bmilekic@unixdaemons.com>, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 4.6 rl0 and xl0 watchdog timeout problems (and solution) Message-ID: <1029343247.364.22.camel@heater.vladsempire.net> In-Reply-To: <1029270995.6144.127.camel@icehouse> References: <1029102290.9472.188.camel@snowball.frostbytes.com> <20020813162742.B2869@unixdaemons.com> <1029270995.6144.127.camel@icehouse>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2002-08-13 at 20:36, Jim Frost wrote: > On Tue, 2002-08-13 at 16:27, Bosko Milekic wrote: > > > > I thought maybe the thing was incorrectly sensing the media; I still > run > > > 10baseT because it's here and it works and I don't see why I should > > > spend money on a new hub. ifconfig said it autoconfigured to > > > 10baseT/UTP but just to be sure I forced the config. Same problem. > > > > What was sharing the card's IRQ? When you have devices sharing IRQs, > > it obviously takes longer before the handler gets to run. The > > watchdog is getting fired off before the handler gets to run. Was the > > interface working at all? > > I've realized that I did not clearly state the nature of the problem. > No other cards exist in the system to share an IRQ with; this card was > assigned its own (IRQ12 FWIW). > > What appears to be special is that the slot that the card in shares a > single PCI interrupt assignment with another slot (which was empty). > I.e. if I go into the BIOS config it lists a number of things that can > be assigned interrupts, all of which are currently set to "auto". The > PCI slot assignments are 1/3, 2/6, 4, and 5 (ie only four interrupts can > be assigned between six slots). So long as the card is in slot 4 or > slot 5 it works; if it's in 1, 2, 3 or 6 it does not. > > > Sounds good. You know, it's entirely possible that other operating > > systems silently ignore the watchdog timeouts and you may just think > > that FreeBSD is the problem because it's telling you that maybe you > > should think about changing your setup. > > Could be; certainly that was the case back in the old days with cheap > IDE interfaces that didn't deliver interrupts. Personally I don't much > care if it's just BSD being more picky, but "watchdog timeout" did not > seem to indicate "card is in the wrong PCI slot" to me. > > jim > Did you have the ps/2 mouse controller disabled? That lives on IRQ 12 on every motherboard I"ve seen in ATX form factor. Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1029343247.364.22.camel>