From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] oops on 2.4.2 with lvm-0.9beta5 and Reiserfs 3.6.25
Date: Fri, 23 Feb 2001 16:16:24 -0500 [thread overview]
Message-ID: <703660000.982962984@tiny> (raw)
In-Reply-To: <14998.53544.642864.34288@eagle.mh.lucent.com>
On Friday, February 23, 2001 04:07:52 PM -0500 lvm@winux.com wrote:
> ReiserFS version 3.6.25
> journal-1777: buffer 16 bad state !PREPARED !LOCKED !DIRTY !JDIRTY_WAIT
This oops shows that somebody logged the super block without preparing it.
Could you please run this data through ksymoops so I can track down the
caller?
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000000 printing eip:
> c011370b
> *pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c011370b>]
> EFLAGS: 00010086
> eax: c697b578 ebx: 00000000 ecx: 00000286 edx: c15bdd68
> esi: c15bdd60 edi: c15bc000 ebp: c697bb90 esp: c15bdd48
> ds: 0018 es: 0018 ss: 0018
> Process lvcreate (pid: 134, stackpage=c15bd000)
> Stack: c697b56c c15bdd60 c01079d9 c697ba00 c697b400 c6879000 00000001
> c15bc000 c697b578 00000000 c0107b38 c697b56c c13b51a0 00000000 c023bf73
> 4004fe20 080989e0 c15bdf9c c6879000 c697ba00 00000001 c68794c4
> 00000004 c68794c4 Call Trace: [<c01079d9>] [<c0107b38>]
> [<c023bf73>] [<c01f3724>] [<c013b967>] [<c0108e2f>] [<c010002b>]
>
> Code: 89 13 51 9d 5b 5e c3 89 f6 9c 58 fa 8b 4a 0c 8b 52 08 89 4a
-chris
next prev parent reply other threads:[~2001-02-23 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 21:07 [linux-lvm] oops on 2.4.2 with lvm-0.9beta5 and Reiserfs 3.6.25 lvm
2001-02-23 21:16 ` Chris Mason [this message]
2001-02-23 21:46 ` lvm
2001-02-23 21:56 ` Chris Mason
2001-02-24 3:45 ` lvm
2001-02-23 21:23 ` Andreas Dilger
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=703660000.982962984@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.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 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).