Skip to contentSkip to conversation

clocksource: !keventd_up() && schedule_work() == oops

DISCUSSION Jiri Slaby 1 participant 2 messages Sep 9, 2009 – Sep 14, 2009

lore
Share & tools
lore

Jiri Slaby

author
#0 lore raw

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

author
#1 lore raw
Quoted 6 lines · Jiri Slaby

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.

Quoted 7 lines

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.

Quoted 2 lines

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