From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15231] kernel BUG at fs/ext4/inode.c:1852!
Date: Thu, 11 Feb 2010 04:48:10 GMT [thread overview]
Message-ID: <201002110448.o1B4mAoh014607@demeter.kernel.org> (raw)
In-Reply-To: <bug-15231-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15231
--- Comment #12 from Theodore Tso <tytso@mit.edu> 2010-02-11 04:47:31 ---
So the "kernel BUG at fs/inode.c:1343!" failure was showing up on both 2.6.32.2
and 2.6.32.7, right? Do you know when it first started showing up?
The kernel stack trace indicates that it's coming from releasing one the nfs
kernel thread's network sockets, when the TCP connection is broken or something
else goes wrong. I don't think it's ext4 related at all; it looks like an NFS
server issue.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-02-11 4:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 9:38 [Bug 15231] New: BUG: soft lockup - CPU#3 stuck for 61s bugzilla-daemon
2010-02-05 9:43 ` [Bug 15231] " bugzilla-daemon
2010-02-05 9:50 ` [Bug 15231] kernel BUG at fs/ext4/inode.c:1852! bugzilla-daemon
2010-02-09 1:05 ` bugzilla-daemon
2010-02-09 1:06 ` bugzilla-daemon
2010-02-09 3:52 ` bugzilla-daemon
2010-02-09 3:57 ` bugzilla-daemon
2010-02-09 18:09 ` bugzilla-daemon
2010-02-09 18:27 ` bugzilla-daemon
2010-02-09 18:30 ` bugzilla-daemon
2010-02-10 3:26 ` bugzilla-daemon
2010-02-11 3:53 ` bugzilla-daemon
2010-02-11 4:48 ` bugzilla-daemon [this message]
2010-02-11 5:13 ` bugzilla-daemon
2010-02-11 5:22 ` bugzilla-daemon
2010-02-12 3:29 ` bugzilla-daemon
2010-02-15 17:14 ` bugzilla-daemon
2010-02-16 0:49 ` bugzilla-daemon
2010-02-16 6:45 ` bugzilla-daemon
[not found] <bug-15231-13602@https.bugzilla.kernel.org/>
2012-05-14 15:06 ` bugzilla-daemon
2012-05-14 15:06 ` bugzilla-daemon
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=201002110448.o1B4mAoh014607@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).