From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.14-rt21 & evolution
Date: Sat, 03 Dec 2005 12:47:46 -0800 [thread overview]
Message-ID: <1133642866.16477.11.camel@cmn3.stanford.edu> (raw)
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'm sorry I don't have more information on exactly what
is happening and I know this report is not very useful. The crash seems
related to reading email (when there's a lot of it) at the same as it is
storing folders and doing other things. After starting it again a couple
of times it keeps working fine for the rest of the day. I'm now at home
with a cold so I have not been able to reboot into the previous kernel
to double check but I wanted to warn you anyway... (I don't see anything
on the logs).
The kernel I was running successfully before (by setting the clock
source manually to acpi_pm) was 2.6.14-rt13.
-- Fernando
next reply other threads:[~2005-12-03 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 20:47 Fernando Lopez-Lezcano [this message]
2005-12-03 22:08 ` Lee Revell
2005-12-03 23:48 ` Fernando Lopez-Lezcano
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=1133642866.16477.11.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®