linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Mika Liljeberg <mika.liljeberg@welho.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1: irq18 nobody cared! on Intel D865PERL motherboard -- found it!
Date: Sun, 27 Jul 2003 01:17:06 +0100	[thread overview]
Message-ID: <200307270117.06786.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <200307270023.43992.adq_dvb@lidskialf.net>


> There is something else that is not being done by linux. I'd assumed this
> was an nforce2-specific issue, but your results hint that it may be larger
> than this.

Yay! I've found it. What seems to be happening is the PIC is left connected to 
the PCI IRQ lines, and is causing problems.. I assume pulling the lines 
up/down incorrectly.

My BIOS lets me define which PIC IRQs are allocated to PCI and which are 
"reserved". I set them all to reserved, effectively disabling any IRQs < 15 
being allocated to PCI. Now everything works perfectly. 

I've downloaded the manual for your motherboard, but I can't see anything like 
that for your board.. all you can do is the standard choose IRQ, or auto.

Anyway, now I know what is causing this, expect a patch soon.


  reply	other threads:[~2003-07-27  0:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 13:12 2.6.0-test1: irq18 nobody cared! on Intel D865PERL motherboard Felipe Alfaro Solana
2003-07-26 21:52 ` Mika Liljeberg
2003-07-26 22:13   ` Andrew de Quincey
2003-07-26 23:01     ` Mika Liljeberg
2003-07-26 23:23       ` Andrew de Quincey
2003-07-27  0:17         ` Andrew de Quincey [this message]
2003-07-27 19:09     ` Felipe Alfaro Solana

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200307270117.06786.adq_dvb@lidskialf.net \
    --to=adq_dvb@lidskialf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.liljeberg@welho.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).