Ever since the 2.6.17 kernel pulled in the generic timer code, I've been
experiencing hangs and softlockups with the aic94xx driver (which I
thought were driver related). Finally, after a lot of debugging I've
isolated the culprit to linux/time.h:timespec_add_ns()
What is happening is that a->tv_nsec is coming in here negative and
looping for huge amounts of time.
Why tv_nsec is negative appears to be related to massive cycle
adjustments in kernel/timer.c:update_wall_time(). With the TSC as my
clocksource I've seen the clocksource_read() return increments of in the
200s range. No idea why this is happening. The same strange
discontinuous jumps in cycle count also occurs with pm_acpi as the clock
source.
I can't get a good enough handle on all the generic time code changes to
reverse them. However, this machine is a P4, so I was able to boot it
with an x86_64 kernel (which doesn't yet use the generic time code) and
confirm that all the hangs and softlockups go away.
The machine in question is an IBM x206m dual core P4.
James
-
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]
