From: Boaz Harrosh <bharrosh@panasas.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
LKP <fnstml-lkp@cn.fujitsu.com>,
Fengguang Wu <fengguang.wu@intel.com>,
<linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall()
Date: Mon, 25 Nov 2013 16:32:19 +0200 [thread overview]
Message-ID: <52935F73.4090209@panasas.com> (raw)
In-Reply-To: <CAFLxGvynVV=aY755xTPTa7-57O25Dwzc+cbWELj+4xxFKznKMg@mail.gmail.com>
On 11/25/2013 04:15 PM, Richard Weinberger wrote:
> On Fri, Nov 22, 2013 at 7:02 AM, Yuanhan Liu
> <yuanhan.liu@linux.intel.com> wrote:
>> Greetings,
>>
>> I got the below dmesg and the first bad commit is
>>
>> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
>> Author: Boaz Harrosh <bharrosh@panasas.com>
>> Date: Thu Jul 19 15:22:37 2012 +0300
>>
>> RFC: do_xor_speed Broken on UML do to jiffies
>>
>> Remember that hang I reported a while back on UML. Well
>> I'm at it again, and it still hangs and I found why.
>>
>> I have dprinted jiffies and it never advances during the
>> loop at do_xor_speed. There for it is stuck in an endless
>> loop. I have also dprinted current_kernel_time() and it
>> returns the same constant value as well.
>>
>> Note that it does usually work on UML, only during
>> the modprobe of xor.ko while that test is running. It looks
>> like some lucking is preventing the clock from ticking.
>>
>> However ktime_get_ts does work for me so I changed the code
>> as below, so I can work. See how I put several safety
>> guards, to never get hangs again.
>> And I think my time based approach is more accurate then
>> previous system.
>>
>> UML guys please investigate the jiffies issue? what is
>> xor.ko not doing right?
>
> This patch never hit my mailbox...
>
>> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
>>
Sir Richard
I never followed on this patch. Sorry. I do think it is in
the right direction, but it has a dev-by-zero problem and
a 32 bitness problem. (So I never sent it, beyond the initial
query)
[It stopped to be very important for me since I stopped using
UM very much. Ever since FC17 I'm unable to produce a running
image. It just will not boot, an image that a kvm would. So
very sad me, but no UML for me anymore.]
If you want to investigate. try doing a modprobe xor.ko on
a uml and see. since xor.ko is only built on demand for example
enabling exofs or object-layout-driver will select it. ,or MD-raid5.
Thanks
Boaz
next prev parent reply other threads:[~2013-11-25 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 6:02 WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall() Yuanhan Liu
2013-11-25 10:43 ` Boaz Harrosh
2013-11-25 13:25 ` Yuanhan Liu
2013-11-25 13:57 ` Boaz Harrosh
2013-11-26 10:37 ` Yuanhan Liu
2013-11-26 10:54 ` Boaz Harrosh
2013-11-25 14:15 ` Richard Weinberger
2013-11-25 14:32 ` Boaz Harrosh [this message]
2013-11-25 14:43 ` Richard Weinberger
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=52935F73.4090209@panasas.com \
--to=bharrosh@panasas.com \
--cc=fengguang.wu@intel.com \
--cc=fnstml-lkp@cn.fujitsu.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=yuanhan.liu@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox