From: Mark Lord <kernel@teksavvy.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG at net/sunrpc/svc_xprt.c:921
Date: Wed, 16 Jan 2013 17:58:02 -0500 [thread overview]
Message-ID: <50F7307A.4090808@teksavvy.com> (raw)
In-Reply-To: <50F72F03.5070806@teksavvy.com>
On 13-01-16 05:51 PM, Mark Lord wrote:
> On 13-01-16 12:20 AM, Stanislav Kinsbursky wrote:
>>
>> Mark, could you provide any call traces?
>
> Call traces from where/what?
> There's this one, posted earlier in the BUG report:
>
> kernel BUG at net/sunrpc/svc_xprt.c:921!
> Call Trace:
> [<ffffffffa016a56a>] ? svc_recv+0xcc/0x338 [sunrpc]
> [<ffffffffa0318bfc>] ? nfs_callback_authenticate+0x20/0x20 [nfsv4]
> [<ffffffffa0318c19>] ? nfs4_callback_svc+0x1d/0x3c [nfsv4]
> [<ffffffff810407e6>] ? kthread+0x81/0x89
> [<ffffffff81040765>] ? kthread_freezable_should_stop+0x36/0x36
> [<ffffffff812ea62c>] ? ret_from_fork+0x7c/0xb0
> [<ffffffff81040765>] ? kthread_freezable_should_stop+0x36/0x36
..
This might be of some interest.
Here are the first few lines of the same BUG occurance,
with timestamps and the dmesg lines that immediately preceeded it.
Perhaps they might help indicate who's triggering the action
that results in the BUG(?).
Jan 14 10:58:05 zippy kernel: [66045.627952] NFS: Registering the id_resolver key type
Jan 14 10:58:05 zippy kernel: [66045.628014] Key type id_resolver registered
Jan 14 10:58:05 zippy kernel: [66045.628020] Key type id_legacy registered
Jan 14 10:58:05 zippy kernel: [66045.636302] ------------[ cut here ]------------
Jan 14 10:58:05 zippy kernel: [66045.648342] kernel BUG at net/sunrpc/svc_xprt.c:921!
next prev parent reply other threads:[~2013-01-16 22:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 16:17 BUG at net/sunrpc/svc_xprt.c:921 Mark Lord
2013-01-14 20:37 ` J. Bruce Fields
2013-01-15 4:16 ` Mark Lord
2013-01-15 20:56 ` J. Bruce Fields
2013-01-16 5:20 ` Stanislav Kinsbursky
2013-01-16 22:51 ` Mark Lord
2013-01-16 22:58 ` Mark Lord [this message]
2013-01-17 5:05 ` Stanislav Kinsbursky
2013-01-17 13:03 ` J. Bruce Fields
2013-01-17 13:24 ` Stanislav Kinsbursky
2013-01-17 23:41 ` Mark Lord
2013-01-18 5:37 ` Stanislav Kinsbursky
2013-01-18 15:48 ` Mark Lord
2013-01-18 15:56 ` J. Bruce Fields
2013-01-21 8:19 ` Stanislav Kinsbursky
2013-01-20 22:51 ` BUG at net/sunrpc/svc_xprt.c:921 (another one) Mark Lord
2013-02-12 20:52 ` J. Bruce Fields
2013-02-13 15:00 ` Mark Lord
2013-02-15 19:22 ` J. Bruce Fields
2013-02-15 19:42 ` Tom Horsley
2013-02-15 19:46 ` J. Bruce Fields
2013-02-15 19:23 ` [PATCH 1/2] svcrpc: make svc_age_temp_xprts enqueue under sv_lock J. Bruce Fields
2013-02-15 19:23 ` [PATCH 2/2] svcrpc: fix rpc server shutdown races J. Bruce Fields
2013-02-15 19:33 ` BUG at net/sunrpc/svc_xprt.c:921 (another one) Paweł Sikora
2013-02-17 15:54 ` J. Bruce Fields
2013-02-18 7:42 ` Paweł Sikora
2013-01-17 13:11 ` BUG at net/sunrpc/svc_xprt.c:921 Mark Lord
2013-01-17 13:53 ` J. Bruce Fields
2013-01-17 23:40 ` Mark Lord
2013-02-25 20:45 ` Mark Lord
2013-02-25 20:52 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2013-02-07 12:56 Tom Horsley
2013-02-08 20:58 ` J. Bruce Fields
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=50F7307A.4090808@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.