mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: dledford@redhat.com (Doug Ledford)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	bennyb@ntplx.net (Benedict Bridgwater),
	linux-kernel@vger.kernel.org (Linux-Kernel)
Subject: Re: 2.4.4-ac5 aic7xxx causes hang on my machine
Date: Wed, 9 May 2001 16:49:25 +0100 (BST)	[thread overview]
Message-ID: <E14xWDP-0002dE-00@the-village.bc.nu> (raw)
In-Reply-To: <3AF96164.40F73A9@redhat.com> from "Doug Ledford" at May 09, 2001 11:25:24 AM

> EXTREMELY unlikely.  Under a 2.2 no-apic kernel, the aic7xxx card uses IRQ 11
> and works.  Under a 2.2 ioapic kernel, it uses high interrupts and works. 

non SMP that is clueless ignorance mode, SMP that is MP table mode

> situation.  Specifically, if the eepro100 or e100 drivers are not loaded, then
> IRQ 10 is not enabled by any device driver and loading the aic7xxx driver
> simply results in infinite SCSI bus timeouts with nary a single interrupt on
> pin 11.  However, if the eepro100 or e100 driver is loaded, then IRQ 10 will
> have an active interrupt handler on it (which implies the interrupt is enabled
> in the PIC) and loading the aic7xxx driver will hard lock the machine (which

Which is exactly why I think it is an  IRQ routing table bug. It is wired
to IRQ 10 and claims to be on IRQ 11.

There are two things at work here

	PCI_INTERRUPT_LINE - random gunge for the OS
	PCI_INTERRUPT_PIN - INTA/INTB/INTC/INTD wiring

The tables are then described by the $PIRQ table in the BIOS. We use that to
load the mapping registers in the PCI bridge (and also to read them). If the
tables are wrong then we will mismap interrupt INTA-D lines to IRQ lines.

IRQ11 appearing on IRQ10 sounds exactly like the INTA-D line setting for IRQ
11 is wrong and we connected it to IRQ 10

Alan



  reply	other threads:[~2001-05-09 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 12:59 Benedict Bridgwater
2001-05-09 14:06 ` Alan Cox
2001-05-09 15:25   ` Doug Ledford
2001-05-09 15:49     ` Alan Cox [this message]
2001-05-09 15:52       ` Doug Ledford
2001-05-09 16:10         ` Alan Cox
2001-05-09 16:21           ` Doug Ledford
2001-05-09 16:59             ` Alan Cox
2001-05-09 17:08               ` Doug Ledford
2001-05-09 17:16                 ` Alan Cox
     [not found]     ` <3AF96271.81C27F57@mandrakesoft.com>
     [not found]       ` <3AF9661B.1707F5E3@redhat.com>
     [not found]         ` <3AF96811.3C6C196D@mandrakesoft.com>
     [not found]           ` <3AF96B39.7C7888F4@redhat.com>
     [not found]             ` <3AF96D99.AB18CB4F@mandrakesoft.com>
     [not found]               ` <3AF97DE0.3C6455A6@ntplx.net>
2001-05-10 14:39                 ` Ben Bridgwater
2001-05-09 16:21   ` Andy Carlson
  -- strict thread matches above, loose matches on Subject: below --
2001-05-07 12:43 [Patch] Do not account shmem pages to the page cache Christoph Rohland
2001-05-07 13:04 ` 2.4.4-ac5 aic7xxx causes hang on my machine Andy Carlson
2001-05-07 13:58   ` Oyvind Jagtnes
2001-05-07 14:14   ` Justin T. Gibbs

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=E14xWDP-0002dE-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bennyb@ntplx.net \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®