From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [linux bisection] complete test-amd64-i386-win
Date: Fri, 03 Dec 2010 08:24:04 -0800 [thread overview]
Message-ID: <4CF919A4.5020203@goop.org> (raw)
In-Reply-To: <19705.6016.117795.795380@mariner.uk.xensource.com>
On 12/03/2010 08:14 AM, Ian Jackson wrote:
> Ian Jackson writes ("[linux bisection] complete test-amd64-i386-win"):
>> *** Found and reproduced problem changeset ***
>>
>> Bug is in tree: git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> ...
>> commit efa6c814f5fe72f74cdcd60da13e67ec9fc34fc9
>> Merge: b92d1ec... 5dca841...
>> Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>> Date: Thu Dec 2 15:37:19 2010 -0800
>>
>> Merge branch 'xen/next' into xen/next-2.6.32
> This seems to be a real bug, with oopses in the dom0 serial kernel
> logs. See for example:
>
> http://www.chiark.greenend.org.uk/~xensrcts/logs/2964/test-amd64-i386-xl/info.html
> http://www.chiark.greenend.org.uk/~xensrcts/logs/2964/test-amd64-i386-xl/serial-itch-mite.log
>
> Two multicall failure WARNINGs and then a BUG.
OK. I reverted the commit that would have caused this, since it was a
bit incomplete and not really necessary for .32 anyway.
J
prev parent reply other threads:[~2010-12-03 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 15:23 [linux bisection] complete test-amd64-i386-win xen.org
2010-12-03 16:14 ` Ian Jackson
2010-12-03 16:24 ` Jeremy Fitzhardinge [this message]
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=4CF919A4.5020203@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.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.