From owner-freebsd-current  Thu Jul 10 04:10:46 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA26373
          for current-outgoing; Thu, 10 Jul 1997 04:10:46 -0700 (PDT)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA26366
          for <freebsd-current@freebsd.org>; Thu, 10 Jul 1997 04:10:42 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA12847
  (5.67b/IDA-1.5 for <freebsd-current@FreeBSD.ORG>); Thu, 10 Jul 1997 13:10:39 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id NAA06291; Thu, 10 Jul 1997 13:10:41 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19970710131040.40020@mi.uni-koeln.de>
Date: Thu, 10 Jul 1997 13:10:40 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: "John W. DeBoskey" <jwd@unx.sas.com>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: 3.0-970621-SNAP & fxp0 failure
References: <199707092020.AA26603@iluvatar.unx.sas.com> <199707092205.PAA24480@implode.root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <199707092205.PAA24480@implode.root.com>; from David Greenman on Wed, Jul 09, 1997 at 03:05:11PM -0700
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Jul 9, David Greenman <dg@root.com> wrote:
> >fxp0: <Intel EtherExpress Pro 10/100B Ethernet>
> >       rev 0x01 int a irq 15 on pci0.17.0

> >vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 14 on pci1.9.0

>    Looks like an interrupt problem. Many systems have the secondary IDE
> controller mapped to using irq15, so perhaps that is the problem. Try moving
> the Intel card to a physically different slot - this should cause the PCI
> BIOS to assign a different interrupt.

True! The PCI/ISA code in FreeBSD does not check
for conflicts between bus types, currently. (I 
have fixed this in my development sources, but
wait for a consensus on how conflicts checking 
is generally approached before I'll commit my
code.)

It is generally good to avoid using IRQ14 and 
IRQ15 for PCI devices. Your BIOS may allow to
reserve them for ISA devices, even if you don't
actually use any IDE drives.

In case you *do* have IDE drives connected, the
system will most probably crash, if there is an
IRQ conflict. But I actually don't know enough 
about IDE to understand, when IRQ14 is used for
a disk drive, and when IRQ15 gets used ...

You may want to do a "dmesg | grep 'irq 14'"
(and the same for 'irq 15') and look for more
than one line matching the conditions.

Regards, STefan