From: Boaz Harrosh <bharrosh@panasas.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: initcall calibrate_xor_blocks returned with preemption imbalance
Date: Fri, 11 Oct 2013 11:42:39 -0700 [thread overview]
Message-ID: <5258469F.9070108@panasas.com> (raw)
In-Reply-To: <20131011012936.GB11191@localhost>
On 10/10/2013 06:29 PM, Fengguang Wu wrote:
>
> I'm running kernel build/boot/performance tests for *all* the public
> kernel git trees I'm aware of. If this is not necessary for your tree
> or some of the branches, sorry I can remove them from the test pool.
>
>> I can see below:
>> Merge 'open-osd/exofs_ioctl' into devel-hourly-2013101007
>>
OK then there you have it then. Yes exofs_ioctl is a testing branch
that I also use with UML. And there for must carry this unfinished
patch.
Thankyou for the bisect. I will take this crash report and put
it on my todo for fixing the xor stuckness.
Have a good day
Boaz
prev parent reply other threads:[~2013-10-11 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 9:02 initcall calibrate_xor_blocks returned with preemption imbalance Fengguang Wu
2013-10-10 20:41 ` Boaz Harrosh
2013-10-11 1:29 ` Fengguang Wu
2013-10-11 18:42 ` Boaz Harrosh [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=5258469F.9070108@panasas.com \
--to=bharrosh@panasas.com \
--cc=fengguang.wu@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).