From: Xianghua Xiao <xiaoxianghua@gmail.com>
To: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: 2.6.33.3-rt16 Oops caused by umount
Date: Tue, 27 Apr 2010 13:44:26 -0500 [thread overview]
Message-ID: <l2ye6bf505b1004271144ta6817962vec8167d813658648@mail.gmail.com> (raw)
2.6.33.2-rt13 worked fine, however on 2.6.33.3-rt16, when I do reboot, it oops:
# reboot
# Oops: Kernel access of bad area, sig: 11 [#1]
PREEMPT 83xx Sys
Modules linked in:
NIP: c00efc68 LR: c00efc38 CTR: 00000000
REGS: ce6e3dc0 TRAP: 0300 Not tainted (2.6.33.3-rt16)
MSR: 00009032 <EE,ME,IR,DR> CR: 24000448 XER: 00000000
DAR: 00000038, DSISR: 20000000
TASK = cd89ccc0[1613] 'umount' THREAD: ce6e2000
GPR00: 00000000 ce6e3e70 cd89ccc0 ce6e3ddc 22222222 00000000 ce6e3e24 ce6e3e04
GPR08: 00008000 00000010 cdfa2130 cdfa26e0 44000442 100bbc1c 0fffd000 ffffffff
GPR16: 00000001 00000000 007fff00 00000000 00000000 00000001 ce6e3eb8 00000021
GPR24: 00000060 00000000 00000000 ceb94c40 00000000 ceb94cc0 c065781c ce6e3e70
NIP [c00efc68] fs_may_remount_ro+0x6c/0xd8
LR [c00efc38] fs_may_remount_ro+0x3c/0xd8
Call Trace:
[ce6e3e70] [c00efc38] fs_may_remount_ro+0x3c/0xd8 (unreliable)
[ce6e3e90] [c00f1198] do_remount_sb+0x11c/0x164
[ce6e3eb0] [c0113a3c] do_mount+0x538/0x86c
[ce6e3f10] [c0113e30] sys_mount+0xc0/0x120
[ce6e3f40] [c00178d8] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0xfe5f8c4
LR = 0x10051b88
Instruction dump:
38000000 817d00c0 3bbd00c0 60088000 814b0000 2f8a0000 419e0008 7c00522c
7f8be800 419e004c 812b000c 81290040 <80090028> 2f800000 419e0028 a009006e
---[ end trace 17c711f9d369c3a3 ]---
------------[ cut here ]------------
Kernel BUG at c045eeac [verbose debug info unavailable]
Oops: Exception in kernel mode, sig: 5 [#2]
PREEMPT 83xx Sys
Modules linked in:
NIP: c045eeac LR: c045ee84 CTR: 00000000
REGS: ce6e3a80 TRAP: 0700 Tainted: G D (2.6.33.3-rt16)
MSR: 00021032 <ME,CE,IR,DR> CR: 44004428 XER: 00000000
TASK = cd89ccc0[1613] 'umount' THREAD: ce6e2000
GPR00: 00000001 ce6e3b30 cd89ccc0 c068f6b4 c045fc68 00000000 ce6e3b84 ce6e3b64
GPR08: ce6e3b5c c0690000 cd89ccc0 ce6e3b30 24004422 100bbc1c 0fffd000 ffffffff
GPR16: 00000001 00000000 007fff00 00000000 00000000 c0657824 ce6e3eb8 ce6e3b3c
GPR24: cf028ea0 cec84d1c c065781c cec86a60 00009032 c065781c c065781c ce6e3b30
NIP [c045eeac] rt_spin_lock_slowlock+0xa8/0x394
LR [c045ee84] rt_spin_lock_slowlock+0x80/0x394
Call Trace:
[ce6e3b30] [c045ee84] rt_spin_lock_slowlock+0x80/0x394 (unreliable)
[ce6e3bc0] [c045fc68] rt_spin_lock+0x58/0x90
[ce6e3bd0] [c00efbbc] file_sb_list_del+0x48/0x88
[ce6e3bf0] [c00f03ac] __fput+0x168/0x274
[ce6e3c20] [c00f04f8] fput+0x40/0x58
[ce6e3c30] [c00d3f74] remove_vma+0x78/0xd8
[ce6e3c50] [c00d4150] exit_mmap+0x17c/0x1e4
[ce6e3cc0] [c00318c0] mmput+0x6c/0x144
[ce6e3ce0] [c003712c] exit_mm+0x15c/0x190
[ce6e3d10] [c00391e8] do_exit+0xf0/0x670
[ce6e3d60] [c0014c9c] die+0x1cc/0x1d4
[ce6e3d90] [c001cdb8] bad_page_fault+0x98/0xf0
[ce6e3db0] [c0017d8c] handle_page_fault+0x7c/0x80
--- Exception: 300 at fs_may_remount_ro+0x6c/0xd8
LR = fs_may_remount_ro+0x3c/0xd8
[ce6e3e90] [c00f1198] do_remount_sb+0x11c/0x164
[ce6e3eb0] [c0113a3c] do_mount+0x538/0x86c
[ce6e3f10] [c0113e30] sys_mount+0xc0/0x120
[ce6e3f40] [c00178d8] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0xfe5f8c4
LR = 0x10051b88
Instruction dump:
38600001 4bbc95d1 801a0004 3aba0008 2f800000 419e0264 801a0018 7c4a1378
5400003a 7c400278 7c000034 5400d97e <0f000000> 83a20000 39200002 2f9d0002
---[ end trace 17c711f9d369c3a4 ]---
Fixing recursive fault but reboot is needed!
BUG: scheduling while atomic: umount/0x00000001/1613, CPU#0
Modules linked in:
Call Trace:
[ce6e3800] [c000b6a0] show_stack+0xe8/0x244 (unreliable)
[ce6e3850] [c04608c0] dump_stack+0x2c/0x44
[ce6e3860] [c00282b0] __schedule_bug+0x9c/0xc4
[ce6e3880] [c045cfe8] __schedule+0x488/0x5a4
[ce6e38b0] [c045d2e0] schedule+0x40/0xa8
[ce6e38c0] [c003973c] do_exit+0x644/0x670
[ce6e3910] [c0014c9c] die+0x1cc/0x1d4
[ce6e3940] [c0014fd0] _exception+0x130/0x170
[ce6e3a30] [c00151d0] program_check_exception+0xd0/0x634
[ce6e3a70] [c0017f38] ret_from_except_full+0x0/0x4c
--- Exception: 700 at rt_spin_lock_slowlock+0xa8/0x394
LR = rt_spin_lock_slowlock+0x80/0x394
[ce6e3bc0] [c045fc68] rt_spin_lock+0x58/0x90
[ce6e3bd0] [c00efbbc] file_sb_list_del+0x48/0x88
[ce6e3bf0] [c00f03ac] __fput+0x168/0x274
[ce6e3c20] [c00f04f8] fput+0x40/0x58
[ce6e3c30] [c00d3f74] remove_vma+0x78/0xd8
[ce6e3c50] [c00d4150] exit_mmap+0x17c/0x1e4
[ce6e3cc0] [c00318c0] mmput+0x6c/0x144
[ce6e3ce0] [c003712c] exit_mm+0x15c/0x190
[ce6e3d10] [c00391e8] do_exit+0xf0/0x670
[ce6e3d60] [c0014c9c] die+0x1cc/0x1d4
[ce6e3d90] [c001cdb8] bad_page_fault+0x98/0xf0
[ce6e3db0] [c0017d8c] handle_page_fault+0x7c/0x80
--- Exception: 300 at fs_may_remount_ro+0x6c/0xd8
LR = fs_may_remount_ro+0x3c/0xd8
[ce6e3e90] [c00f1198] do_remount_sb+0x11c/0x164
[ce6e3eb0] [c0113a3c] do_mount+0x538/0x86c
[ce6e3f10] [c0113e30] sys_mount+0xc0/0x120
[ce6e3f40] [c00178d8] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0xfe5f8c4
LR = 0x10051b88
next reply other threads:[~2010-04-27 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 18:44 Xianghua Xiao [this message]
2010-04-27 18:56 ` Thomas Gleixner
2010-04-27 20:23 ` john stultz
2010-04-27 20:30 ` john stultz
2010-04-27 20:54 ` Xianghua Xiao
2010-04-27 22:08 ` 2.6.33.3-rt16 - not reaching login Uwaysi Bin Kareem
2010-04-28 6:01 ` 2.6.33.3-rt16 Oops caused by umount john stultz
2010-04-28 15:21 ` Xianghua Xiao
2010-04-28 16:34 ` Thomas Gleixner
2010-04-28 17:54 ` Xianghua Xiao
2010-04-28 19:38 ` Thomas Gleixner
2010-04-28 20:06 ` Xianghua Xiao
2010-04-28 20:22 ` Thomas Gleixner
2010-04-28 21:22 ` Xianghua Xiao
2010-04-28 21:46 ` Thomas Gleixner
2010-04-28 23:33 ` Xianghua Xiao
2010-04-29 12:22 ` Thomas Gleixner
[not found] ` <20100429151555.GM17639@pcarmody-desktop>
2010-04-29 15:52 ` Xianghua Xiao
2010-04-30 10:02 ` Thomas Gleixner
2010-04-30 14:04 ` Xianghua Xiao
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=l2ye6bf505b1004271144ta6817962vec8167d813658648@mail.gmail.com \
--to=xiaoxianghua@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®