2005-11-26 10:37:53

by Karsten Wiese

[permalink] [raw]
Subject: 2.6.14-rt15 @x86_64UP: "sem_post: Invalid argument"

I get loads of those messages since switching from rt12 to rt15.
no other known change.

They happen during startup and when I trigger
i.e. an ardour build like this:
$ scons

a typical strace excerpt:
----
futex(0x5012a0, FUTEX_WAKE, 1) = -1 EINVAL (Invalid argument)
write(2, "sem_post: Invalid argument\n", 27) = 27
----

Other futex() calls like
----
futex(0x3b384030c8, FUTEX_WAKE, 2147483647) = 0
----
succeed.

This happens on fc4.
Maybe caused by a recent change from a semaphore to completion?

Karsten





___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de


2005-11-27 14:14:13

by Karsten Wiese

[permalink] [raw]
Subject: Re: 2.6.14-rt15 @x86_64UP: "sem_post: Invalid argument"

Am Samstag, 26. November 2005 11:40 schrieb Karsten Wiese:
> I get loads of those messages since switching from rt12 to rt15.

fixed in rt20.

I've got an "io_apic cached" patch for x86_64 here,
that ticks since weeks on my UP. Interisting?

danke,
Karsten





___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de

2005-11-27 14:59:38

by Ingo Molnar

[permalink] [raw]
Subject: Re: 2.6.14-rt15 @x86_64UP: "sem_post: Invalid argument"


* Karsten Wiese <[email protected]> wrote:

> Am Samstag, 26. November 2005 11:40 schrieb Karsten Wiese:
> > I get loads of those messages since switching from rt12 to rt15.
>
> fixed in rt20.

great.

> I've got an "io_apic cached" patch for x86_64 here, that ticks since
> weeks on my UP. Interesting?

yeah, please send it, i'll add it to -rt.

Ingo