Bug 9649 - SC-5200 + wine = System freeze
SC-5200 + wine = System freeze
Status: REJECTED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA)
All Linux
: P1 normal
Assigned To: Jaroslav Kysela
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-27 16:13 UTC by HisChild
Modified: 2008-09-26 07:06 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.22-14
Tree: Mainline
Regression: ---


Attachments

Description HisChild 2007-12-27 16:13:10 UTC
Most recent kernel where this bug did not occur: UnknownDistribution: Ubuntu 7.10 64-bit
Hardware Environment:
-- Processor: Amd Athlon 3800+ X2 2,0 Ghz
-- Ram: 2 Gb ram
-- Motherboard: Asus A8R-MVP
-- Harddrive: Samsung 200Gb
-- Soundcard 1: Onboard
-- Soundcard 2: Trust SC-5200
Software Environment:
-- Clean installation of Ubuntu 7.10 64-bit with latest wine (0.9.51) installed. 
Problem Description:
Running any part of wine freezes up the whole system. Both SSH connections, the normal X screen and any other device, including sound played by for example music players, freezes up. After about 10 seconds the system reboots.
Steps to reproduce:
Run any part of wine on the system described above. 
Other notes:
By removing my second sound card it works. By disabling my onboard sound it still causes the freeze. 
Attempting to connect by ssh and other methods have failed.
Comment 1 Takashi Iwai 2008-02-12 03:45:24 UTC
The description is too ambiguous.  Please make clear some facts:

- Do you mean "disabling the onboard sound without any extra soundcard causes the freeze", or "disabling the onboard sound and with the extra soundcard causes the freeze"?

- Which drivers are used for the sound devices?

- Any program except for wine causes this bug?

- Any kernel oops or panic messages?  What about serial console connection?  No alt-sysrq response?

- Does the problem appear on newer kernels? 
Comment 2 Roland Kletzing 2008-03-30 04:57:26 UTC
any update on this?
could you provide the needed information

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