mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Leibs <leibs@willowgarage.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Blaise Gassend <blaise@willowgarage.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Darren Hart <dvhltc@us.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: ERESTARTSYS escaping from sem_wait with RTLinux patch
Date: Sat, 10 Oct 2009 19:07:57 -0700	[thread overview]
Message-ID: <92be2ef30910101907h68aa44c0tad678f036f19c8f3@mail.gmail.com> (raw)
In-Reply-To: <92be2ef30910101208p1b2eb493wdfa46d363ca96f99@mail.gmail.com>

On Sat, Oct 10, 2009 at 12:08 PM, Jeremy Leibs <leibs@willowgarage.com> wrote:
> Thomas, thanks for the quick reply.
>
> On Sat, Oct 10, 2009 at 10:59 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
-----snip-----
>>
>> 1) Does that happen with 2.6.31.2-rt13 as well ?
>
> I am nearly certain we saw the problems with the newer kernel as well,
> although that was back with a much less concise test and I've since
> reinstalled over that machine in the process of trying a number of
> different 32/64 hardy/jaunty configurations on different hardware.
> I'll do a fresh install of that particular kernel with default
> configuration options on our hardware and let you know a little later
> today.

Running on fresh install of 64 bit jaunty:

leibs@c1:~$ uname -rv
2.6.31.2-rt13 #1 SMP PREEMPT RT Sat Oct 10 15:34:13 PDT 2009

leibs@c1:~$ python threadprocs8.py
sem_wait: Unknown error 512
Fatal Python error: ceval: orphan tstate
Aborted

  reply	other threads:[~2009-10-11  2:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10  9:09 Blaise Gassend
2009-10-10 16:40 ` ERESTARTSYS escaping from sem_wait with Preempt-RT Blaise Gassend
2009-10-10 17:59 ` ERESTARTSYS escaping from sem_wait with RTLinux patch Thomas Gleixner
2009-10-10 19:08   ` Jeremy Leibs
2009-10-11  2:07     ` Jeremy Leibs [this message]
2009-10-11  5:48   ` Jeremy Leibs
2009-10-12 14:16     ` Darren Hart
     [not found]       ` <1255384010.10236.123.camel@lts.willowgarage.com>
     [not found]         ` <4AD3BD57.6080703@us.ibm.com>
     [not found]           ` <4AD3D6AE.2050609@us.ibm.com>
     [not found]             ` <4AD3FFB0.5030405@us.ibm.com>
2009-10-13  4:54               ` Darren Hart
2009-10-13  8:56                 ` Blaise Gassend
2009-10-13 15:13                   ` Darren Hart
2009-10-13 18:45                     ` Thomas Gleixner

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=92be2ef30910101907h68aa44c0tad678f036f19c8f3@mail.gmail.com \
    --to=leibs@willowgarage.com \
    --cc=blaise@willowgarage.com \
    --cc=dvhltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®