On Mon, Jan 16, 2006 at 12:16:21PM -0800, john stultz wrote:
> On Sat, 2006-01-14 at 13:08 +0100, Mattia Dongili wrote:
> > On Thu, Jan 12, 2006 at 03:26:01PM -0800, john stultz wrote:
[...]
> > > Few things to try (independently):
> > > 1. Does booting w/ idle=poll change the behavior?
> >
> > yes, no more stalls
>
> Ok, this points to the TSC is changing frequency (likely due to C3
> halting).
humm... no C3 state here :) did you mean this C3?
# cat /proc/acpi/processor/CPU0/power
active state: C2
max_cstate: C8
bus master activity: 00000000
states:
C1: type[C1] promotion[C2] demotion[--] latency[000] usage[00007790]
*C2: type[C2] promotion[--] demotion[C1] latency[010] usage[02310093]
> > > 2. Does booting w/ clocksource=jiffies change the behavior?
> >
> > yes, same as above
>
> Ok, good, interrupts are getting there at the right frequency.
>
> > > 3. After booting up, run:
> > > echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > And check that the system keeps accurate time.
> >
> > didn't try as there seems to be no problem in timekeeping
>
> Well, it would have re-inforced the TSC being the issue, but I'm fairly
> confident that that is the case.
Now that filesystem problems have gone I have longer uptimes. OhOhOh,
very funnny, echoing tsc into the mentioned sysfs entry makes the clock
almost completely stop:
# date
Mon Jan 16 21:29:26 CET 2006
now count with me 1..2..3..4..5
# date
Mon Jan 16 21:29:27 CET 2006
I'd say the time is far from being accurate.
> My theory: The stalls are due to the TSC frequency not being consistent
> for the small window at boot between when it is installed and when the
> ACPI PM clocksource is installed.
seems you're right, issuing a 'sleep 1' takes ages before it returns and
it's exactely where the boot process got stuck.
> I'll try to narrow that window down a bit and see if that doesn't
> resolve the issue.
I'll be happy to test new patches if necessary (I'm running -mm4)
--
mattia
:wq!
-
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]