On Mon, 2011-09-26 at 17:39 -0700, Simon Kirby wrote: > Hello! > > Following up on "System CPU increasing on idle 2.6.36", this issue is > still happening even on 3.1-rc7. So, since it has been 9 months since I > reported this, I figured I'd bisect this issue. The first bisection ended > in an IPMI regression that looked like the problem, so I had to start > again. Eventually, I got commit b80c3cb628f0ebc241b02e38dd028969fb8026a2 > which made it into 2.6.34-rc4. > > With this commit, system CPU keeps rising as the log crunch box runs > (reads log files via NFS and spews out HTML files into NFS-mounted report > directories). When it finishes the daily run, the system time stays > non-zero and continues to be higher and higher after each run, until the > box never completes a run within a day due to all of the wasted cycles. So reverting that commit fixes the problem on 3.1-rc7? As far as I can see, doing so should be safe thanks to commit 5547e8aac6f71505d621a612de2fca0dd988b439 (writeback: Update dirty flags in two steps) which fixes the original problem at the VFS level. Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
