All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Kilian <kilian@bobodyne.com>
To: Roland Dreier <roland@topspin.com>
Cc: Peter Chubb <peterc@gelato.unsw.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems.
Date: Wed, 23 Feb 2005 19:23:41 -0600	[thread overview]
Message-ID: <1109208221.9116.337.camel@desk> (raw)
In-Reply-To: <52sm3malg1.fsf@topspin.com>

On Wed, 2005-02-23 at 15:46 -0800, Roland Dreier wrote:
>     Alan> 	pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &softp->interrupt_line);
>     Alan> 	request_irq(softp->interrupt_line, sseintr, SA_INTERRUPT, "sse", softp);
> 
> Don't do that.  The kernel may need you to use a different interrupt
> number than you read from the PCI config header.  Use dev->irq, as in
> 
> 	request_irq(dev->irq, sseintr, SA_SHIRQ | SA_INTERRUPT, "sse", softp);

    Roland, 

	You are the best. Thank you so much for this information.

    	That was the ticket.

    	request_irq(dev->irq, sseintr, SA_SHIRQ | SA_INTERRUPT, 
	            "sse", softp);

    	It works on all machines now without adding "pci=noapci"

    	I'm running again!!!

                                     -Alan

-- 
- Alan Kilian <kilian(at)bobodyne.com>



  reply	other threads:[~2005-02-24  1:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 20:24 Help enabling PCI interrupts on Dell/SMP and Sun/SMP systems Alan Kilian
2005-02-23 20:46 ` linux-os
2005-02-23 22:17   ` Alan Kilian
2005-02-23 22:58     ` Peter Chubb
2005-02-23 23:24       ` Alan Kilian
2005-02-23 23:46         ` Roland Dreier
2005-02-24  1:23           ` Alan Kilian [this message]
2005-02-24 12:37     ` linux-os
     [not found] <3Bbj7-7lG-17@gated-at.bofh.it>
     [not found] ` <3BbMe-7FP-39@gated-at.bofh.it>
     [not found]   ` <3BdkS-GS-21@gated-at.bofh.it>
2005-02-23 23:25     ` Robert Hancock
     [not found]     ` <3BdNW-1bH-29@gated-at.bofh.it>
     [not found]       ` <3Be7p-1pY-43@gated-at.bofh.it>
2005-02-23 23:52         ` Robert Hancock

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=1109208221.9116.337.camel@desk \
    --to=kilian@bobodyne.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterc@gelato.unsw.edu.au \
    --cc=roland@topspin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.