From: Robert Hancock <hancockr@shaw.ca>
To: niessner@jpl.nasa.gov
Cc: Kyle McMartin <kyle@mcmartin.ca>, linux-kernel@vger.kernel.org
Subject: Re: Where is the interrupt going?
Date: Thu, 22 Nov 2007 19:20:24 -0600 [thread overview]
Message-ID: <47462AD8.2040905@shaw.ca> (raw)
In-Reply-To: <fa.4GMGd+vtd9BoH5cWYyPKXdddZG4@ifi.uio.no>
niessner@jpl.nasa.gov wrote:
>
> I tried the hammer and the problem persists.
> observer@bbb:~$ cat /proc/cmdline
> root=UUID=8b3c3666-22c3-4c04-b399-ece266f2ef30 ro noapic quiet splash
>
> However, I reserve the right to try the hammer again in the future. When
> I look at /proc/interrupts without the APIC:
> observer@bbb:~$ cat /proc/interrupts
> CPU0
> 0: 144 XT-PIC-XT timer
> 1: 10 XT-PIC-XT i8042
> 2: 0 XT-PIC-XT cascade
> 5: 100000 XT-PIC-XT ohci_hcd:usb5, mxser
> 6: 5 XT-PIC-XT floppy
> 7: 1 XT-PIC-XT parport0
> 8: 3 XT-PIC-XT rtc
> 9: 1 XT-PIC-XT acpi, uhci_hcd:usb2
> 10: 100000 XT-PIC-XT ohci_hcd:usb4, ehci_hcd:usb6,
> r128@pci:0000:01:00.0
> 11: 2231 XT-PIC-XT uhci_hcd:usb1, ohci_hcd:usb3, eth0
> 12: 130 XT-PIC-XT i8042
> 14: 4362 XT-PIC-XT libata
> 15: 15315 XT-PIC-XT libata
> NMI: 0
> LOC: 130125
> ERR: 0
> MIS: 0
>
> I do not even see the device that I registered unless it is that r128...
> line. However the code printed out in /var/log/messages:
> Nov 22 16:05:27 bbb kernel: [ 104.712473] apc8620: VID = 0x10B5
> Nov 22 16:05:27 bbb kernel: [ 104.712486] apc8620: mapped addr = e0bd4000
> Nov 22 16:05:27 bbb kernel: [ 104.713022] apc8620: registered carrier 0
> Nov 22 16:05:27 bbb kernel: [ 104.713028] apc8620: interrupt data
> (0xe1083e40) on irq (10) and status (0x10)
>
> which indicates it successfully registered without being shared. When I
> have more time, I will changed the code to be a shared IRQ and try the
> noapic again.
You're not calling pci_enable_device anywhere. Unless you do this before
requesting the IRQ, the IRQ routing may not be set up properly for your
device and it may not even give you the right IRQ number. You should see
a line like this somewhere in dmesg for the IRQ your card is on:
ACPI: PCI Interrupt 0000:00:1f.2[D] -> GSI 19 (level, low) -> IRQ 17
I think this behavior changed in the somewhat recent past..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-11-23 1:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.KsmqgW5tYuaXUkIKwnbJk9eJIAI@ifi.uio.no>
[not found] ` <fa.JGl5fAfWYHut6bLbEcD35M84qbY@ifi.uio.no>
[not found] ` <fa.4GMGd+vtd9BoH5cWYyPKXdddZG4@ifi.uio.no>
2007-11-23 1:20 ` Robert Hancock [this message]
2007-11-22 1:08 Where is the interrupt going? Al Niessner
2007-11-22 1:56 ` Alan Cox
2007-11-22 2:14 ` Kyle McMartin
2007-11-22 2:16 ` Jesper Juhl
2007-11-22 23:56 ` niessner
2007-11-22 2:20 ` Kyle McMartin
2007-11-23 0:48 ` niessner
2007-11-23 1:25 ` Alan Cox
2007-11-23 1:58 ` Bartlomiej Zolnierkiewicz
2007-11-23 10:36 ` Alan Cox
2007-11-23 3:18 ` Marin Mitov
2007-11-23 4:31 ` niessner
2007-11-23 8:16 ` Jiri Slaby
2007-11-22 2:50 ` Arjan van de Ven
2007-11-23 21:53 ` Benjamin Herrenschmidt
2007-11-26 22:49 ` Al Niessner
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=47462AD8.2040905@shaw.ca \
--to=hancockr@shaw.ca \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=niessner@jpl.nasa.gov \
/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).