public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* clocksource: !keventd_up() && schedule_work() == oops
@ 2009-09-09  8:00 Jiri Slaby
  2009-09-14  9:28 ` Jiri Slaby
  0 siblings, 1 reply; 2+ messages in thread
From: Jiri Slaby @ 2009-09-09  8:00 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: Linux kernel mailing list

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?

[1]
kernel_init/smp_init/cpu_up/native_cpu_up/check_tsc_sync_source/mark_tsc_unstable/clocksource_mark_unstable/__clocksource_unstable

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-09-14  9:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-09  8:00 clocksource: !keventd_up() && schedule_work() == oops Jiri Slaby
2009-09-14  9:28 ` Jiri Slaby

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox