All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikesh Rambaran <vikesh.rambaran@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai LTTng support
Date: Tue, 14 Apr 2009 10:12:40 +0200	[thread overview]
Message-ID: <1239696760.5780.12.camel@domain.hid> (raw)
In-Reply-To: <49DC6612.40802@domain.hid>

Hi
Hope everybody had a good Easter weekend :)

On Wed, 2009-04-08 at 10:53 +0200, Jan Kiszka wrote:
> vikesh rambaran wrote:
> > Hi
> > 
> > On Tue, Apr 7, 2009 at 1:20 PM, Jan Kiszka <jan.kiszka@domain.hid> wrote:
> > 
> >> Hmm, maybe we have issues with MTRR again. Can you also try X without
> >> CONFIG_MTRR set in the kernel?
> > 
> > 
> > Tried the following combinations on intel and amd platforms
> > 
> > 1. No MTRR on 2.6.28.7 + Xenomai 2.4.7 for Intel core 2
> > 2. No MTRR on 2.6.28.7 + Xenomai 2.4.7 + LTTng for Amd Athlon
> > 
> > Lockup still persists (:
> 
> OK, something to rule out. So I'm hoping for serial/netconsole dumps now
> (don't forget to switch off klogd for this, otherwise the information
> may get lost between crashing ipipe/xenomai and klogd.
> 

Unfortunately, no last words on serial console (:

Stopped klogd (using /etc/init.d/klogd stop) and set dmesg -n 8 prior to
logging into gnome desktop.

Serial console setup with console=115200n81 with minicom on the monitor
PC. Startup messages and other events (eg USB attach/detach) visible

For info, 

1) Lockup seems to occur especially when applications are opened or when
trying to access disks

2) a fellow colleague is using Xenomai 2.4.7 with the 2.6.27 kernel
(without LTTng) with similar lockups.


If there are any other tests that i can do, please let me know ...

> > 
> > Going to compare the vanilla installation message log with that of the
> > xenomai patched installation
> > ("Unable to set hardware clock" is something i don't remember seeing in the
> > vanilla logs - will check again)
> 
> The RTC issue is most probably unrelated, should rather have something
> to do with conflicting old/new RTC config switches (sorry, don't recall
> details ATM).
> 
Yes, agreed. Built the RTC into the kernel and the warning goes away.

Keep well
Vicki




  reply	other threads:[~2009-04-14  8:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23  8:00 [Xenomai-help] Xenomai LTTng support vikesh rambaran
2009-03-23 13:07 ` Jan Kiszka
2009-03-24  7:37   ` vikesh rambaran
2009-03-24 17:40     ` Jan Kiszka
2009-03-24 21:37       ` vikesh rambaran
2009-03-24 22:11         ` Jan Kiszka
2009-03-25 11:17           ` Philippe Gerum
2009-03-25 13:36           ` vikesh rambaran
2009-04-06  8:26             ` vikesh rambaran
2009-04-06 10:57               ` Jan Kiszka
2009-04-07 10:19                 ` Vikesh Rambaran
2009-04-07 11:20                   ` Jan Kiszka
2009-04-08  7:57                     ` vikesh rambaran
2009-04-08  8:53                       ` Jan Kiszka
2009-04-14  8:12                         ` Vikesh Rambaran [this message]
2009-04-14  9:16                           ` Jan Kiszka
2009-04-14 11:26                             ` Vikesh Rambaran
2009-04-14 11:35                               ` Jan Kiszka
     [not found]                                 ` <1239709765.5780.40.camel@domain.hid>
     [not found]                                   ` <49E4793D.2010105@domain.hid>
2009-04-14 13:55                                     ` Vikesh Rambaran
2009-04-14 14:13                                       ` Jan Kiszka
2009-04-17 15:44                                         ` vikesh rambaran
2009-04-18 10:27                                           ` Philippe Gerum
2009-04-19 18:23                                             ` vikesh rambaran
2009-03-23 13:12 ` Andreas Glatz
2009-03-23 13:17   ` Andreas Glatz
2009-03-23 13:40   ` Jan Kiszka

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=1239696760.5780.12.camel@domain.hid \
    --to=vikesh.rambaran@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.