All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adi Kriegisch <adi@cg.tuwien.ac.at>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, Adi Kriegisch <adi@cg.tuwien.ac.at>
Subject: Re: Re: Dom0 ACPI S3 patches
Date: Thu, 15 Sep 2011 15:18:31 +0200	[thread overview]
Message-ID: <20110915131831.GA7204@vrvis.at> (raw)
In-Reply-To: <20110914154726.GA18810@phenom.oracle.com>

On Wed, Sep 14, 2011 at 11:47:26AM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Sep 14, 2011 at 05:09:34PM +0200, Adi Kriegisch wrote:
> > On Wed, Sep 14, 2011 at 10:28:54AM -0400, Konrad Rzeszutek Wilk wrote:
> > > > > Excellent. Is it OK if I put 'Tested-by: Adi Kriegish" on them?
> > > > Sure, go ahead! ;-)
Now, I think, you may really go ahead! ;-) 'nopat' did the trick for me.

> > > Hmmm.. I wonder if you are hitting the writecombine issue I've seen sometimes.
> > > Just to eliminate it, can you try 'nopat' on the Linux command line?
> > Sure. Do you know any way to make sure I am hitting the writecombine issue
> > fast, so that I can make (kind of) sure everything is working?
> Mysterious applications crashing left and right. Under my box bash stopped
> working right and such. Pretty obvious that something went wrong.
Hmmm... I rethought the workloads I had and found a way to reproduce the
crashes -- more or less reliably:
As I did a complete reinstallation of my notebook, I had a lot of data to
copy. The first bunch of sutff was copied on Dom0 -- this was where I
experienced the crashes; not immediately while copying but a little later
(The warnings in the syslog always happened during copying, btw).
Then -- after I basic setup was done -- I used xm block-attach and copied
tons of stuff within a DomU. I did not experience a single crash while
doing so.

Do you want me to do something to further debug the issue? Just tell me
what I could/should try to do! ;-)

> > > > > http://lists.xensource.com/archives/html/xen-devel/2010-02/msg00469.html
> > > > Sounds like it could be related. Shall I apply that patch? If so, which
> > > > hook takes care that the function is called?
[SNIP]
> > It does not apply at all:
> 
> Pfff.. well, I will try to rebase it in a couple of days. Can you ping in a week
> if I haven't sent anything to you yet?
Yes, I will! ;-)

-- Adi

  reply	other threads:[~2011-09-15 13:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14  8:11 Dom0 ACPI S3 patches Adi Kriegisch
2011-09-14  8:41 ` Jan Beulich
2011-09-14 17:44   ` Jeremy Fitzhardinge
2011-09-14 10:21 ` Konrad Rzeszutek Wilk
2011-09-14 13:17   ` Adi Kriegisch
     [not found]   ` <20110914112718.GG3079@vrvis.at>
2011-09-14 14:28     ` Konrad Rzeszutek Wilk
2011-09-14 15:09       ` Adi Kriegisch
2011-09-14 15:47         ` Konrad Rzeszutek Wilk
2011-09-15 13:18           ` Adi Kriegisch [this message]
2011-09-27 14:50           ` Adi Kriegisch
2011-09-27 22:26             ` 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=20110915131831.GA7204@vrvis.at \
    --to=adi@cg.tuwien.ac.at \
    --cc=konrad.wilk@oracle.com \
    --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.