Prev: tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call
Next: Remove large struct from stack in DVB dib3000mc and dib7000p drivers
From: Andrew Morton on 2 Mar 2010 19:20

(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 2 Mar 2010 16:31:03 GMT
bugzilla-daemon(a)bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=15426
>
> Summary: Running many copies of bonnie++ on different
> filesystems seems to deadlock in sync
> Product: File System
> Version: 2.5
> Kernel Version: 2.6.32
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: VFS
> AssignedTo: fs_vfs(a)kernel-bugs.osdl.org
> ReportedBy: john(a)calva.com
> Regression: No
>
>
> I create 8 ext3 filesystems on 8 disks and run a copy of bonnie++ on each
> filesystem. All but two or three of the Bonnie++ processes seem to hang in
> sync and I get log messages like:
>
> [ 1557.377626] INFO: task bonnie:2503 blocked for more than 120 seconds.
> [ 1557.377693] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
> message.
> [ 1557.377775] bonnie D 0000000000000000 0 2503 2489 0x00000000
> [ 1557.377778] ffffffff8144b1f0 0000000000000082 0000000000000000
> ffff88034ac155c0
> [ 1557.377780] ffff88033c079880 ffffffff81047f43 000000000000f8a0
> ffff88063b1e9fd8
> [ 1557.377783] 00000000000155c0 00000000000155c0 ffff88063bbe3f90
> ffff88063bbe4288
> [ 1557.377785] Call Trace:
> [ 1557.377787] [<ffffffff81047f43>] ? finish_task_switch+0x3a/0xa7
> [ 1557.377790] [<ffffffff812ee653>] ? __mutex_lock_common+0x10b/0x17b
> [ 1557.377792] [<ffffffff812ee77b>] ? mutex_lock+0x1a/0x31
> [ 1557.377794] [<ffffffff8110a3cd>] ? sync_filesystems+0x13/0xe3
> [ 1557.377796] [<ffffffff8110a4d8>] ? sys_sync+0x12/0x2e
> [ 1557.377799] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
>

When the system is stuck, please run

echo w > /proc/sysrq-trigger

or, equivalently, hit `alt-sysrq-w'.

This will emit huge amounts of stack traces into the system logs and
onto the console. There's no need to send all of them - please
identify typical-looking ones and then send them in reply to this
email. Email clients like to wordwrap these traces - please try to
prevent that.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call
Next: Remove large struct from stack in DVB dib3000mc and dib7000p drivers