From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [1/3] Revert "ACPI,PCI,IRQ: reduce static IRQ array size to 16"
Date: Sun, 2 Oct 2016 21:07:21 -0400 [thread overview]
Message-ID: <bf16b077-603f-bc7e-cd7b-bf006242f781@codeaurora.org> (raw)
In-Reply-To: <CANwerB2bhMbkQrGG55Bq-yrFk_DC3Pz2tF0CRrt4ccmrzTmrzQ@mail.gmail.com>
On 10/2/2016 7:40 AM, Jonathan Liu wrote:
> This series fixes one or more network adapters in VirtualBox not
> working with Linux 32-bit x86 guest if I have 4 network adapters
> enabled. The following message no longer appears in the kernel log:
> ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off
>
> Tested-by: Jonathan Liu <net147@gmail.com>
Thanks for the test. I didn't realize that VirtualBox was broken too.
So far I got some random test results in the mail list that something
is broken. I hope to hear more that we close the issue for some time
now.
The IRQ stuff got broken three times already. Hopefully, this will be
the seal.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2016-10-03 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 17:46 [PATCH 1/3] Revert "ACPI, PCI, IRQ: reduce static IRQ array size to 16" Sinan Kaya
2016-10-01 17:46 ` [PATCH 2/3] ACPI, PCI IRQ: add PCI_USING penalty for ISA interrupts Sinan Kaya
2016-10-02 11:40 ` [2/3] " Jonathan Liu
2016-10-01 17:46 ` [PATCH 3/3] Revert "ACPI,PCI,IRQ: remove SCI penalize function" Sinan Kaya
2016-10-02 11:40 ` [3/3] " Jonathan Liu
2016-10-04 7:23 ` [PATCH 3/3] " Thomas Gleixner
2016-10-04 14:10 ` Sinan Kaya
2016-10-04 14:23 ` Thomas Gleixner
2016-10-02 11:40 ` [1/3] Revert "ACPI,PCI,IRQ: reduce static IRQ array size to 16" Jonathan Liu
2016-10-03 1:07 ` Sinan Kaya [this message]
2016-10-03 8:03 ` Jonathan Liu
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=bf16b077-603f-bc7e-cd7b-bf006242f781@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).