[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <92be2ef30910101907h68aa44c0tad678f036f19c8f3@mail.gmail.com>
Date: Sat, 10 Oct 2009 19:07:57 -0700
From: Jeremy Leibs <leibs@...lowgarage.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Blaise Gassend <blaise@...lowgarage.com>,
LKML <linux-kernel@...r.kernel.org>,
Darren Hart <dvhltc@...ibm.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: ERESTARTSYS escaping from sem_wait with RTLinux patch
On Sat, Oct 10, 2009 at 12:08 PM, Jeremy Leibs <leibs@...lowgarage.com> wrote:
> Thomas, thanks for the quick reply.
>
> On Sat, Oct 10, 2009 at 10:59 AM, Thomas Gleixner <tglx@...utronix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists