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 17:24:30 +0000 [thread overview]
Message-ID: <9d9c55d7-cc62-8c84-1782-e49929e58adf@kontron.de> (raw)
In-Reply-To: <d9448930-e466-864a-41ce-08bf4588d0d1@kontron.de>
On 19.12.18 14:46, Frieder Schrempf wrote:
> 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?
So the source of the issue turned out to be completely unrelated to
this. Although it seems like enabling PREEMPT_RT_FULL triggered the
problem in my case.
The lockup of the kernel was caused by the SNVS RTC driver. Pulling in
this patch: [1], solved the problem.
As this patch fixes a real bug I sent a request for it to be backported
to the stable releases.
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd7f3a249dbed2858e6c2f30e5be7f1f7a709ee2
>>>>
>>>> [1]:
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v4.14-rt&id=56684d21f7f8341f7a5ed1433714112f49294590
>>>>
>>
>> Sebastian
>>
prev parent reply other threads:[~2018-12-19 17:24 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
2018-12-19 17:24 ` Schrempf Frieder [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=9d9c55d7-cc62-8c84-1782-e49929e58adf@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®