Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Aug 2001 23:05:40 +0300
From:      Peter Pentchev <roam@orbitel.bg>
To:        lists <lists@security.za.net>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Wierd IRQ Routing issues
Message-ID:  <20010802230540.B480@ringworld.oblivion.bg>
In-Reply-To: <Pine.BSF.4.21.0108022158001.19788-100000@security.za.net>; from lists@security.za.net on Thu, Aug 02, 2001 at 10:01:25PM %2B0200
References:  <Pine.BSF.4.21.0108022158001.19788-100000@security.za.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 02, 2001 at 10:01:25PM +0200, lists wrote:
> Hi, hoping someone can help me out with something here, because Ive got a
> very strange problem.
> 
> On my one pc, when assigning an IRQ to my PCIC device, it assigns an IRQ
> and continues, works 100% now that I changed device.hints to look for pcic
> on pci instead of isa, card works everything.
> 
> However, on my other pc with an identical setup, when trying to assign
> pcic irq it does this: (from dmesg):
> 
> pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0
> pci_cfgintr: 0:10 INTA routed to irq 10 
> 
> Now for some reason I have it in my head that that irq routing is broken,
> because its the only difference I can find between the non-working box and
> the working box.  Is there any way that I can force that card to not use a
> routed interrupt like that.  Ive already tried fiddling in my bios with
> the IRQ settings to reserve things etc, no luck there either.  I know for
> a fact that irq 5/7/9/10/11 are all available on my box, with nothing
> taking them.
> 
> Any ideas would be MUCH appreciated

The second box wouldn't be a -stable machine, would it now?
I think PCIC IRQ routing was absolutely not working in -stable as of
a few weeks ago, when Warner Losh started MFC'ing the PCIC bits.
That MFC might not be complete yet.

If both boxes are running -current, I'll just shut up :)

G'luck,
Peter

-- 
This would easier understand fewer had omitted.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010802230540.B480>