Date: Sat, 13 Aug 2005 22:43:51 -0700 From: Brandon Fosdick <bfoz@bfoz.net> To: Mike Jakubik <mikej@rogers.com> Cc: stable@freebsd.org Subject: Re: IRQ conflict between twa0 and skc0 Message-ID: <42FEDA17.4030400@bfoz.net> In-Reply-To: <3579.172.16.0.199.1123995836.squirrel@172.16.0.1> References: <42FE8A25.3000101@bfoz.net> <3545.172.16.0.199.1123994542.squirrel@172.16.0.1> <42FECCD8.8080902@bfoz.net> <3579.172.16.0.199.1123995836.squirrel@172.16.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Jakubik wrote: > Forgot to mention. You can always buy a cheap pciE video card :) You're a big help :) I was fiddling and I noticed something odd. Previously, the ESCD screen at boot showed the raid controller and network controller both at IRQ 5. The dmesg I sent before showed both at IRQ 18. That seemed odd to me. I also noticed that unused drive channels were being assigned IRQs so I disabled them in the BIOS. The idea being to free up an IRQ and maybe one of the controllers would use it. Now the ESCD table shows both the raid and the network on IRQ 10 and dmesg still shows them at IRQ 18. This seems screwy to me, but I have no idea what it means. Now that I know both IRQs 10 and 18 are useable, is there some way to force the drivers? Aren't there some boot hints that handle this? Or was it done in the kernel config. I can't remember. BTW, this is all with the stock SMP kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42FEDA17.4030400>