Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!uunet!in2.uu.net!iphase.com!mark From: mark@iphase.com (Mark Veteikis) Newsgroups: comp.unix.bsd.freebsd.misc Subject: 3Com Card Config Date: 19 Nov 1996 06:45:11 GMT Organization: Interphase Corporation, Dallas TX. Lines: 22 Message-ID: <56rl1n$20m@que.iphase.com> NNTP-Posting-Host: @sw10-fddi.iphase.com While configuring a 3Com 3C509 10BaseT card I found the following. I used a custom kernel with NO IO Port or IRQ conflicts and found that this card (OS?) behaves badly when the IRQ is set to 9. If IRQ 12 is used (still no conflicts), interrupts are handled fine. This occurred with 3 different 35C09b cards and on 1 that supported PNP, PNP was disabled. Looking at sniffer traces during simple ping tests, it looks like using IRQ 9 does not seem to generate receive interrupts consistently. It appears that configuring this card at 9 might be a FreeBSD driver/OS problem, a hw bug, or some old IRQ2/9 foolishness?? For what its worth, Win95 exhibited no problems in any of the above IRQ configurations ( device manager also reported a clean hw config). This problem is difficult to duplicate unless the card is operated in a very quiet environment ( single ISDN router ). I hope this post saves someone else some grief. -- Mark Veteikis mark@iphase.com 1-214-654-5257 Interphase Corp. 13800 Senlac Dallas Tx. 75234