All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Steven Seeger <sseeger@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] more geode issues
Date: Sun, 11 Nov 2007 10:49:40 +0100	[thread overview]
Message-ID: <4736D034.5040606@domain.hid> (raw)
In-Reply-To: <51CAD0CE1504444DBE77CBBE51A0135D3285C8@domain.hid>

Steven Seeger wrote:
> I’m trying to get 2.6.23 to work with rc5. I’ve also tried trunk. I’m
> noticing the following behavior:
> 
>  
> 
> I’m using a geode GX1 board. The following relevant settings work with
> 2.6.22-2 and rc3:
> 
>  
> 
> Tickless system, one shot, TSC, geode 2cx200hr timer, and high res timers.
> 
>  
> 
> Everything is great with 2.6.22-2 and this config. The same settings on
> 2.6.23, however, yield an extremely fast blinking cursor in the
> framebuffer when xeno_nucleus is loaded. When xeno_native is loaded, the
> system runs fine except the timer interrupt is messed up for linux and
> the realtime tasks. A sleep 1 may take a couple minutes to return. If I
> switch to another VT and do a cat /lib/* or something, then it runs
> fine. I have a realtime task that acts as a sound driver.
>

Since you still have access to a shell, could you send the output of a
couple of "cat /proc/interrupts /proc/xenomai/irq" with roughly a
one-second delay between them? I'd like to know how many timer
interrupts are reported during this period.

>  
> 
> I’ve talked to Philippe about this problem privately, and there’s no
> real solution yet. I’m just posting it on the list now.
> 

It's a matter of being able to reproduce this behaviour, as usual. Your
.config for 2.6.23 would help too.

>  
> 
> Also, I’m having an issue with select() locking up the system with
> pipes. I saw there was a change made to pipe in trunk and am going to
> try and get that going with 2.6.22-2 now. If anyone knows anything about
> these two issues, please let me know.

The latest change is meant to have the real-time side receive a zero
byte count when the channel is closed by the Linux-side peer while
reading from it. I'll have a look at the select() issue once -rc6 is out.

--
Philippe.



  parent reply	other threads:[~2007-11-11  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11  0:35 [Xenomai-help] more geode issues Steven Seeger
2007-11-11  0:53 ` Steven Seeger
2007-11-11 17:08   ` Philippe Gerum
2007-11-11 20:46     ` Steven Seeger
2007-11-27 17:36       ` Philippe Gerum
2007-11-11  9:49 ` Philippe Gerum [this message]
2007-11-11 19:36   ` Steven Seeger

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=4736D034.5040606@domain.hid \
    --to=rpm@xenomai.org \
    --cc=philippe.gerum@domain.hid \
    --cc=sseeger@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.