From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Stefan Bader <stefan@krikkit.de>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: Booting dom0, various issues since v3.16 kernels
Date: Thu, 5 Feb 2015 14:56:20 -0500 [thread overview]
Message-ID: <20150205195619.GC16042@l.oracle.com> (raw)
In-Reply-To: <73492960.20150205154711@eikelenboom.it>
On Thu, Feb 05, 2015 at 03:47:11PM +0100, Sander Eikelenboom wrote:
>
> Thursday, February 5, 2015, 3:22:49 PM, you wrote:
>
> > Hey David,
>
> > after just being in that pain, I thought I might as well give a summary to
> > you/the list. Maybe helpful to not forget which piece should go to which stable...
>
> > So:
> > v3.16...v3.17.8: Somewhen in between those, the acpi irq seems to have broken.
> > I have not yet verified that, but at least three changes in
> > 3.19-rc6 seem to look related:
>
> > * "x86/xen: Treat SCI interrupt as normal GSI interrupt",
> > * "ACPI: pci: Do not clear pci_dev->irq in acpi_pci_irq_disable()", and
> > * "x86/xen: Override ACPI IRQ management callback __acpi_unregister_gsi"
>
> Yes Jiang Liu fixed those and said he would backport the required fixes once
> they where accepted in mainline, put perhaps a polite ping is necessary there.
Would you be OK pinging him please?
>
> > v3.17.8...v3.18.4: Beside the acpi interrupt, no USB devices (beyond the
> > hubs) get initialized. Not sure what fixed it, but it
> > looks ok in v3.19-rc7.
> > Beside that, there also was a regression in swiotlb
> > that I think was passed on to some stable maintainers:
>
> Probably the same issue as above (for me it fixed a powerbutton issue and some
> pci-passthrough problems).
>
> And there seems to be more refactoring coming for 3.20 .. so fingerscrossed.
>
> --
> Sander
>
> > * "Revert "swiotlb-xen: pass dev_addr to swiotlb_tbl_unmap_single""
>
> > v3.18.4..v3.19-rc7: The issues above look to be fixed. Only some Haswell
> > based box now crashed on boot as dom0 while parsing
> > some ACPI tables (will send more detail seperately).
> > This happens only on that host and only when running
> > as dom0. Bare-metal is ok and an Opteron based different
> > host is also fine.
>
> > -Stefan
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-02-05 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 14:22 Booting dom0, various issues since v3.16 kernels Stefan Bader
2015-02-05 14:47 ` Sander Eikelenboom
2015-02-05 19:56 ` Konrad Rzeszutek Wilk [this message]
2015-02-09 9:31 ` Stefan Bader
2015-02-09 9:36 ` Sander Eikelenboom
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=20150205195619.GC16042@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux@eikelenboom.it \
--cc=stefan@krikkit.de \
--cc=xen-devel@lists.xensource.com \
/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.