From: Ricardo Galli <gallir@uib.es>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0-test1 Ext3 Ooops. Reboot needed.
Date: Fri, 18 Jul 2003 23:13:23 +0200 [thread overview]
Message-ID: <200307182313.23288.gallir@uib.es> (raw)
In-Reply-To: <20030718140019.4f6667bd.akpm@osdl.org>
On Friday 18 July 2003 23:00, Andrew Morton shaped the electrons to shout:
> Ricardo Galli <gallir@uib.es> wrote:
> > Unable to handle kernel paging request at virtual address e9000018
> > EIP is at find_inode_fast+0x20/0x70
> > Call Trace:
> > [<c0168e42>] iget_locked+0x52/0xc0
> > [<c018a54b>] ext3_lookup+0x6b/0xd0
> > [<c015cd92>] real_lookup+0xd2/0x100
>
> What is "famd"? File access monitor daemon? From where did you obtain it?
"File alteration monitor", from Debian. It uses portmapperand is recommended
to improve kde performance.
$ apt-cache show fam
Package: fam
Priority: extra
Section: admin
Installed-Size: 232
Maintainer: Joerg Wendland <joergland@debian.org>
...
Description: File Alteration Monitor
FAM monitors files and directories, notifying interested applications
of changes.
.
This package provides a server that can monitor a given list of files
and notify applications through a socket. If the kernel supports dnotify
(kernels >= 2.4.x) FAM is notified directly by the kernel. Otherwise it has
to poll the files' status. FAM can also provide a RPC service for monitoring
remote files (such as on a mounted NFS filesystem).
Nevertheless I saw the same message the morning after updatedb run.
Regards,
--
ricardo galli GPG id C8114D34
http://mnm.uib.es/~gallir/
next prev parent reply other threads:[~2003-07-18 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 10:28 Linux 2.6.0-test1 Ext3 Ooops. Reboot needed Ricardo Galli
2003-07-18 21:00 ` Andrew Morton
2003-07-18 21:13 ` Ricardo Galli [this message]
2003-07-18 21:27 ` Andrew Morton
2003-07-18 21:51 ` Ricardo Galli
2003-07-18 21:51 ` Alan Cox
2003-07-18 23:26 ` Martin J. Bligh
2003-07-18 21:21 ` Arjan van de Ven
2003-07-18 22:59 ` Chris Mason
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=200307182313.23288.gallir@uib.es \
--to=gallir@uib.es \
--cc=akpm@osdl.org \
--cc=linux-kernel@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.