Hi!
> > > > > and send us the output? (Enabling CONFIG_TIMER_STATS,
> > > > > CONFIG_SCHED_DEBUG and CONFIG_SCHEDSTATS would maximize the amount
> > > > > of information.)
> > > >
> > > > This was w/o hpet=disable . Do you want me to test with hpet=disable?
> > >
> > > no, this is fine. You've got a hpet clockevents driver and two lapic
> > > drivers:
> > >
> > > Clock Event Device: hpet
> > > set_next_event: hpet_legacy_next_event
> > > set_mode: hpet_legacy_set_mode
> > > event_handler: tick_handle_oneshot_broadcast
> > >
> > > Clock Event Device: lapic
> > > set_next_event: lapic_next_event
> > > set_mode: lapic_timer_setup
> > > event_handler: hrtimer_interrupt
> > >
> > > Clock Event Device: lapic
> > > set_next_event: lapic_next_event
> > > set_mode: lapic_timer_setup
> > > event_handler: hrtimer_interrupt
> > >
> > > to me this has the feeling of lapic breakage in C2 mode. Does it get any
> > > better if you boot with 'nolapic'? (but that might in turn turn off
> > > high-res timers and nohz in essence) Thomas, any ideas?
> >
> > Hmm, lapic is considered unstable in c2 by default. You have to tell
> > the kernel that you trust it in C2 on the command line.
>
> yeah, i was wondering about that too. ACPI enumerated them properly at a
> certain stage:
>
> ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
> ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
>
> but perhaps somehow we miss this fact and fail to turn off the lapic
> clockevents drivers?
I tried to add nolapic_timer manually, and that helped, but:
checking TSC synchronization [CPU#0 -> CPU#1]:
Measured 627605 cycles TSC warp between CPUs, turning off TSC clock.
Marking TSC unstable due to: check_tsc_sync_source failed.
Brought up 2 CPUs
CPU0 attaching sched-domain:
domain 0: span 3
groups: 1 2
CPU1 attaching sched-domain:
domain 0: span 3
groups: 2 1
net_namespace: 64 bytes
...
Bluetooth: HCI socket layer initialized
ACPI: RTC can wake from S4
Time: hpet clocksource has been installed.
Clockevents: could not switch to one-shot mode:<6>Clockevents: could
not switch to one-shot mode: lapic is not functional.
Could not switch to high resolution mode on CPU 1
lapic is not functional.
Could not switch to high resolution mode on CPU 0
system 00:00: iomem range 0x0-0x9ffff could not be reserved
...and result is nohz is not functional :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
