From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Xianghua Xiao <xiaoxianghua@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.33.3-rt16 Oops caused by umount
Date: Tue, 27 Apr 2010 13:23:18 -0700 [thread overview]
Message-ID: <1272399798.2255.2.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.1004272053130.2951@localhost.localdomain>
On Tue, 2010-04-27 at 20:56 +0200, Thomas Gleixner wrote:
> On Tue, 27 Apr 2010, Xianghua Xiao wrote:
>
> cc'ed John
>
> > 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 ]---
Hey Xianghua,
What filesystem was this on? And what architecture?
thanks
-john
next prev parent reply other threads:[~2010-04-27 20:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 18:44 2.6.33.3-rt16 Oops caused by umount Xianghua Xiao
2010-04-27 18:56 ` Thomas Gleixner
2010-04-27 20:23 ` john stultz [this message]
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=1272399798.2255.2.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xiaoxianghua@gmail.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.