smokey's fork tests hangs with glibc 2.28+ ?
norbert.lange at andritz.com
Mon Mar 11 14:40:18 CET 2019
Well, swapping out glibc with 2.27 removes the issue, so it has been introduced afterwards,
the current buildroot will use 2.28 so you should be able to build yourself a reproducer that way.
I will also attach a prebuilt rootfs once the clean rebuild is done.
Unfortunately the smokey suite is not available with the Mercury core, might be easier to isolate that way.
In the future, maybe some battletested glibc versions could be recommended for xenomai?
> -----Original Message-----
> From: Jan Kiszka <jan.kiszka at siemens.com>
> Sent: Freitag, 8. März 2019 16:23
> To: Lange Norbert <norbert.lange at andritz.com>; Xenomai
> (xenomai at xenomai.org) <xenomai at xenomai.org>
> Subject: Re: smokey's fork tests hangs?
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINKS OR
> On 08.03.19 15:05, Lange Norbert wrote:
> >> -----Original Message-----
> >> From: Jan Kiszka <jan.kiszka at siemens.com>
> >> Sent: Freitag, 8. März 2019 14:59
> >> To: Lange Norbert <norbert.lange at andritz.com>; Xenomai
> >> (xenomai at xenomai.org) <xenomai at xenomai.org>
> >> Subject: Re: smokey's fork tests hangs?
> >> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE,
> >> EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINKS OR
> >> On 08.03.19 14:47, Lange Norbert wrote:
> >>>> Not reproducible here with stable/3.0.x or next, and with
> >>>> ipipe-x86-
> >> 4.14.y.
> >>>> What are your parameters?
> >>> Not entirely upstream, but based on ipipe-core-4.14.89-x86-2 and
> >>> xenomai master, the difference is contained in the rt_igb driver,
> >>> which is
> >> not even loaded.
> >>> Defconfig is attached.
> >>> I mostly suspect glibc as the relevant difference, I am using
> >>> glibc-2.28-69-g1e5c5303a522764d7e9d2302a60e4a32cdb902f1.
> >>> Looking at the strace the child process 1039 is stuck at
> >>> FUTEX_WAIT_PRIVATE, Don’t really know how to tackle this.
> >> Is this a regression? Then try bisecting the causing commit.
> > Not really, I haven't ran the smokey suite often (and only for specific tests).
> > I use buildroot for my rootfs, so I have no easy way of swapping around
> glibc versions.
> > I have not encountered other issues outside of those tests.
> > Which version of glibc is running on your end?
> Mine is in fact old: 2.19. Colleagues are on Debian 9 with 2.24 where this used
> to work but was not tested recently against master.
> I haven't tried buildroot with Xenomai yet - is there a working 3.x recipe, and
> everything is out-of-the-box?
> Regarding how to possibly debug this: If one thread is stuck, you could check
> if there are other threads in that application that may hold the lock. Or if the
> lock content is actually invalid and therefore blocking the caller (memory
> corruption). You should be able to read out the thread ID of the owner from
> a valid lock structure.
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate
> Competence Center Embedded Linux
This message and any attachments are solely for the use of the intended recipients. They may contain privileged and/or confidential information or other information protected from disclosure. If you are not an intended recipient, you are hereby notified that you received this email in error and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system.
ANDRITZ HYDRO GmbH
Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation
Firmensitz/ Registered seat: Wien
Firmenbuchgericht/ Court of registry: Handelsgericht Wien
Firmenbuchnummer/ Company registration: FN 61833 g
More information about the Xenomai