From: Jiri Slaby <jirislaby@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: clocksource: !keventd_up() && schedule_work() == oops
Date: Mon, 14 Sep 2009 11:28:34 +0200 [thread overview]
Message-ID: <4AAE0CC2.5010502@gmail.com> (raw)
In-Reply-To: <4AA760B6.6070601@gmail.com>
On 09/09/2009 10:00 AM, Jiri Slaby wrote:
> Hi,
>
> I started to see oopses on boot in qemu machine because keventd is
> created in kernel_init/do_basic_setup, but schedule_work is done earlier
> in kernel_init/smp_init[1] when the tsc is unstable during this early phase.
>
> It looks like "clocksource: Resolve cpu hotplug dead lock with TSC
> unstable" is the culprit.
>
> Creating its own either singlethread or "multithread" workqueue won't
> work either (we do not have singlethread_cpu and cpu_populated_map).
> Checking !keventd_up() in the clocksource code looks to me like a hack.
> Any ideas, please?
Still present in mmotm 2009-09-14-01-57.
> [1]
> kernel_init/smp_init/cpu_up/native_cpu_up/check_tsc_sync_source/mark_tsc_unstable/clocksource_mark_unstable/__clocksource_unstable
prev parent reply other threads:[~2009-09-14 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 8:00 clocksource: !keventd_up() && schedule_work() == oops Jiri Slaby
2009-09-14 9:28 ` Jiri Slaby [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=4AAE0CC2.5010502@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.