Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:3581 comp.os.386bsd.questions:13532 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!swrinde!sgiblab!wetware!kaiwan.com!not-for-mail From: jclf@kaiwan.com (Jason Fordham) Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions Subject: Re: [FreeBSD] BT445C SCSI host: 'strayintr c' message - help! Date: 30 Sep 1994 21:21:30 -0700 Organization: KAIWAN Internet (310/527-4279,818/756-0180,714/741-2920) Lines: 16 Message-ID: <36io4a$lnk@kaiwan009.kaiwan.com> References: <36i0fj$akc@kaiwan009.kaiwan.com> <36iiei$q04@newstand.syr.edu> NNTP-Posting-Host: kaiwan009.kaiwan.com Shawn M Carey <smcarey@rodan.syr.edu> wrote: >I think you're on the right track. I was getting this a while back >on a customer's machine. Turns out the card was using interrupt >12 (0xc), and the kernel was configured for irq11. Changing the >irq to 12 (via the SCSI bios setup) made the messages go away, >and also helped the system stay up longer :-) Yes, that does it! Thanks! I must say it's puzzling, though: _something_ was generating the 'strayintr c', and I guess that's now being caught by the bt driver. The kernel had decided (as the setup should have told it) that the 445C was using IRQ 11, so where did the IRQ 12 signal come from? Should the bt driver be trapping it at all?