LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Renato S. Yamane" <renatoyamane@mandic.com.br>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Updatedb hangs Kernel 2.6.22.9-cfs-v22
Date: Wed, 16 Jan 2008 14:40:53 -0200 [thread overview]
Message-ID: <478E3395.6050301@mandic.com.br> (raw)
In-Reply-To: <2c0942db0801160830j72c0fc77xc4cc9e7fd676d78a@mail.gmail.com>
Ray Lee escreveu:
> On Jan 14, 2008 7:28 AM, Renato S. Yamane <renatoyamane@mandic.com.br> wrote:
>> Ray Lee escreveu:
>>> On Jan 12, 2008 10:03 AM, Renato S. Yamane wrote:
>>>> I can't use updatedb in Debian Etch (stable) using customized Kernel
>>>> 2.6.22.9-cfs-v22.
>>>>
>>>> When I ran updatedb, after ~1 minute my system hangs and "caps lock" LED
>>>> is blinking. No log is registered.
>>> Please switch out of X11 to a text mode console (CTRL-ALT-F1), and run
>>> updatedb there. Capture the oops with a digital camera, and post a
>>> link to the picture (not the picture itself!) to the list. Or, write
>>> down the oops carefully, and post the text.
>> I see a infinite loop and is very fast, so I can't capture errors messages.
>> None is registered in /var/log/*
>
> Well, that's very odd. Please also try the latest CFS backport to see
> if that solves the problem.
This problem still occour in 2.6.23.13 with CFS 24.1
I see a part of error message: Is something about ipw2200.
I need find a Camera with good focus, because my cam is not so good to
take a picture in distance <=20cm.
Best regards,
Renato
next prev parent reply other threads:[~2008-01-16 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 18:03 Updatedb hangs Kernel 2.6.22.9-cfs-v22 Renato S. Yamane
2008-01-12 18:25 ` Ray Lee
2008-01-14 15:28 ` Renato S. Yamane
2008-01-16 16:30 ` Ray Lee
2008-01-16 16:40 ` Renato S. Yamane [this message]
2008-01-16 17:11 ` Dhaval Giani
2008-01-12 18:36 ` Dhaval Giani
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=478E3395.6050301@mandic.com.br \
--to=renatoyamane@mandic.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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 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).