On Fri, Mar 03, 2006 at 05:09:57PM -0500, Jeff Garzik wrote:
> Or sata_nv/libata is to blame.
In case you are coming late to the thread:
The lost ticks are closely correlated with sata_nv disk activity on
multiple disks, and the problem is easily reproducable with "find /usr |
cpio -o >/dev/null" on an MD RAID1 -- but not on a single disk.
Andi suggested:
Yes, I bet something forgets to turn on interrupts again and it's
picked up by (and blamed on) the next guy who does an unconditional
sti, which happens to be __do_sofitrq or idle.
That sounds right to me.
I built 2.6.16-rc5-git6 yesterday, and it still suffers from the same
issue.
-Bill
-
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]
