Date: Tue, 10 Jun 1997 14:11:29 -0500 From: Bob Willcox <bob@luke.pmr.com> To: Stefan Esser <se@FreeBSD.ORG> Cc: Terry Lambert <terry@lambert.org>, stesin@gu.net, matt@3am-software.com, hackers@FreeBSD.ORG Subject: Re: Does SMC9332BDT work in 2.2.2R?? Message-ID: <19970610141129.32251@luke.pmr.com> In-Reply-To: <19970610101445.26928@mi.uni-koeln.de>; from Stefan Esser on Tue, Jun 10, 1997 at 10:14:45AM %2B0200 References: <Pine.BSF.3.96.970609185104.15820Q-100000@trifork.gu.net> <199706091814.LAA29703@phaeton.artisoft.com> <19970610101445.26928@mi.uni-koeln.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 10, 1997 at 10:14:45AM +0200, Stefan Esser wrote: > On Jun 9, Terry Lambert <terry@lambert.org> wrote: > > Here is a duplicate of a response I've sent in the past. I suspect > > that it is the problem in your case. > > > > > > | This is probably the problem (the 5th slot, not the bus mastering). > > | > > | It has to do with PCI interrupt sharing. > > | > > | The PCI INT's are normally daisy-chained, and slots 4 and 5 (if 5 > > | is present) are expected to share: > > | > > | slot 1 slot 2 slot 3 slot 4 slot 5 > > | ,-. ,-. ,-. ,-. ,-. > > | INT A --|A|-. ,------|B|-. ,------|C|-. ,------|D|----------|D| > > | | | X | | X | | X | | | | > > | INT B --| |-' \ ,----| |-' \ ,----| |-' \ ,----| |----------| | > > | | | X | | X | | X | | | | > > | INT C --| |---' \ ,--| |---' \ ,--| |---' \ ,--| |----------| | > > | | | X | | X | | X | | | | > > | INT D --| |-----' `--| |-----' `--| |-----' `--| |----------| | > > | `-' `-' `-' `-' `-' > > | > > | By default, each PCI card will use the first interrupt connector, > > | which will be A, B, C, or D, depending on the slot (note: old PCI > > | hardware will *NOT* chain... it expects the boards to be jumper > > | configurable, or all boards to share INT A). > > Why should that cause ANY problems > for a bus-master card in slot 5 ??? I have moved my SMC card to another PPro system (my dual processor test machine) which only has 3 PCI cards in it (NCR SCSI, Matrox Melenium, and the SMC ethernet) which is running -current and still experience the same problem (with a UP kernel, with a SMP kernel I get timeouts on the device -- same as I get with an Intel EtherExpress Pro/100B card, though the Intel card does work with the UP kernel). Right now, the only way to get that system on my network is to use the Intel card with a UP kernel. :-( > > Regards, STefan -- Bob Willcox Anyone who is capable of getting themselves made bob@luke.pmr.com President should on no account be allowed to do the job. Austin, TX -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970610141129.32251>