On 09/26/2012 02:19 AM, Stephane Grosjean wrote:
Good morning,
I first sent the below e-mail on September, 24th... Perhaps it fell
somewhere, perhaps the answer fell in some junk e-mail folders too, or
perhaps you didn't find time to answer (sorry for the noise if this is
the case).
So I decided to retry once...
I'm working on an issue with one of our PCI adapters.
This PCI adapter is a standard and well proven board, for many years:
$ lspci -v
...
04:08.0 Network controller: PEAK-System Technik GmbH PCAN-PCI CAN-Bus
controller (rev 02)
Subsystem: PEAK-System Technik GmbH 2 Channel CAN Bus SJC1000
Flags: medium devsel, IRQ 11
Memory at f0410000 (32-bit, non-prefetchable) [size=64K]
Memory at f0400000 (32-bit, non-prefetchable) [size=64K]
Kernel driver in use: pcan
What does lspci -vv show for the device? It gives a bit more detail.
The running system is:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.1.9-1.4-desktop (geeko@buildhost) (gcc
version 4.6.2 (SUSE Linux) ) #1 SMP PREEMPT Fri Jan 27 08:55:10 UTC 2012
(efb5ff4)
...
[ 0.000000] Kernel command line:
root=/dev/disk/by-id/ata-SPCC_Solid_State_DiskB28_00000000000000000015-part2
resume=/dev/disk/by-id/ata-SPCC_Solid_State_DiskB28_00000000000000000015-part1
splash=silent quiet vga=0x31b
...
[ 0.471267] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 10 *11 12
14 15)
[ 0.471323] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 10 11 12
14 15) *7
[ 0.471378] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 10 11 12
14 15) *7
[ 0.471434] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 *10 11 12
14 15)
[ 0.471487] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 10 11 12
14 15) *0, disabled.
[ 0.471541] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 10 11 12
14 15) *0, disabled.
[ 0.471594] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 *10 11 12
14 15)
[ 0.471647] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 10 *11 12
14 15)
We don't succeed to send and receive data to/from this card and we
suspect an IRQ related issue. For example, loading our (good old) "pcan"
driver leads to the below logs:
...
[ 6.186877] pci 0000:00:1e.0: can't derive routing for PCI INT A
[ 6.186878] pcan 0000:04:08.0: PCI INT A: no GSI - using ISA IRQ 11
...
My questions are:
- why does the system not succeed to "derive" routing for INTA? And why
us? ;-)
At first glance it would appear that there's some kind of ACPI/PCI IRQ
routing problem on that system. Does the card work in another machine?
Or does a different card work in the same slot on this machine?
- since the system looks like it switched in old "ISA" mode, should the
driver run differently (IRQ not shared, for example) or is this
transparently handled by the Kernel?
I imagine what's happening is that based on some information the kernel
has decided to try using IRQ 11, but if there's no IRQ routing known
then the kernel may not know how to actually enable the PCI interrupt
link to actually allow the interrupts to be received.
(implied question: how to fix this problem?)
Many thanks for your time and your help,
Stéphane Grosjean
--
PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt
Geschaeftsleitung: A.Gach/U.Wilhelm,St.Nr.:007/241/13586 FA Darmstadt
HRB-9183 Darmstadt, Ust.IdNr.:DE 202220078, WEE-Reg.-Nr.: DE39305391
Tel.+49 (0)6151-817320 / Fax:+49 (0)6151-817329, info@xxxxxxxxxxxxxxx
----
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
