From: Dietmar Kling <d.kling@kling-bauer.de>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7 and setpci no go
Date: Mon, 23 Jul 2001 09:38:47 +0200 [thread overview]
Message-ID: <3B5BD487.2050308@kling-bauer.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10107222138280.27761-100000@coffee.psychology.mcmaster.ca>
[-- Attachment #1: Type: text/plain, Size: 4663 bytes --]
> it looks like you setpci while the driver was loaded.
> normally, drivers only query the irq on load.
Sorry but i did set all this values in the init script (even before proc
with the -H1 switch
of setpci) of my redhat 7.1
but the output of dump_irq ( i've read about this on the
kernel-mailing-list )
looks rather strange.
output of lscpi -vv -xxxx attached toot
Any Hints?
Regards
Dietmar
Interrupt routing table found at address 0xfdf00:
Version 1.0, size 0x0090
Interrupt router is device 00:00.0
PCI exclusive interrupt mask: 0x0820 [5,11]
Device 00:08.0 (slot 1):
INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:09.0 (slot 2): Ethernet controller
INTA: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:0a.0 (slot 3):
INTA: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:0b.0 (slot 4):
INTA: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:0c.0 (slot 5):
INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:0d.0 (slot 6):
INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Device 00:01.0 (slot 0): PCI bridge
INTA: link 0x01, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTB: link 0x02, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTC: link 0x03, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
INTD: link 0x04, irq mask 0xdeb8 [3,4,5,7,9,10,11,12,14,15]
Interrupt router at 00:00.0: unknown vendor 0x1106 device 0x3099
PIRQ? (link 0x01): unrouted?
PIRQ? (link 0x02): irq 10
PIRQ? (link 0x03): unrouted?
PIRQ? (link 0x04): unrouted?
[root@thor /root]#
Mark Hahn wrote:
>it looks like you setpci while the driver was loaded.
>normally, drivers only query the irq on load.
>
>
>>### Example 1 ####
>>/sbin/setpci -v -s 00:11.5 INTERRUPT_LINE=9
>>00:11.5:3c 09
>>/sbin/lspci -v -s 00:11.5 -x
>>00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
>>Controller (rev 10)
>> Subsystem: Elitegroup Computer Systems: Unknown device 0996
>> Flags: medium devsel, IRQ 11
>> I/O ports at e400 [size=256]
>> Capabilities: [c0] Power Management version 2
>>00: 06 11 59 30 01 00 10 02 10 00 01 04 00 00 00 00
>>10: 01 e4 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 96 09
>>30: 00 00 00 00 c0 00 00 00 00 00 00 00 09 03 00 00
>> ^^<---
>>changed
>>### Example 2 ####
>>/sbin/setpci -v -s 00:11.5 INTERRUPT_LINE=0x0a
>>00:11.5:3c 0a
>>/sbin/lspci -v -s 00:11.5 -x
>>00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
>>Controller (rev 10)
>> Subsystem: Elitegroup Computer Systems: Unknown device 0996
>> Flags: medium devsel, IRQ 11
>> I/O ports at e400 [size=256]
>> Capabilities: [c0] Power Management version 2
>>00: 06 11 59 30 01 00 10 02 10 00 01 04 00 00 00 00
>>10: 01 e4 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>20: 00 00 00 00 00 00 00 00 00 00 00 00 19 10 96 09
>>30: 00 00 00 00 c0 00 00 00 00 00 00 00 10 03 00 00
>> ^^<---
>>changed
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>
[-- Attachment #2: lspci.txt.gz --]
[-- Type: application/octet-stream, Size: 2120 bytes --]
next parent reply other threads:[~2001-07-23 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10107222138280.27761-100000@coffee.psychology.mcmaster.ca>
2001-07-23 7:38 ` Dietmar Kling [this message]
2001-07-22 21:18 2.4.7 and setpci no go Dietmar Kling
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=3B5BD487.2050308@kling-bauer.de \
--to=d.kling@kling-bauer.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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