clone 594812 -1
block 594812 by -1
retitle -1 Zero writeback interval sends flush processes into busy loop
reassign -1 linux-image-2.6.32-5-amd64
thanks
Hi Xavier!
On Mon, Aug 30, 2010 at 05:12:11PM +0200, Xavier Roche wrote:
> Note that the proble never occurred in 2.6.24 ; it might be some
> regression code in the kernel OR in the TX2 code ?
I've updated my devel machine to the latest kernel version, and now I can
reproduce the problem. It's not the fsync(), actually, but but the stopping of
the pdflush daemon that makes the flush-<major>:<minor> kernel threads enter a
busy loop (spinning in bdi_writeback_task()). It can be triggered as simple as:
echo 0 > /proc/sys/vm/dirty_writeback_centisecs
(Use echo 500 > /proc/sys/vm/dirty_writeback_centisecs to restore a sane
behaviour.) Suspending pdflush activity this way used to work before. Now it
seems to be interpreted as a zero wait time between iterations in the flush
threads. Thus, I'd say this is a regression in the kernel.
Regards,
Daniel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
