* ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ?
@ 2006-09-14 19:43 Sergio Monteiro Basto
2006-09-22 0:32 ` Stian Jordet
0 siblings, 1 reply; 4+ messages in thread
From: Sergio Monteiro Basto @ 2006-09-14 19:43 UTC (permalink / raw)
To: acpi devel; +Cc: Stian Jordet
drivers/acpi/pci_link.c, line #583
acpi_irq_penalty[link->irq.active] += PIRQ_PENALTY_PCI_USING;
printk(PREFIX "%s [%s] enabled at IRQ %d\n",
acpi_device_name(link->device),
acpi_device_bid(link->device), link->irq.active);
any clue about this problem ?
-------- Forwarded Message --------
From: Sergio Monteiro Basto
Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
Date: Wed, 13 Sep 2006 01:48:28 +0100
On Tue, 2006-09-12 at 23:38 +0200, Stian Jordet wrote:
> On tir, 2006-09-12 at 13:37 +0100, Sergio Monteiro Basto wrote:
> > Ok, as a quick answer, you have a very primitive VIA SMP board, which
> > make me remember my old laptop.
> > I maintain what a had write in previous emails about this system.
> > Seeing the configuration of irqs on windows, USB are in 9, so could be a
> > clue.
> > If I had your board, I'll try not quirk USB (cause quirk put USB in 11)
> > and make USB interrupts work as IO-APIC-edge.
> > 9: nnnn nnnn IO-APIC-edge uhci_hcd:usb1, uhci_hcd:usb2,
> > uhci_hcd:usb3
>
> The point is, that even when I do not quirk (just insert return at the
> top of the quirk-function), usb still uses irq 11 (as I wrote here:
> http://lkml.org/lkml/2006/9/6/49 ), but won't work. And acpi (on
> interrupt 9) gets an interrupt storm, and gets disabled.
>
Good point , you got on your dmesg of kernel 2.6.18-rc6
(http://lkml.org/lkml/2006/9/10/120)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: VIA IRQ fixup for 0000:00:11.2, from 9 to 11
uhci_hcd 0000:00:11.2: UHCI Host Controller
uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:11.2: irq 11, io base 0x00009800
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
but before
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
LNKD was on 9, so may be the bug is on ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
you have to investigate :)
Further more, your interrupts have 4 steps
ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
and mine just got 3
ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 201
> But if I somehow got usb using irq 9, all my problems might vanish...
>
> -Stian
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ?
2006-09-14 19:43 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ? Sergio Monteiro Basto
@ 2006-09-22 0:32 ` Stian Jordet
2006-09-25 3:42 ` Randy Dunlap
0 siblings, 1 reply; 4+ messages in thread
From: Stian Jordet @ 2006-09-22 0:32 UTC (permalink / raw)
To: Sergio Monteiro Basto; +Cc: acpi devel
tor, 14,.09.2006 kl. 20.43 +0100, skrev Sergio Monteiro Basto:
> drivers/acpi/pci_link.c, line #583
> acpi_irq_penalty[link->irq.active] += PIRQ_PENALTY_PCI_USING;
> printk(PREFIX "%s [%s] enabled at IRQ %d\n",
> acpi_device_name(link->device),
> acpi_device_bid(link->device), link->irq.active);
>
> any clue about this problem ?
I think you might be on to something here, but doesn't seem like anyone
with the right skills has anything to add :( But it seems obvious that
it's somewhat related to the fact that LNKD is enabled on irq11, even
though it seems like it should have been irq9. Weird, but I don't
understand nada :(
Thanks for looking into it, though.
-Stian
> -------- Forwarded Message --------
> From: Sergio Monteiro Basto
> Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
> Date: Wed, 13 Sep 2006 01:48:28 +0100
>
> On Tue, 2006-09-12 at 23:38 +0200, Stian Jordet wrote:
> > On tir, 2006-09-12 at 13:37 +0100, Sergio Monteiro Basto wrote:
> > > Ok, as a quick answer, you have a very primitive VIA SMP board, which
> > > make me remember my old laptop.
> > > I maintain what a had write in previous emails about this system.
> > > Seeing the configuration of irqs on windows, USB are in 9, so could be a
> > > clue.
> > > If I had your board, I'll try not quirk USB (cause quirk put USB in 11)
> > > and make USB interrupts work as IO-APIC-edge.
> > > 9: nnnn nnnn IO-APIC-edge uhci_hcd:usb1, uhci_hcd:usb2,
> > > uhci_hcd:usb3
> >
> > The point is, that even when I do not quirk (just insert return at the
> > top of the quirk-function), usb still uses irq 11 (as I wrote here:
> > http://lkml.org/lkml/2006/9/6/49 ), but won't work. And acpi (on
> > interrupt 9) gets an interrupt storm, and gets disabled.
> >
>
> Good point , you got on your dmesg of kernel 2.6.18-rc6
> (http://lkml.org/lkml/2006/9/10/120)
>
> USB Universal Host Controller Interface driver v3.0
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> PCI: VIA IRQ fixup for 0000:00:11.2, from 9 to 11
> uhci_hcd 0000:00:11.2: UHCI Host Controller
> uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
> uhci_hcd 0000:00:11.2: irq 11, io base 0x00009800
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 2 ports detected
>
> but before
>
> ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
>
> LNKD was on 9, so may be the bug is on ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> you have to investigate :)
>
> Further more, your interrupts have 4 steps
> ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> and mine just got 3
> ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 201
>
> > But if I somehow got usb using irq 9, all my problems might vanish...
> >
> > -Stian
> >
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ?
2006-09-22 0:32 ` Stian Jordet
@ 2006-09-25 3:42 ` Randy Dunlap
2006-09-25 10:22 ` Sergio Monteiro Basto
0 siblings, 1 reply; 4+ messages in thread
From: Randy Dunlap @ 2006-09-25 3:42 UTC (permalink / raw)
To: Stian Jordet; +Cc: Sergio Monteiro Basto, acpi devel
On Fri, 22 Sep 2006 02:32:11 +0200 Stian Jordet wrote:
> tor, 14,.09.2006 kl. 20.43 +0100, skrev Sergio Monteiro Basto:
> > drivers/acpi/pci_link.c, line #583
> > acpi_irq_penalty[link->irq.active] += PIRQ_PENALTY_PCI_USING;
> > printk(PREFIX "%s [%s] enabled at IRQ %d\n",
> > acpi_device_name(link->device),
> > acpi_device_bid(link->device), link->irq.active);
> >
> > any clue about this problem ?
>
> I think you might be on to something here, but doesn't seem like anyone
> with the right skills has anything to add :( But it seems obvious that
> it's somewhat related to the fact that LNKD is enabled on irq11, even
> though it seems like it should have been irq9. Weird, but I don't
> understand nada :(
You should probably file a bug in the kernel bugzilla at
http://kernel.bugzilla.org and provides lots of info.
> Thanks for looking into it, though.
>
> -Stian
>
>
> > -------- Forwarded Message --------
> > From: Sergio Monteiro Basto
> > Subject: Re: [PATCH V3] VIA IRQ quirk behaviour change
> > Date: Wed, 13 Sep 2006 01:48:28 +0100
> >
> > On Tue, 2006-09-12 at 23:38 +0200, Stian Jordet wrote:
> > > On tir, 2006-09-12 at 13:37 +0100, Sergio Monteiro Basto wrote:
> > > > Ok, as a quick answer, you have a very primitive VIA SMP board, which
> > > > make me remember my old laptop.
> > > > I maintain what a had write in previous emails about this system.
> > > > Seeing the configuration of irqs on windows, USB are in 9, so could be a
> > > > clue.
> > > > If I had your board, I'll try not quirk USB (cause quirk put USB in 11)
> > > > and make USB interrupts work as IO-APIC-edge.
> > > > 9: nnnn nnnn IO-APIC-edge uhci_hcd:usb1, uhci_hcd:usb2,
> > > > uhci_hcd:usb3
> > >
> > > The point is, that even when I do not quirk (just insert return at the
> > > top of the quirk-function), usb still uses irq 11 (as I wrote here:
> > > http://lkml.org/lkml/2006/9/6/49 ), but won't work. And acpi (on
> > > interrupt 9) gets an interrupt storm, and gets disabled.
> > >
> >
> > Good point , you got on your dmesg of kernel 2.6.18-rc6
> > (http://lkml.org/lkml/2006/9/10/120)
> >
> > USB Universal Host Controller Interface driver v3.0
> > ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> > ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> > PCI: VIA IRQ fixup for 0000:00:11.2, from 9 to 11
> > uhci_hcd 0000:00:11.2: UHCI Host Controller
> > uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
> > uhci_hcd 0000:00:11.2: irq 11, io base 0x00009800
> > usb usb1: configuration #1 chosen from 1 choice
> > hub 1-0:1.0: USB hub found
> > hub 1-0:1.0: 2 ports detected
> >
> > but before
> >
> > ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
> >
> > LNKD was on 9, so may be the bug is on ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
> > you have to investigate :)
> >
> > Further more, your interrupts have 4 steps
> > ACPI: PCI Interrupt 0000:00:11.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
> > and mine just got 3
> > ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 201
> >
> > > But if I somehow got usb using irq 9, all my problems might vanish...
> > >
> > > -Stian
---
~Randy
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ?
2006-09-25 3:42 ` Randy Dunlap
@ 2006-09-25 10:22 ` Sergio Monteiro Basto
0 siblings, 0 replies; 4+ messages in thread
From: Sergio Monteiro Basto @ 2006-09-25 10:22 UTC (permalink / raw)
To: Randy Dunlap; +Cc: Stian Jordet, acpi devel
On Monday 25 September 2006 04:42, Randy Dunlap wrote:
> You should probably file a bug in the kernel bugzilla at
> http://kernel.bugzilla.org and provides lots of info.
Is already in bubzilla
http://bugzilla.kernel.org/show_bug.cgi?id=2874#c22
Thanks,
--
Sérgio M. B.
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-09-25 10:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-14 19:43 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ? Sergio Monteiro Basto
2006-09-22 0:32 ` Stian Jordet
2006-09-25 3:42 ` Randy Dunlap
2006-09-25 10:22 ` Sergio Monteiro Basto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox