All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: paulmck@linux.vnet.ibm.com,
	"David S. Miller" <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: rhashtable: hang while running tests on boot
Date: Sat, 11 Oct 2014 19:41:41 -0400	[thread overview]
Message-ID: <5439C035.8020208@oracle.com> (raw)
In-Reply-To: <20141011222615.GB14186@casper.infradead.org>

On 10/11/2014 06:26 PM, Thomas Graf wrote:
> On 10/11/14 at 12:09pm, Sasha Levin wrote:
>> On 10/11/2014 11:50 AM, Paul E. McKenney wrote:
>>>>>>> I am guessing that this happens only when running the resizable hashtable
>>>>>>> tests -- if that guess is incorrect, please let me know.
>>>>>
>>>>> I've seen it a few times only with rhashtable related traces, if that ever
>>>>> changes I'll update - but for now I think it's safe to assume it's rhashtable
>>>>> specific.
>>> Ah, so this is intermittent.  Joy.
>>
>> Yup, I'm seeing it in about 10% of boot attempts.
> 
> Have you ever seen any traces outside of the test_rht code?  I'm
> trying to figure out whether it's a bug in the test code or in the
> hash table itself.

There are odd RCU lockups (one of which is pasted earlier in this thread),
but there's nothing pointing to rht code there, and I'm not seeing any other
rht related issues.


Thanks,
Sasha


  reply	other threads:[~2014-10-11 23:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 13:40 rhashtable: hang while running tests on boot Sasha Levin
2014-10-10 14:22 ` Paul E. McKenney
2014-10-10 14:28   ` Sasha Levin
2014-10-11 15:50     ` Paul E. McKenney
2014-10-11 16:09       ` Sasha Levin
2014-10-11 22:26         ` Thomas Graf
2014-10-11 23:41           ` Sasha Levin [this message]
2014-10-11 12:41   ` Sasha Levin
2014-10-11 15:52     ` Paul E. McKenney
2014-10-11 15:59       ` Sasha Levin

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=5439C035.8020208@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tgraf@suug.ch \
    /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.