*BSD News Article 64156


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!odin.oar.net!malgudi.oar.net!imci4!newsfeed.internetmci.com!in2.uu.net!news1.digex.net!news3.digex.net!digex.net!not-for-mail
From: dcmyers@access4.digex.net (David Myers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Stray IRQ 7s
Date: 23 Mar 1996 15:36:57 -0500
Organization: Express Access Online Communications USA: 800-969-9090
Lines: 24
Message-ID: <4j1nd9$7uf@access4.digex.net>
NNTP-Posting-Host: access4.digex.net



Ever since I added a cheapo Logitech SoundMan sound card to my FreeBSD
system (P90, Asus motherboard, Triton chipset), I've been getting console
messages about stray IRQ 7s being picked up by the kernel.  Sure enough,
the sound card is running on IRQ 7, as is the parallel port -- but I did
compile in SoundBlaster support with the "conflicts" flag on.  In fact, I
get so many of these messages that syslog eventually says it won't report
them anymore.  I have not detected any problem with these stray interrupts,
but I thought I'd ask: is this anything to worry about?  Will it impact
performance?  Cause unstable behavior?

A possibly related matter is the fact that the sound card is detected at
boot time on port 220 only about one time in three.  Any ideas why this
would be?  (I've configured the kernel to treat the card as a SoundBlaster
Pro.)

Thanks. 

-David.
-- 
________________________________________
David C. Myers
dcmyers@access.digex.net