From: Bjorn Helgaas <bhelgaas@google.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Jayson A Dyke <jdyke@gdeb.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
michael.d.labriola@gmail.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stuart Wehrly <swehrly@gdeb.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] 3.18 xen-pcifront regression?
Date: Tue, 24 Mar 2015 18:31:39 -0500 [thread overview]
Message-ID: <CAErSpo46hAg7kfEZ9hiNFP1jr=-_L55_iNd0RXXBcO-10G1fDQ@mail.gmail.com> (raw)
In-Reply-To: <OF3F22FEC8.8B4BEFD3-ON85257E12.007A8088-85257E12.007B5FAC@gdeb.com>
On Tue, Mar 24, 2015 at 5:27 PM, Michael D Labriola <mlabriol@gdeb.com> wrote:
> Bjorn Helgaas <bhelgaas@google.com> wrote on 03/24/2015 01:27:02 PM:
>> Thanks for the report, Michael, and sorry for the inconvenience. I
> think
>> the patch below will fix it, but I don't think it's the right fix either
>> because it seems a little ad hoc to sprinkle "acpi_pci_disabled" tests
>> around like fairy dust. I wonder if we can set things up so ACPI
> methods
>> would fail gracefully like they do when ACPI is disabled at
> compile-time.
>>
>> I can boot with "acpi=off" on qemu just fine, and when we look up the
> ACPI
>> device handles, we just get NULL pointers, so everything works out even
>> without a fix like the one below.
>
> FYI, I'm not passing "acpi=off" on the guest's command line... I believe
> it's getting turned off dynamically by the guest kernel. I get the
> following in dmesg within the 1st dozen lines:
>
> ACPI in unprivileged domain disabled
That's from xen_arch_setup(), which prints it when it calls
disable_acpi(). Booting with "acpi=off" also calls disable_acpi(), so
the effect should be similar. But of course xen's PCI enumeration is
started a little differently and my guess is that difference is what
leads to this oops.
Bjorn
next prev parent reply other threads:[~2015-03-24 23:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 15:14 3.18 xen-pcifront regression? Michael D Labriola
2015-03-24 15:28 ` Konrad Rzeszutek Wilk
2015-03-24 17:27 ` Bjorn Helgaas
2015-03-24 17:27 ` [Xen-devel] " Bjorn Helgaas
2015-03-24 22:27 ` Michael D Labriola
2015-03-24 22:27 ` [Xen-devel] " Michael D Labriola
2015-03-24 23:31 ` Bjorn Helgaas [this message]
2015-03-24 23:31 ` Bjorn Helgaas
2015-03-25 20:27 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-03-25 20:40 ` Konrad Rzeszutek Wilk
2015-03-25 20:40 ` Konrad Rzeszutek Wilk
2015-03-25 21:01 ` Michael D Labriola
2015-03-25 20:27 ` Konrad Rzeszutek Wilk
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='CAErSpo46hAg7kfEZ9hiNFP1jr=-_L55_iNd0RXXBcO-10G1fDQ@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=jdyke@gdeb.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=mlabriol@gdeb.com \
--cc=rjw@rjwysocki.net \
--cc=swehrly@gdeb.com \
--cc=xen-devel@lists.xenproject.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 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.