From: Andi Kleen <ak@suse.de>
To: reiserfs-dev@namesys.com, mason@suse.de, jeffm@suse.de
Cc: linux-fsdevel@vger.kernel.org
Subject: reiserfs unstable on large systems in 2.6.13-git9
Date: Mon, 12 Sep 2005 00:30:46 +0200 [thread overview]
Message-ID: <20050911223045.GA11071@wotan.suse.de> (raw)
When I run even relatively minor stress on 8 or 16 core
Opterons I get deadlocks like this:
At one point I also had a deadlock on a semaphore with
all processes that did disk access going into D
(backtrace lost on that one unfortunately but all the
traces went through reiserfs_set_acl)
Watchdog detected LOCKUP on CPU 10
CPU 10
Modules linked in:
Pid: 21498, comm: reaim Not tainted 2.6.13-git9 #4
RIP: 0010:[<ffffffff80418e2f>] <ffffffff80418e2f>{.text.lock.spinlock+22}
RSP: 0018:ffff81013b59bc40 EFLAGS: 00000086
RAX: 0000000000000000 RBX: ffffffff804c2ba0 RCX: 00000000c0000100
RDX: 0000000000000000 RSI: ffff81023b6f30c0 RDI: ffffffff804c2ba8
RBP: 0000000000000282 R08: ffff81013b59a000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: ffffffff804c2ba8
R13: ffff81023b6f30c0 R14: ffff81013b59bc50 R15: 00000000000001ff
FS: 00002aaaaaf3b0a0(0000) GS:ffffffff80603d00(0000) knlGS:00000000401c9c60
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007ffffffe048c CR3: 000000013dbdb000 CR4: 00000000000006a0
Process reaim (pid: 21498, threadinfo ffff81013b59a000, task ffff81023b6f30c0)
Stack: 0000000000000282 ffffffff80418ad0 0000000000000001 ffff81023b6f30c0
ffffffff801313b0 ffff810134a0bc68 ffffffff804c2bb0 ffff81013b59bdd8
ffff81013b59bdd8 ffff8102b586c678
Call Trace:<ffffffff80418ad0>{__down+160} <ffffffff801313b0>{default_wake_function+0}
<ffffffff80418779>{__down_failed+53} <ffffffff80418f96>{.text.lock.kernel_lock+25}
<ffffffff801c2bdc>{reiserfs_setattr+44} <ffffffff80418603>{__down_write+51}
<ffffffff80199594>{notify_change+340} <ffffffff8017bf61>{do_truncate+65}
<ffffffff8018d3e4>{may_open+468} <ffffffff8018ecfe>{open_namei+734}
<ffffffff80417af3>{thread_return+0} <ffffffff8017bb97>{filp_open+39}
<ffffffff8017b94b>{get_unused_fd+219} <ffffffff8017bc11>{do_sys_open+81}
<ffffffff8010d91e>{system_call+126}
Code: 80 3f 00 7e f9 e9 90 fd ff ff f3 90 80 3f 00 7e f9 e9 9c fd
console shuts up ...
NMI Watchdog detected LOCKUP on CPU 6
...
-Andi
next reply other threads:[~2005-09-11 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 22:30 Andi Kleen [this message]
2005-09-11 23:21 ` reiserfs unstable on large systems in 2.6.13-git9 Chris Mason
2005-09-12 8:48 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050911223045.GA11071@wotan.suse.de \
--to=ak@suse.de \
--cc=jeffm@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.de \
--cc=reiserfs-dev@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).