Suse 9.2 Kernel hangs with 32 bit Application
There seems to be a severe problem with the 64 bit Kernel of Suse 9.2. I am using Tax 2004, it is a 32 bit application running on Wine. It has its own implementation of wine, which worked with Suse 9.0 and 9.1, but now I had to use the wine package that comes with Suse 9.2. After I had fixed the configuration of the paths, I was able to start the application. It crashes very often, which is not a problem in itself. But sometimes the screen freezes, the keyboard doesn't react anymore and finally even a ping to the freezing machine stops working. The only explanation I have is that the kernel has crashed. Interesting enough I can start the same application with Transgaming cedega and it doesn't crash or freeze the machine. (Not all parts of Tax are working with cedega, so I can't use it all the time.) My assumption is that the wine package that comes with Suse 9.2 crashes the 64 bit kernel while running a 32 bit application in user space. This is a very severe problem and I would rather see that only the 32 bit application crashes, but not the kernel. Without further assistance I can only guess what is happening here. Judging by the poor stability of wine it could be the NX feature or of course any other problem in the kernel. Has anyone similar experiences with the new kernel? Regards Detlef Grittner ------------------------- uname -a Linux linux 2.6.8-24.5-default #1 Wed Nov 17 11:10:06 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux rpm -qi wine Name : wine Relocations: (not relocatable) Version : 20040813 Vendor: SUSE LINUX AG, Nuernberg, Germany Release : 7 Build Date: Mo 04 Okt 2004 21:30:04CEST Install date: Sa 04 Dez 2004 14:11:52 CET Build Host: g242.suse.de Group : System/Emulators/PC Source RPM: wine-20040813-7.src.rpm Size : 51062464 License: LGPL, Other License(s),see package Signature : DSA/SHA1, Mo 04 Okt 2004 21:39:37 CEST, Key ID a84edae89c800aca Packager : http://www.suse.de/feedback URL : http://www.winehq.com Summary : An MS Windows emulator (ALPHA) ....
On Sun, Dec 05, 2004 at 12:02:11PM +0100, Detlef Grittner wrote:
There seems to be a severe problem with the 64 bit Kernel of Suse 9.2.
I am using Tax 2004, it is a 32 bit application running on Wine. It has its own implementation of wine, which worked with Suse 9.0 and 9.1, but now I had to use the wine package that comes with Suse 9.2. After I had fixed the configuration of the paths, I was able to start the application. It crashes very often, which is not a problem in itself. But sometimes the screen freezes, the keyboard doesn't react anymore and finally even a ping to the freezing machine stops working. The only explanation I have is that the kernel has crashed. Interesting enough I can start the same application with Transgaming cedega and it doesn't crash or freeze the machine. (Not all parts of Tax are working with cedega, so I can't use it all the time.)
My assumption is that the wine package that comes with Suse 9.2 crashes the 64 bit kernel while running a 32 bit application in user space.
This is a very severe problem and I would rather see that only the 32 bit application crashes, but not the kernel. Without further assistance I can only guess what is happening here. Judging by the poor stability of wine it could be the NX feature or of course any other problem in the kernel.
Has anyone similar experiences with the new kernel?
We tested some Windows software in the 9.2 Wine and it worked. Could you perhaps connect a serial console (null modem to another machine and boot with console=ttyS0,baudrate) and try to capture any kernel output from the hang? -Andi
Am Dienstag, 14. Dezember 2004 15:13 schrieb Andi Kleen: ...
We tested some Windows software in the 9.2 Wine and it worked.
Could you perhaps connect a serial console (null modem to another machine and boot with console=ttyS0,baudrate) and try to capture any kernel output from the hang?
-Andi
I need some help with this debugging process. For the connection of the two machines I use a serial computer to computer cable. I have started the 64 bit machine with the above mentioned options "console=ttyS0,4800" (removed the splashscreen and vga, too) and the output no longer goes to tty0. On the other side I try to connect with minicom. The communication setttings are /dev/ttyS0 for the modem and the baudrate is set to 4800 N1. But I don't get any output or even a connection on the other side. Have I to do anything else than to initialize the modem in minicom? The OS running minicom is a Suse 9.0 by the way. Detlef
Andi Kleen wrote:
We tested some Windows software in the 9.2 Wine and it worked.
Could you perhaps connect a serial console (null modem to another machine and boot with console=ttyS0,baudrate) and try to capture any kernel output from the hang?
-Andi
Thanks Andi for your help. I have installed a new bios for my mainboard now and can't reproduce the hangs of the 32 bit software any longer. I will observe the software, but it looks like as if the problem is solved. Detlef
I just came in on this thread, so forgive me if I'm way off course here, but I noticed the comment on Wine. I'm running Codewarriors Crossover Office on my system and it's working perfectly with a variety of windows software. Tom On Thursday 23 December 2004 04:23 am, Detlef Grittner wrote:
Andi Kleen wrote:
We tested some Windows software in the 9.2 Wine and it worked.
Could you perhaps connect a serial console (null modem to another machine and boot with console=ttyS0,baudrate) and try to capture any kernel output from the hang?
-Andi
Thanks Andi for your help.
I have installed a new bios for my mainboard now and can't reproduce the hangs of the 32 bit software any longer. I will observe the software, but it looks like as if the problem is solved.
Detlef
-- Tom Nielsen Neuro Logic Systems 1.805.389.5435 x18 www.neuro-logic.com
participants (3)
-
Andi Kleen -
detlef.grittner＠t-online.de -
Tom Nielsen