mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: RT-Kernel boot stalls because of change in fs/dcache.c
Date: Wed, 19 Dec 2018 13:46:34 +0000	[thread overview]
Message-ID: <d9448930-e466-864a-41ce-08bf4588d0d1@kontron.de> (raw)
In-Reply-To: <20181219113650.ak3wj3h3oapfy3tj@linutronix.de>

Hi Sebastian,

On 19.12.18 12:36, Sebastian Andrzej Siewior wrote:
> On 2018-12-19 07:50:17 [+0000], Schrempf Frieder wrote:
>> + linux-rt-users
>>
>> On 17.12.18 11:42, Frieder Schrempf wrote:
>>> Hi,
>>>
>>> I have tried to boot a 4.14-Kernel with the RT-patches and
>>> PREEMPT_RT_FULL on an i.MX6UL board. Unfortunately the boot stalls at
>>> some point and never finishes.
>>>
>>> I did some bisecting and found out, that reverting this change: [1],
>>> makes the board boot correctly.
>>>
>>> Can anyone help to come up with a proper fix for this?
> 
> can you check if the hashtable is initialized twice?

I'm not sure how to check, but I guess you are on the right track. I can 
leave the init loop for dentry_hashtable in place and remove the one for 
in_lookup_hashtable in vfs_caches_init_early() and this also makes the 
board boot.

Could it be, that the initializing for dentry_hashtable and 
in_lookup_hashtable somehow interfere?

Thanks for your help,
Frieder

> 
>>> Thanks,
>>> Frieder
>>>
>>> [1]:
>>> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v4.14-rt&id=56684d21f7f8341f7a5ed1433714112f49294590
> 
> Sebastian
> 

  reply	other threads:[~2018-12-19 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 10:42 Schrempf Frieder
2018-12-19  7:50 ` Schrempf Frieder
2018-12-19 11:36   ` Sebastian Andrzej Siewior
2018-12-19 13:46     ` Schrempf Frieder [this message]
2018-12-19 17:24       ` Schrempf Frieder

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=d9448930-e466-864a-41ce-08bf4588d0d1@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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

all inboxes | Powered by JetHome®