Bug 82952 - wine dosn't work on kernel 2.4.20-2.2{6,7} and locks ps,top,killall etc
wine dosn't work on kernel 2.4.20-2.2{6,7} and locks ps,top,killall etc
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel (Show other bugs)
1.0
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-28 17:12 EST by Michael Stefaniuc
Modified: 2007-04-18 12:50 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-02 02:03:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
output of Sysreq-t after the wine/ps/top/killall process locked up (25.28 KB, text/plain)
2003-01-28 17:14 EST, Michael Stefaniuc
no flags Details
remove FASTCALL from vm_ in lnclude/linux/mm.h (953 bytes, patch)
2003-01-28 18:39 EST, Michael Stefaniuc
no flags Details | Diff
sysreq-t output for the 2.4.20-2.27 with the patch applied (23.94 KB, text/plain)
2003-01-28 18:43 EST, Michael Stefaniuc
no flags Details

  None (edit)
Description Michael Stefaniuc 2003-01-28 17:12:57 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
I recompiled the 2.4.20-2.2{2,6,7} kernels on a up2date RHL 7.3 from the
kernel-source rpm using the athlon config from the configs directory.
Starting wine on the 2.4.20-2.2{6,7} kernel dosn't work; it just hangs without
spitting out the normal warnings it spits out on startup. The wine process can't
be terminated by CTRL-C nor moved into background. killall and top just hang and
ps outputs the details for the processes with pid smaller then the pid of the
wine process and then hangs too.
Before starting wine ps/top/killall just work fine.
The 2.4.20-2.22 kernel works just fine without exhibiting any of the above problems.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. boot a 2.4.20-2.2{6,7} kernel
2. start wine
3. start top/ps/killall
    

Actual Results:  wine, top, ps ,killall hangs

Expected Results:  they should not hang

Additional info:

wine is latest CVS but that shouldn't matter.
I'll attach the output of Sysrq-t
Comment 1 Michael Stefaniuc 2003-01-28 17:14:45 EST
Created attachment 89663 [details]
output of Sysreq-t after the wine/ps/top/killall process locked up
Comment 2 Ben LaHaise 2003-01-28 17:24:08 EST
Note: may be related to FASTCALL macros interacting with gcc 2.96.  Can remove
them for older gcc.
Comment 3 Michael Stefaniuc 2003-01-28 18:39:49 EST
Created attachment 89668 [details]
remove FASTCALL from vm_ in lnclude/linux/mm.h

As requested i tried this patch without succes.
Comment 4 Michael Stefaniuc 2003-01-28 18:43:16 EST
Created attachment 89669 [details]
sysreq-t output for the 2.4.20-2.27 with the patch applied
Comment 5 Michael Stefaniuc 2003-01-28 18:45:43 EST
Forgot to say that i did a "make clean" after applying the patch
Comment 6 Michael Young 2003-01-29 08:37:44 EST
I am seeing the killall problem on phoebe2+rawhide packages for kernel -2.27
when the shutdown stops at the "sending TERM signal to all processes" stage. The
-2.25 kernel works fine.
Comment 7 Arjan van de Ven 2003-02-01 08:09:42 EST
it looks like -2.30 works ok here... should be in rawhide now.
Comment 8 Michael Stefaniuc 2003-02-01 16:10:46 EST
Just tested it and wine works just fine. You can close the bug.
Comment 9 Ingo Molnar 2003-02-02 02:03:37 EST
So the signal fixes in 2.30 did the trick - great.

Note You need to log in before you can comment on or make changes to this bug.