From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: acpi devel <linux-acpi@vger.kernel.org>
Cc: Stian Jordet <liste@jordet.net>
Subject: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ?
Date: Thu, 14 Sep 2006 20:43:13 +0100 [thread overview]
Message-ID: <1158262993.4200.14.camel@localhost.localdomain> (raw)
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
>
next reply other threads:[~2006-09-14 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 19:43 Sergio Monteiro Basto [this message]
2006-09-22 0:32 ` ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11, why not in 9 ? Stian Jordet
2006-09-25 3:42 ` Randy Dunlap
2006-09-25 10:22 ` Sergio Monteiro Basto
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=1158262993.4200.14.camel@localhost.localdomain \
--to=sergio@sergiomb.no-ip.org \
--cc=linux-acpi@vger.kernel.org \
--cc=liste@jordet.net \
/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.