http://bugs.winehq.org/show_bug.cgi?id=29294
--- Comment #28 from Jörg Höhle hoehle@users.sourceforge.net 2012-03-07 15:26:59 CST --- James, multi-MB logs from a closed source app are not as helpful to me as logs produced by the Wine tests where everybody can look at the source and see what the test app does. I saw nothing in the log that wasn't mentioned in comment #21 already, e.g. repeated "out of the blue underruns" 120-140ms apart, with padding around 4000 frames, CreateTimerQueue slew and DSound letting padding slowly decrease. IOW, you system acts like Antonio's.
What would help me is to systematically perform the tests mentioned in comment #17 and comment #21. Do the WINETEST_INTERACTIVE render tests produce good output? The winmm ones? The dsound ones? Additionally, what if you increase EXTRA_SAFE_RT to 300000 (30ms) in dlls/winealsa.drv/mmdevdrv.c or even beyond that value?
It seems that your logs were not generated using the >> append-mode trick mentioned above, were they? Some lines are simply missing, or something odd is going on with Wine's logging. E.g. where's the line about "pad:" or "XRun" that must precede:
27.015:0050:trace:alsa:alsa_write_data lead-in 1009
It cannot be:
27.005:0050:trace:alsa:alsa_write_data pad: 3954
because thread 005c managed to grab the device's critical section in-between.