From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 114301] New: "Oops: Kernel access of bad area, sig: 11 [#1]" (check log for details)
Date: Thu, 10 Mar 2016 13:44:39 +0000 [thread overview]
Message-ID: <bug-114301-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=114301
Bug ID: 114301
Summary: "Oops: Kernel access of bad area, sig: 11 [#1]" (check
log for details)
Product: File System
Version: 2.5
Kernel Version: 2.6.32-573.7.1.el6.ppc64
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: xierui1010@sina.com.cn
Regression: No
Created attachment 208631
--> https://bugzilla.kernel.org/attachment.cgi?id=208631&action=edit
backtrace.txt
KERNEL: /usr/lib/debug/lib/modules/2.6.32-573.7.1.el6.ppc64/vmlinux
DUMPFILE: vmcore [PARTIAL DUMP]
CPUS: 32
DATE: Wed Mar 9 22:17:09 2016
UPTIME: 61 days, 16:55:25
LOAD AVERAGE: 1.28, 1.27, 1.34
TASKS: 2741
NODENAME: pow-bss-jf23
RELEASE: 2.6.32-573.7.1.el6.ppc64
VERSION: #1 SMP Thu Sep 10 13:44:06 EDT 2015
MACHINE: ppc64 (4228 Mhz)
MEMORY: 251.8 GB
PANIC: "Oops: Kernel access of bad area, sig: 11 [#1]" (check log for
details)
PID: 1840
COMMAND: "jbd2/dm-13-8"
TASK: c000003e8a130f60 [THREAD_INFO: c000003e845d4000]
CPU: 4
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 1840 TASK: c000003e8a130f60 CPU: 4 COMMAND: "jbd2/dm-13-8"
#0 [c000003e845d7500] .crash_kexec at c0000000000ec0c4
#1 [c000003e845d7700] .die at c000000000031638
#2 [c000003e845d77b0] .bad_page_fault at c000000000044bd8
#3 [c000003e845d7830] handle_page_fault at c000000000005228
Data Access error [300] exception frame:
R0: 0000000000000001 R1: c000003e845d7b20 R2: d0000000198de328
R3: c0000019e95753d0 R4: c000003e853bf180 R5: 0000000000000005
R6: c0000019e9575440 R7: c0000000016958c8 R8: c000003eefec1f00
R9: 0000000000000010 R10: 0000000000000000 R11: c000001c751f4be0
R12: d0000000198cf750 R13: c000000001072f00 R14: 0000000000000000
R15: 0000000000000000 R16: ffffffffc03b3998 R17: 0000000000000005
R18: c000003e853bf180 R19: 0000000000000441 R20: c000003e966c3388
R21: 0000000000020000 R22: 0000000000000002 R23: 0000000000000001
R24: c0000019e95753d0 R25: c0000019e95753d0 R26: d0000000198d6360
R27: 0000000000000010 R28: c000003e88907590 R29: c000003e8a8b1e00
R30: d0000000198dd0d8 R31: 1fc67f012a980061
NIP: d0000000198c77c4 MSR: 8000000000009032 OR3: d0000000198d6370
CTR: d0000000198c0880 LR: d0000000198c791c XER: 0000000000000000
CCR: 0000000024008044 MQ: 0000000000000001 DAR: 1fc67f012a980079
DSISR: 0000000040000000 Syscall Result: 0000000000000000
#4 [c000003e845d7b20] .jbd2_journal_write_revoke_records at d0000000198c77c4
[jbd2]
[Link Register ] [c000003e845d7b20] .jbd2_journal_write_revoke_records at
d0000000198c791c (unreliable)
#5 [c000003e845d7c10] .jbd2_journal_commit_transaction at d0000000198c39ec
[jbd2]
#6 [c000003e845d7de0] .kjournald2 at d0000000198cc51c [jbd2]
#7 [c000003e845d7ed0] .kthread at c0000000000c17ec
#8 [c000003e845d7f90] .kernel_thread at c000000000033c34
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-03-10 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:44 bugzilla-daemon [this message]
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
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@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.