On Sun, 2006-06-18 at 02:09 -0700, Andrew Morton wrote:
> On Sun, 18 Jun 2006 09:36:16 +0200
> Mike Galbraith <[email protected]> wrote:
>
> > as
> > evolution mail demonstrates to me every time it's GUI hangs and I see
> > that a nice 19 find is running, eating very little CPU, but effectively
> > DoSing evolution nonetheless (journal).
>
> eh? That would be an io scheduler bug, wouldn't it?
>
> Tell us more.
The trace below was done with a nice -n 19 bonnie -s 2047 running, but
the same happens with the find that SuSE starts at annoying times.
Scheduler is cfq, but changing schedulers doesn't help.
Place a shell window over the evolution window, start io, then click on
the evolution window, and see how long it takes to be able to read mail.
Here, it's a couple forevers.
evolution D 00000001 0 9324 6938 9333 7851 (NOTLB)
ef322dec 00000000 00000000 00000001 00000003 93a3f580 000f44c2 ef322000
ef322000 ef314030 93a3f580 000f44c2 ef322000 001fb058 ef24d980 ef322000
ef322e50 b10bcb57 00000000 b1399998 ef322e3c 00000001 ef24d9c0 ef24d9d0
Call Trace:
[<b10bcb57>] log_wait_commit+0x139/0x1f1
[<b10b6000>] journal_stop+0x239/0x350
[<b10b6dc8>] journal_force_commit+0x1d/0x1f
[<b10ae32a>] ext3_force_commit+0x24/0x26
[<b10a83a0>] ext3_write_inode+0x34/0x7b
[<b107fa79>] __writeback_single_inode+0x2e8/0x3c9
[<b10803f1>] sync_inode+0x15/0x2f
[<b10a426b>] ext3_sync_file+0xc3/0xc8
[<b10600fc>] do_fsync+0x68/0xb3
[<b1060167>] __do_fsync+0x20/0x2f
[<b1060195>] sys_fsync+0xd/0xf
[<b1002e1b>] syscall_call+0x7/0xb
-
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]
