Bug 82433
Summary: | Pthread program brings Seg.fault on only IA64. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Shinya Narahara <naraha_s> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | drepper, fweimer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-11-10 23:24:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shinya Narahara
2003-01-22 03:14:58 UTC
What release are you using? What updates? This is obviously no retail product so I need more information. I've already written the version of retail product, Red Hat Linux 7.2 for Itanium processor. Actually, this issue occures on retail RH72 and all of updated kernel/glibc, from ftp://updates.redhat.com/7.2/en/os/ia64/ Just try the test program above, you can see this issue soon. If you've tested the program and not seen any errors, please tell us your version of retail product, or kernel/glibc. We guess this issue is caused by "thread un-safe" system call. So, our silly countermeasure is add pthread_mutex_lock()/unlock() before/after all of system calls that the test program calls. Then it works fine, although the performance is not pretty good... I have some questions about this bugzilla #82433, from someone who have same issue. This is not so local. Have you tried AS2.1 or even better, RHEL3? RHEL3 features a new thread library, the only one for which we can aim at providing standard compliance. We've tried it on RHEL3 Beta2, kernel-2.4.21-1.1931.2.399.ent, glibc-2.3.2-74, gcc-3.2.3-16. It seems to work fine. Thanks for your information. However the program with 100 threads, is very heavy even if on 8CPU machine... ;-) What do you mean by "heavy"? Do you see delays? I have fixed one bug which is especially noticable on machines with >= 4 processors after beta 2. It is in the RHEL release. Please give that version a try. In any case, the original problem is fixed in RHEL3 which is the first version we truly can say threads are working (especially on ia64). We won't backport any of the changes. So I close the bug. |