[Hardy][wine][regression] Segmentation Fault in Palm Hotsync over serial

Bug #235613 reported by jan
4
Affects Status Importance Assigned to Milestone
Wine
New
Medium
rt2x00 Project
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned
wine (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: wine

I upgraded to Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362

Now it crashes half-way synchronising over the serial port, sometimes after a
few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further
information
$ wine hotsync.exe
Segmentation fault
$

I do not know if this means that a part of Wine crashes, or just the
application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0

It is disappointing that an application that used to work fine, and I came to
depend on, is now broken.
Logging can be found at Wine HQ:
http://bugs.winehq.org/show_bug.cgi?id=13296
---
I've recompiled with several versions of wine, especially those that did work with Gutsy.
The problem does not disappear. Therefore, I think it's not a change in wine that triggers the problem, but rather a problem in another module in Hardy.
---
I just got the kernel upgrade from vmlinuz-2.6.24-16 to vmlinuz-2.6.24-17 (patch for Ubuntu Hardy).
Now, the problem is less frequent.
It seems that I can introduce the failure by switching electrical equipment nearby. Therefore, I think that the crash occurs after a severe communications failure.
Apparently, Hardy generates them, even with no ambient influences, where Gutsy didn't.

lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

Tags: cft-2.6.27
Revision history for this message
In , Austin English (austinenglish) wrote :

Please run a regression test:

http://wiki.winehq.org/RegressionTesting

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

I did rebuilds all the way back to "git checkout wine-0.9.50".
The problem reproduces all the way back to those versions.
This means that ANY of those builds of wine shows this problem under Ubuntu Hardy (kernel version 2.6.24-16-generic). This wine application did not show this bug under Gutsy (kernel version linux-2.6.22.14).

I guess some function now returns a value that it didn't before.
I'm not sure what to do now, as the problem now seems to lie somewhere in the middle between wine and Ubuntu linux core development.

Note: The behavior at start-up changed to the behavior of those earlier versions: the iconified version did not show up at the desktop.

Revision history for this message
In , Austin English (austinenglish) wrote :

(In reply to comment #2)
> I did rebuilds all the way back to "git checkout wine-0.9.50".
> The problem reproduces all the way back to those versions.
> This means that ANY of those builds of wine shows this problem under Ubuntu
> Hardy (kernel version 2.6.24-16-generic). This wine application did not show
> this bug under Gutsy (kernel version linux-2.6.22.14).
>
> I guess some function now returns a value that it didn't before.
> I'm not sure what to do now, as the problem now seems to lie somewhere in the
> middle between wine and Ubuntu linux core development.
>
> Note: The behavior at start-up changed to the behavior of those earlier
> versions: the iconified version did not show up at the desktop.
>

Have you filed a bug with ubuntu? You might try switching kernels under gutsy or hardy to see if that's where the problem is...

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Created an attachment (id=13443)
Logging from Wine

Filed bug at Ubuntu under:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/235613

I just got the kernel upgrade from vmlinuz-2.6.24-16 to vmlinuz-2.6.24-17 (patch for Ubuntu Hardy).
Now, the problem is less frequent.
It seems that I can introduce the failure by either
1) switching electrical equipment nearby.
2) switching on the logging (as for attached file)
Therefore, I think that the crash occurs after a communications / timing failure.
Apparently, Hardy generates them, even with no ambient influences, where Feisty didn't.

Probably unrelated: at end of a succesful synchronisation, I now get :
fixme:comm:io_control Unsupported
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 000000c0

Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Binary package hint: wine

I upgraded to Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362

Now it crashes half-way synchronising over the serial port, sometimes after a
few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further
information
$ wine hotsync.exe
Segmentation fault
$

I do not know if this means that a part of Wine crashes, or just the
application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0

It is disappointing that an application that used to work fine, and I came to
depend on, is now broken.
Logging can be found at Wine HQ:
http://bugs.winehq.org/show_bug.cgi?id=13296
---
I've recompiled with several versions of wine, especially those that did work with Gutsy.
The problem does not disappear. Therefore, I think it's not a change in wine that triggers the problem, but rather a problem in another module in Hardy.
---
I just got the kernel upgrade from vmlinuz-2.6.24-16 to vmlinuz-2.6.24-17 (patch for Ubuntu Hardy).
Now, the problem is less frequent.
It seems that I can introduce the failure by switching electrical equipment nearby. Therefore, I think that the crash occurs after a severe communications failure.
Apparently, Hardy generates them, even with no ambient influences, where Gutsy didn't.

lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

Changed in openvz-kernel:
status: Unknown → New
Revision history for this message
Daniel Hahler (blueyed) wrote :

Not a bug in OpenVZ.

Changed in openvz-kernel:
status: New → Invalid
Changed in wine:
status: Unknown → New
Revision history for this message
Scott Ritchie (scottritchie) wrote :

This appears to be a kernel issue and not a Wine one, then. Thank you for reporting!

Changed in wine:
status: New → Invalid
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Since the latest wine upgrade (wine-1.1.1) I get the following error message as well at the time of the crash:
err:seh:setup_exception_record nested exception on signal stack in thread 0009 eip 7bc65efa esp 7ffdb900 stack 0x232000-0x330000
$ uname -a
Linux his08 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Still crashes wine-1.1.6 with and kernel 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux

err:seh:setup_exception_record nested exception on signal stack in thread 0009 eip 7bc6688a esp 7ffdb900 stack 0x232000-0x330000

Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

It may have to do with the inclusion of the new rt2500 driver in the kernel at the time the bug started to appear.
The behavior vanishes (= workaround) if I do the following commands before and after the hotsync.
 sudo ifdown wlan0
  ... then hotsync
 sudo ifup wlan0

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Disappeared after upgrading to Ubuntu Intrepid, kernel version
2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
May have been kernel (rt2500 netwrok driver ?) bug.

Revision history for this message
In , Vitaliy-bugzilla (vitaliy-bugzilla) wrote :

Not Wine bug - invalid.

Revision history for this message
In , Vitaliy-bugzilla (vitaliy-bugzilla) wrote :

Closing

Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Disappeared after upgrading to Ubuntu Intrepid, kernel version
2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
May have been kernel (rt2500 netwrok driver ?) bug.

Changed in rt2x00:
status: New → Fix Released
Changed in linux:
status: New → Fix Released
Changed in wine:
status: New → Invalid
Changed in wine:
importance: Unknown → Medium
Changed in wine:
status: Invalid → Won't Fix
Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Problem keeps appearing.
I thought it had to do with an USB / serial converter I used on my Ubuntu 10.04 system.
Now, on a brand-new Ubuntu 12.04 system with a direct serial link, wine with that version yields the same crash, but with a little different eip: 7bc7962a.

Lowering the baud rate makes everything slower. The crash appears later in the program.

This must be a wine bug.

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Created attachment 43722
output of WINEDEBUG=+relay,+seh,+tid wine hotsync.exe > /tmp/output.txt 2>&1

error output on line 729097

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Comment on attachment 43722
output of WINEDEBUG=+relay,+seh,+tid wine hotsync.exe > /tmp/output.txt 2>&1

wine --version:
wine-1.5.24

Changed in wine:
status: Won't Fix → New
Revision history for this message
In , Austin English (austinenglish) wrote :

Is this still an issue in current (1.7.36 or newer) wine? There were some serial fixes a while back that may have helped.

Revision history for this message
In , Imwellcushtymelike (imwellcushtymelike) wrote :

(In reply to Jan Hoogenraad from comment #6)
> Disappeared after upgrading to Ubuntu Intrepid, kernel version
> 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
> May have been kernel (rt2500 netwrok driver ?) bug.

(In reply to Jan Hoogenraad from comment #9)
> Problem keeps appearing.
> I thought it had to do with an USB / serial converter I used on my Ubuntu
> 10.04 system.
> Now, on a brand-new Ubuntu 12.04 system with a direct serial link

You need to make your mind up if the problem is with Wine or with Ubuntu. The Ubuntu bug has been closed fixed.

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

It is not solved by the 1.7 changes.
wine --version : wine-1.8

Linux 3.13.0-83-generic #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

yields the same error. I will attach the log.

Revision history for this message
In , Jan-winehq (jan-winehq) wrote :

Created attachment 54098
output of WINEDEBUG=+relay,+seh,+tid wine hotsync.exe > /tmp/output.txt 2>&

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.