From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: File/memory corruption in 2.6.37?
Date: Wed, 2 Mar 2011 17:10:28 -0700 [thread overview]
Message-ID: <201103021710.29016.thomas@fjellstrom.ca> (raw)
In-Reply-To: <20110302155226.05fbe993.akpm@linux-foundation.org>
On March 2, 2011, Andrew Morton wrote:
> On Fri, 25 Feb 2011 15:31:00 -0700
>
> Thomas Fjellstrom <thomas@fjellstrom.ca> wrote:
> > On February 25, 2011, Thomas Gleixner wrote:
> > > On Fri, 25 Feb 2011, Thomas Fjellstrom wrote:
> > > > On February 25, 2011, you wrote:
> > > > > Ever since I upgraded to 2.6.37 from 2.6.36, that kmail's folder
> > > > > indexes are being corrupted fairly regularly. Far more often than
> > > > > is usual (almost never). Several a day in fact are being
> > > > > corrupted. I can only imagine that this isn't the only corruption
> > > > > happening and it is worrying.
> > > >
> > > > Forgot to give any kind of useful info:
> > > >
> > > > System: Lenovo SL500 laptop, intel core2duo T9400 cpu, 4G ram, gm45
> > > > intel gfx
> > > >
> > > > running debian sid, with the current debian 2.6.37 kernel, was
> > > > running a hand rolled 2.6.36 kernel with autogroup applied and
> > > > didn't have these issues.
> > >
> > > Could you verify that with an hand rolled 2.6.37.2 ?
> > >
> > > Thanks,
> > >
> > > tglx
> >
> > I suppose it won't hurt to give it a try.
>
> Any results yet?
>
> Which filesystem is being used? I've seen at least one similar report
> for reiserfs.
So far I haven't noticed the corruption with 2.6.37.2, and I'm using ext3. I'm
going to test with the debian kernel again soon here to see if the problem
come back. I was just seeing if maybe it only happens when I've been using the
system for a long time. I tend to have a lot of issues with this laptop once
its been running for a long enough period (typically related to the intel_gfx
drivers leaking and causing crashes or general unstableness). I had to restart
my laptop a couple days ago, due to it not noticing the resume image.. but I
didn't notice any corruption before that.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next prev parent reply other threads:[~2011-03-03 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 21:57 File/memory corruption in 2.6.37? Thomas Fjellstrom
2011-02-25 22:08 ` Thomas Fjellstrom
2011-02-25 22:23 ` Thomas Gleixner
2011-02-25 22:31 ` Thomas Fjellstrom
2011-03-02 23:52 ` Andrew Morton
2011-03-03 0:10 ` Thomas Fjellstrom [this message]
2011-03-05 8:58 ` Bastien ROUCARIES
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=201103021710.29016.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).