mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rt21 & evolution
Date: Sat, 03 Dec 2005 15:48:16 -0800	[thread overview]
Message-ID: <1133653696.16477.47.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <1133647737.5890.2.camel@mindpipe>

On Sat, 2005-12-03 at 17:08 -0500, Lee Revell wrote:
> On Sat, 2005-12-03 at 12:47 -0800, Fernando Lopez-Lezcano wrote:
> > Hi Ingo... just a heads up. I've been running 2.6.14-rt21 for a few days
> > and the timing issues seem to be gone on my X2 machine, as the main
> > timing is no longer derived from the TSC's. Very good! It should work
> > great with a patched Jack (that does not use TSC for its internal timing
> > measurements). 
> > 
> > But I'm seeing a recurrent problem that so far I can only blame -rt21
> > for. When I start evolution (on a fully patched 32 bit fc4 system) it
> > eventually dies.
> 
> I was seeing exactly the same problem here.  I don't think it's related
> to -rt21, I think someome posted a malformed message to LKML or one of
> the other lists that we are both on and Evo is choking on it.  It starts
> to download the mail then you get "Storing folder" for like 5 minutes
> then it crashes.

It is not the exact same behavior I'm seeing, I get the crashes usually
in the middle of the new message download process the first time I start
evo in the morning. If I let it idle after startup, evo does all the
"storing folder" stuff and eventually dies when getting the new email
(or so I think). 

But you could of course be right and there is some message it is choking
on - it is strange that this is happening to you as well. I think this
first happened to me on Wed Nov 30. 

To tell the truth this does not seem like a -rt related problem except
that it started happening the day I booted into -rt21. 

> I finally managed to get into my mail by (carefully) deleting ALL
> metadata - all the .index, .index.data, .cmeta, and .ev-summary files
> from .evolution.

I can get it to start after two or three tries (so far) without touching
anything in evo's files. And then it runs fine. The behavior
_subjectively_ gives me the impression that it is related to downloading
large number of messages, or doing many things at once at startup
(threading). 

-- Fernando



  reply	other threads:[~2005-12-03 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 20:47 Fernando Lopez-Lezcano
2005-12-03 22:08 ` Lee Revell
2005-12-03 23:48   ` Fernando Lopez-Lezcano [this message]
2005-12-04 14:58     ` Dinakar Guniguntala
2005-12-05  0:40       ` Fernando Lopez-Lezcano
2005-12-05 17:38       ` Fernando Lopez-Lezcano
2005-12-05 17:43         ` Ingo Molnar
2005-12-20 11:17           ` 2.6.15-rc5-rt2 and Kconfig Esben Nielsen

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=1133653696.16477.47.camel@cmn3.stanford.edu \
    --to=nando@ccrma.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.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

all inboxes | Powered by JetHome®