From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 114301] jbd2_journal_write_revoke_records
Date: Wed, 30 Mar 2016 09:19:26 +0000 [thread overview]
Message-ID: <bug-114301-13602-6y0qSrejTf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-114301-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=114301
jia he <hejiash@cn.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hejiash@cn.ibm.com
--- Comment #4 from jia he <hejiash@cn.ibm.com> ---
(In reply to xierui1010 from comment #3)
> Dear，the system under load.I can't to reproduce this problem.
> Thank you for your help!
Hi xierui
I wonder whether you are using emulex be2net network driver.
And I got the similar call trace with you. Need to collect some common symptoms
for the memory corruption
--
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-30 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:44 [Bug 114301] New: "Oops: Kernel access of bad area, sig: 11 [#1]" (check log for details) bugzilla-daemon
2016-03-10 13:47 ` [Bug 114301] jbd2_journal_write_revoke_records Oops: Kernel access of bad area bugzilla-daemon
2016-03-10 13:47 ` [Bug 114301] jbd2_journal_write_revoke_records bugzilla-daemon
2016-03-13 12:37 ` bugzilla-daemon
2016-03-13 19:35 ` bugzilla-daemon
2016-03-13 23:52 ` bugzilla-daemon
2016-03-14 3:24 ` bugzilla-daemon
2016-03-14 3:30 ` bugzilla-daemon
2016-03-30 9:19 ` bugzilla-daemon [this message]
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=bug-114301-13602-6y0qSrejTf@https.bugzilla.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 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.