All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <gqjiang@suse.com>
To: yizhan <yizhan@redhat.com>, linux-raid@vger.kernel.org
Subject: Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
Date: Wed, 3 Aug 2016 10:46:48 +0800	[thread overview]
Message-ID: <57A15B18.80305@suse.com> (raw)
In-Reply-To: <bd2bb3a9-f970-7726-00b7-1956d2223ef1@redhat.com>



On 08/02/2016 09:31 PM, yizhan wrote:
>
>> I tried with latest Linus's tree 
>> (731c7d3a205ba89b475b2aa71b5f13dd6ae3de56), but still can't find the 
>> warning.
>>
>> linux241:~ # uname -r
>> 4.7.0-11-default+
>> linux241:~ # mdadm --version
>> mdadm - v3.4-41-gf96b130 - 30th March 2016
>>
>> The biggest difference is that I am using VM machine while you were 
>> testing with real hardware, though I am not
>> sure it was caused by hardware or not. Do you always see the 
>> "couldn't update array info" info during test? If so,
>> pls try to make it disappear.
>>
>> Thanks,
>> Guoqing
> May be it's env related, I have tried on another PC which with the 
> same kernel/mdadm version and cannot reproduce it.

I guess you can check the difference of hardware about why it can't be 
happen with another PC.

Regards,
Guoqing

      reply	other threads:[~2016-08-03  2:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1382969797.9407100.1469619450040.JavaMail.zimbra@redhat.com>
2016-07-27 11:38 ` WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456] Yi Zhang
2016-07-28  1:13   ` Shaohua Li
2016-08-01  9:01   ` Guoqing Jiang
     [not found]   ` <579F0E52.8090704@suse.com>
2016-08-01 12:32     ` Yi Zhang
     [not found]     ` <7d0acb42-1209-0722-7740-0fa03d44106b@redhat.com>
2016-08-02  8:36       ` Guoqing Jiang
2016-08-02 13:31         ` yizhan
2016-08-03  2:46           ` Guoqing Jiang [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=57A15B18.80305@suse.com \
    --to=gqjiang@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=yizhan@redhat.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.