From: Warren Togami <warren@togami.com>
To: maneesh@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 kernel BUG include/linux/dcache.h:271!
Date: 02 Jun 2003 02:30:40 -1000 [thread overview]
Message-ID: <1054557040.2020.620.camel@laptop> (raw)
In-Reply-To: <20030602100204.GE1256@in.ibm.com>
On Mon, 2003-06-02 at 00:02, Maneesh Soni wrote:
> On Mon, Jun 02, 2003 at 09:21:31AM +0000, Warren Togami wrote:
> > Hardware:
> > Sony Vaio FXA36 Athlon laptop
> > Red Hat Linux Rawhide
> >
> > After 5 days of uptime on 2.5.70, I noticed this in my dmesg. I don't
> > know what I was doing at the time when this happened. Known bug? Let
> > me know if you want more information about my hardware/software setup.
> >
> Hi Togami,
>
> It will be nice if you can provide some information regarding
> the filesystem set up you have in your system. Like which filesystem
> you were using.
>
Plain ext3 with UTF-8 filenames, no ACLs or Extended Attributes. It was
created with last week's RH rawhide then I moved to 2.5.70, uptime 5
days now.
Should I be worrying about filesystem corruption now?
> Are you able to recreate this problem?.
>
Unfortunately no. I just noticed that message in dmesg after 5 days of
uptime. Hmm, I just noticed this line within that last post:
<6>note: updatedb[18515] exited with preempt_count 1
If it happened during updatedb, then it must have been around 22 hours
ago during cron.daily's updatedb. My laptop was completely idle during
that time.
http://www.togami.com/~warren/archive/2003/fxa36-kernel-2.5.70.cfg
My kernel .config file.
Thanks,
Warren Togami
warren@togami.com
p.s. Please CC me in replies.
next prev parent reply other threads:[~2003-06-02 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 9:20 2.5.70 kernel BUG include/linux/dcache.h:271! Warren Togami
2003-06-02 10:02 ` Maneesh Soni
2003-06-02 12:30 ` Warren Togami [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 16:20 Lou Langholtz
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=1054557040.2020.620.camel@laptop \
--to=warren@togami.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.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