From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Subject: Re: Xen 4 serial hangs during boot
Date: Thu, 26 Jul 2012 10:36:22 -0400 [thread overview]
Message-ID: <20120726143622.GF28024@phenom.dumpdata.com> (raw)
In-Reply-To: <50116BF102000078000909D1@nat28.tlf.novell.com>
On Thu, Jul 26, 2012 at 03:10:25PM +0100, Jan Beulich wrote:
> >>> On 26.07.12 at 15:50, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > Then recently (yesterday?) the upstream kernel started doing something
> > wonky on this card:
> >
> > 01:05.0 Serial controller: NetMos Technology PCI 9835 Multi-I/O Controller
> > (rev 01)
> > Under Xen, when it boots it hits right here:
> > [ 1.240774] pci 0000:01:05.0: [9710:9835] type 00 class 0x070002
> > and then stops [note: I hadn't really done any investigation to see
> > if the machine is dead or if it continues on, but with the serial port just
> > wedged hard].
>
> The machine state here, if accessible at all, would of course be
> very interesting.
<nods> Hope to get to that today.
>
> > On baremetal it can actually read the IO bars:
> > [ 1.240774] pci 0000:01:05.0: [9710:9835] type 00 class 0x070002
> > [ 1.247075] pci 0000:01:05.0: reg 10: [io 0xe050-0xe057]
> > [ 1.252734] pci 0000:01:05.0: reg 14: [io 0xe040-0xe047]
> > [ 1.258394] pci 0000:01:05.0: reg 18: [io 0xe030-0xe037]
> > [ 1.264054] pci 0000:01:05.0: reg 1c: [io 0xe020-0xe027]
> > [ 1.269713] pci 0000:01:05.0: reg 20: [io 0xe010-0xe017]
> > [ 1.275372] pci 0000:01:05.0: reg 24: [io 0xe000-0xe00f]
> >
> > so I am wondering if the back-ports in Xen 4.1 for dealing with
> > PCI have something to do with this?
>
> What backports are you thinking of? I just went through the titles
> of everything since 4.1.2, and nothing that has "PCI" in it looks
> in any way dangerous.
I know :-( That is why I am thinking it might be the kernel, but when
I did a git bisection I got an innocious Documentation patch. But then
recently (say 3.5) has been doing some weird stuff in the PCI space
(like it seems to have MSI's and BARs disabled - at least when using
them with xen-pciback to hide them).
>
> Jan
next prev parent reply other threads:[~2012-07-26 14:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 19:34 Xen 4 occasionally hangs during boot Christopher S. Aker
2011-10-13 7:04 ` Jan Beulich
2011-10-13 10:46 ` Tim Deegan
2012-07-20 17:48 ` Xen 4 serial " Christopher S. Aker
2012-07-20 17:49 ` Andrew Cooper
2012-07-20 17:58 ` Christopher S. Aker
2012-07-20 18:05 ` Andrew Cooper
2012-07-20 19:10 ` Christopher S. Aker
2012-07-20 19:25 ` Andrew Cooper
2012-07-20 19:31 ` Keir Fraser
2012-07-20 19:44 ` Christopher S. Aker
2012-07-20 19:59 ` Keir Fraser
2012-07-23 14:13 ` Konrad Rzeszutek Wilk
2012-07-23 15:26 ` Keir Fraser
2012-07-23 20:53 ` Christopher S. Aker
2012-07-23 22:03 ` Malcolm Crossley
2012-07-23 22:45 ` Malcolm Crossley
2012-07-24 9:40 ` Andrew Cooper
2012-07-24 10:32 ` Jan Beulich
2012-07-26 13:50 ` Konrad Rzeszutek Wilk
2012-07-26 14:10 ` Jan Beulich
2012-07-26 14:36 ` Konrad Rzeszutek Wilk [this message]
2012-07-24 10:46 ` Jan Beulich
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=20120726143622.GF28024@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--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.