From: Andrew Morton <akpm@osdl.org>
To: "Sergey S. Kostyliov" <rathamahata@ehouse.ru>
Cc: linux-kernel@vger.kernel.org, admin@list.net.ru
Subject: Re: 2.6.10 devfs oops without devfs mounted at all
Date: Wed, 9 Feb 2005 16:36:24 -0800 [thread overview]
Message-ID: <20050209163624.44557750.akpm@osdl.org> (raw)
In-Reply-To: <200502082013.50959.rathamahata@ehouse.ru>
"Sergey S. Kostyliov" <rathamahata@ehouse.ru> wrote:
>
> Here is an oops I've just get on my smp system:
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000001c
> printing eip:
> c01afe5b
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT SMP
> Modules linked in: ipt_REJECT ipt_state ip_conntrack iptable_filter
> CPU: 2
> EIP: 0060:[<c01afe5b>] Not tainted VLI
> EFLAGS: 00010286 (2.6.10)
> EIP is at devfsd_close+0x1b/0xc8
> eax: f7440a00 ebx: 00000000 ecx: c01afe40 edx: ed395280
> esi: 00000000 edi: f7f17800 ebp: f74f96c8 esp: cdc70f84
> ds: 007b es: 007b ss: 0068
> Process megamgr.bin (pid: 12844, threadinfo=cdc70000 task=dd81e520)
> Stack: ed395280 ed395280 00000000 f7f17800 c0150c76 ee9e87f8 ed395280 00000000
> f1985c80 cdc70000 c014f50f 00000003 00000003 080caa60 00000000 c01024df
> 00000003 080cc700 bfffe4f8 080caa60 00000000 bfffe4fc 00000006 0000007b
> Call Trace:
> [<c0150c76>] __fput+0x106/0x120
> [<c014f50f>] filp_close+0x4f/0x80
> [<c01024df>] syscall_call+0x7/0xb
Can you work out what file is being closed? One way of doing that would be
to work out how megamgr.bin is being invoked and to then run it by hand:
strace -f -o log megamgr.bin <args>
and we can then use the strace output to work out the pathname of the
offending file.
next prev parent reply other threads:[~2005-02-10 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 17:13 Sergey S. Kostyliov
2005-02-10 0:36 ` Andrew Morton [this message]
2005-02-10 9:49 ` Sergey S. Kostyliov
2005-02-10 10:12 ` Sergey S. Kostyliov
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=20050209163624.44557750.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=admin@list.net.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@ehouse.ru \
/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®