Linux NFS development
 help / color / mirror / Atom feed
From: Stuart Anderson <anderson@ligo.caltech.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: soft lockup
Date: Fri, 29 Jun 2007 08:58:31 -0700	[thread overview]
Message-ID: <20070629155831.GA14875@ligo.caltech.edu> (raw)
In-Reply-To: <1183088891.6163.119.camel@heimdal.trondhjem.org>

On Thu, Jun 28, 2007 at 11:48:11PM -0400, Trond Myklebust wrote:
> On Thu, 2007-06-28 at 16:52 -0700, Stuart Anderson wrote:
> > I am currently getting a soft lockup every few minutes on a Sun X4600M2
> > (8 x Opteron 8218) running 2.6.20.14 plus Tronds revalidate-the-fsid patch
> > and Jeff's O_EXCL-OPEN patch. The machine is still usable but a bit slow and
> > currently the rpciod/0 thread is being reported as using 100%CPU by top.
> > 
> > Any ideas?
> > 
> > Thanks.
> > 
> > kernel: BUG: soft lockup detected on CPU#0!
> > kernel: 
> > kernel: Call Trace:
> > kernel:  <IRQ>  [<ffffffff8025a17c>] softlockup_tick+0xfc/0x140
> > kernel:  [<ffffffff80237ed7>] update_process_times+0x57/0x90
> > kernel:  [<ffffffff802160e4>] smp_local_timer_interrupt+0x34/0x60
> > kernel:  [<ffffffff80216789>] smp_apic_timer_interrupt+0x59/0x80
> > kernel:  [<ffffffff8020a7b6>] apic_timer_interrupt+0x66/0x70
> > kernel:  <EOI>  [<ffffffff8817a310>] :nfs:nfs3_xdr_readres+0x0/0x170
> > kernel:  [<ffffffff803272e1>] _raw_spin_lock+0xb1/0x150
> > kernel:  [<ffffffff8817a310>] :nfs:nfs3_xdr_readres+0x0/0x170
> > kernel:  [<ffffffff8043d74d>] lock_kernel+0x1d/0x30
> > kernel:  [<ffffffff88123f3f>] :sunrpc:rpc_exit_task+0x1f/0x90
> > kernel:  [<ffffffff8812521e>] :sunrpc:__rpc_execute+0x8e/0x280
> > kernel:  [<ffffffff8023fd6e>] run_workqueue+0xae/0x160
> > kernel:  [<ffffffff8023fee0>] worker_thread+0x0/0x190
> > kernel:  [<ffffffff80243930>] keventd_create_kthread+0x0/0x90
> > kernel:  [<ffffffff80240031>] worker_thread+0x151/0x190
> > kernel:  [<ffffffff80229490>] default_wake_function+0x0/0x10
> > kernel:  [<ffffffff8023fee0>] worker_thread+0x0/0x190
> > kernel:  [<ffffffff80243b79>] kthread+0xd9/0x120
> > kernel:  [<ffffffff8020a998>] child_rip+0xa/0x12
> > kernel:  [<ffffffff80243930>] keventd_create_kthread+0x0/0x90
> > kernel:  [<ffffffff80243aa0>] kthread+0x0/0x120
> > kernel:  [<ffffffff8020a98e>] child_rip+0x0/0x12
> > kernel: 
> 
> I don't see how anything could lock up in nfs3_xdr_readres(). There
> should be no loops in that routine at all.
> 
> What is that "<EOI>" in the above dump? Is that syslog failing to record
> something?

syslog is working as far as I can tell. What does EOI indicate (End Of Input?)

> If so, could you please try using 'dmesg -s 90000' in order to recover
> the missing info?

I have increased the buffer for the next occurance. However, after getting
268 soft lockups yesterday they are no longer occuring today. The rpciod/0
kernel thread is now using "just" ~70% of one cpu compared to 100% when we
where getting the lockups yesterday.

Only about half of the soft lockups refer to nfs3_xdr_readres. They all
have an <EOI> and all but one has "sunrpc:__rpc_execute"

Here is example that does not refer to nfs3_xdr_readres. Perhaps this
is more general than NFS? though we did not see these until we started
using NFSV4 client mounts. The other change we made when adding NFSV4
mounts was updating nfs-utils to 1.0.9-16 (CentOS 5 patches) to avoid
some of the known memory leaks/spin loops in rpc.idmapd and rpc.mountd.

kernel: BUG: soft lockup detected on CPU#0!
kernel: 
kernel: Call Trace:
kernel:  <IRQ>  [<ffffffff8025a17c>] softlockup_tick+0xfc/0x140
kernel:  [<ffffffff80237ed7>] update_process_times+0x57/0x90
kernel:  [<ffffffff802160e4>] smp_local_timer_interrupt+0x34/0x60
kernel:  [<ffffffff80216789>] smp_apic_timer_interrupt+0x59/0x80
kernel:  [<ffffffff8020a7b6>] apic_timer_interrupt+0x66/0x70
kernel:  <EOI>  [<ffffffff803272e1>] _raw_spin_lock+0xb1/0x150
kernel:  [<ffffffff8043d74d>] lock_kernel+0x1d/0x30
kernel:  [<ffffffff88123fd0>] :sunrpc:rpc_release_calldata+0x20/0x50
kernel:  [<ffffffff881253ff>] :sunrpc:__rpc_execute+0x26f/0x280
kernel:  [<ffffffff8023fd6e>] run_workqueue+0xae/0x160
kernel:  [<ffffffff8023fee0>] worker_thread+0x0/0x190
kernel:  [<ffffffff80243930>] keventd_create_kthread+0x0/0x90
kernel:  [<ffffffff80240031>] worker_thread+0x151/0x190
kernel:  [<ffffffff80229490>] default_wake_function+0x0/0x10
kernel:  [<ffffffff8023fee0>] worker_thread+0x0/0x190
kernel:  [<ffffffff80243b79>] kthread+0xd9/0x120
kernel:  [<ffffffff8020a998>] child_rip+0xa/0x12
kernel:  [<ffffffff80243930>] keventd_create_kthread+0x0/0x90
kernel:  [<ffffffff80243aa0>] kthread+0x0/0x120
kernel:  [<ffffffff8020a98e>] child_rip+0x0/0x12
kernel: 

Thanks.

-- 
Stuart Anderson  anderson@ligo.caltech.edu
http://www.ligo.caltech.edu/~anderson

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-06-29 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 23:52 soft lockup Stuart Anderson
2007-06-29  3:48 ` Trond Myklebust
2007-06-29 15:58   ` Stuart Anderson [this message]
2007-07-01  3:58     ` Stuart Anderson
2007-07-05  0:36       ` Stuart Anderson

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=20070629155831.GA14875@ligo.caltech.edu \
    --to=anderson@ligo.caltech.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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