From: Johannes Berg <johannes@sipsolutions.net>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: UML time-travel warning from __run_timers
Date: Wed, 30 Mar 2022 14:33:23 +0200 [thread overview]
Message-ID: <c1ff43de7d64831d8f40e8e11177f005b9940050.camel@sipsolutions.net> (raw)
In-Reply-To: <20220330110156.GA9250@axis.com>
On Wed, 2022-03-30 at 13:01 +0200, Vincent Whitchurch wrote:
> Hello Johannes,
>
> As requested in the roadtest thread[0], here is some information about
> reproducing the warnings I'm seeing from the timekeeping code with time
> travel in UML, after about 10-20 wall time seconds of idling.
>
> [0] https://lore.kernel.org/lkml/5b39d572e619c812109af7a1b8028bfb8353efda.camel@sipsolutions.net/
>
> The warning is the WARN_ON_ONCE(!levels && !base->next_expiry_recalc) in
> __run_timers(). The log and the config generated with savedefconfig are
> below. The full .config is attached.
>
> The kernel version is v5.17, but the splats are seen on older kernels
> and on latest mainline also.
>
So interestingly, I cannot reproduce it with my config (it's already
March 2023), but I can with yours ...
johannes
next prev parent reply other threads:[~2022-03-30 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 11:01 Vincent Whitchurch
2022-03-30 12:33 ` Johannes Berg [this message]
2022-04-02 14:09 ` Johannes Berg
2022-04-02 14:17 ` Johannes Berg
2022-04-03 16:18 ` Thomas Gleixner
2022-04-03 17:13 ` Johannes Berg
2022-04-03 17:19 ` Johannes Berg
2022-04-03 23:23 ` Thomas Gleixner
2022-04-03 19:51 ` Thomas Gleixner
2022-04-04 7:02 ` Johannes Berg
2022-04-04 8:32 ` Thomas Gleixner
2022-04-04 8:37 ` Johannes Berg
2022-04-04 12:17 ` Thomas Gleixner
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=c1ff43de7d64831d8f40e8e11177f005b9940050.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=vincent.whitchurch@axis.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
all inboxes | Powered by JetHome®