xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ben Guthro <ben@guthro.net>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: dump with xen-unstable & linux 3.2.17
Date: Tue, 22 May 2012 13:34:03 -0400	[thread overview]
Message-ID: <20120522173403.GD19601@phenom.dumpdata.com> (raw)
In-Reply-To: <CAOvdn6UrJcmrKMJTUcuvwjKW_VqZnvWCJWsUfiSTR1eUWT4kiw@mail.gmail.com>

On Tue, May 22, 2012 at 12:21:20PM -0400, Ben Guthro wrote:
> good point.
> 
> I'll continue to try to figure this out - but if you have anything
> specific I can try (particular boot options, or a patch with extra
> debugging in interesting areas) please let me know, as it is 100%
> reproducible in my environment right now.

So.. you mentioned that you are using the serial console and that
there were some changes in the hypervisor to deal with the serial console.

I sent to xen-devel some of the patches that you guys had (with
proper authorship) - especially the one dealing with PCI serial cards.
Jan found that one of them had an simple mistake of trying to use
the ports before they were initialized and fixed that in xen-unstable.
Perhaps that is missing?

> 
> -Ben
> 
> On Tue, May 22, 2012 at 12:08 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>> On 22.05.12 at 17:38, Ben Guthro <ben@guthro.net> wrote:
> >> I still suspect this is something my dom0 kernel is doing incorrectly,
> >> but I don't have much to back that up other than a gut feeling.
> >
> > If the Dom0 kernel can affect the scheduler in this way, then
> > quite likely a DomU kernel can too. And even if not, it's still a
> > problem - the scheduler just shouldn't be susceptible.
> >
> > Jan
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-05-22 17:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 21:20 dump with xen-unstable & linux 3.2.17 Ben Guthro
2012-05-21 14:55 ` Jan Beulich
2012-05-21 19:12   ` Ben Guthro
2012-05-21 19:49     ` Ben Guthro
2012-05-22 15:38       ` Ben Guthro
2012-05-22 16:08         ` Jan Beulich
2012-05-22 16:21           ` Ben Guthro
2012-05-22 17:34             ` Konrad Rzeszutek Wilk [this message]
2012-05-22 17:55               ` Ben Guthro
2012-05-22 18:00                 ` Konrad Rzeszutek Wilk
2012-05-22 18:26                   ` Ben Guthro
2012-05-22 21:00                     ` Ben Guthro
2012-05-23  9:39                       ` Jan Beulich
2012-05-23 11:00                         ` Juergen Gross
2012-05-25 13:20                           ` Ben Guthro
2012-05-31 15:52                             ` Ben Guthro
2012-05-31 16:06                               ` Jan Beulich
2012-05-31 16:18                                 ` Ben Guthro
2012-06-01  6:54                                 ` Dietmar Hahn

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=20120522173403.GD19601@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=ben@guthro.net \
    --cc=xen-devel@lists.xen.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).