On Tue, 2008-07-08 at 14:06 -0700, Dan Mick wrote:
> Sebastien Roy wrote:
> > What should I make of the following messages generated on my Toshiba
> > Portégé r500?
> > 
> > Jul  8 13:46:50 seb unix: [ID 954099 kern.info] NOTICE: IRQ16 is being 
> > shared by drivers with different interrupt levels.
> > Jul  8 13:46:50 seb This may result in reduced system performance.
> 
> It might be worth looking for messages with 'pcplusmp' in them to see what 
> drivers are sharing that interrupt, but...there's generally not a lot you 
> can do about it these days; interrupt inputs are fixed, assigned by the 
> system manufacturer.  So it's mostly a matter of interest, and checking to 
> make sure it's not, say, your 1394 controller you never use, and your IDE 
> controller, which is critical.  (if so, you could, say, disable the 1394 
> driver.  Then again, it's pretty unlikely a system would be so stupidly 
> designed.)

Thanks for the tip.  It turns out that I have more than one of these
shared IRQ notices during boot:

Jul  8 17:24:56 seb unix: [ID 954099 kern.info] NOTICE: IRQ19 is being shared 
by drivers with different interrupt levels.
Jul  8 17:25:03 seb unix: [ID 954099 kern.info] NOTICE: IRQ21 is being shared 
by drivers with different interrupt levels.
Jul  8 17:25:12 seb unix: [ID 954099 kern.info] NOTICE: IRQ18 is being shared 
by drivers with different interrupt levels.
Jul  8 17:25:34 seb unix: [ID 954099 kern.info] NOTICE: IRQ16 is being shared 
by drivers with different interrupt levels.

According to the pcplusmp output, these correspond to the following
driver instances:

IRQ19: ahci instance 0
IRQ21: pcic instance 0
IRQ18: uhci instance 2
IRQ16: uhci instance #3

(note the #3, that's not a typo, pcplusmp decided to put a # sign in
front of one of the uhci instances and not the other)

I don't see any duplicate uses of these interrupts as reported by
pcplusmp though.  Is there perhaps a bug in the reporting and that
there's in fact no clash?

-Seb


_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to