Bug 36121 - starting Assassin's Creed Brotherhood (in wine) causes kernel freeze
Summary: starting Assassin's Creed Brotherhood (in wine) causes kernel freeze
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2011-04-10 15:44 UTC by Mike Kaplinskiy
Modified: 2019-11-19 08:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

dmesg from the freeze (78.49 KB, text/x-log)
2011-04-10 15:44 UTC, Mike Kaplinskiy
no flags Details
Better dmesg from the freeze (375.14 KB, text/plain)
2011-04-10 18:09 UTC, Mike Kaplinskiy
no flags Details

Description Mike Kaplinskiy 2011-04-10 15:44:00 UTC
Created attachment 45461 [details]
dmesg from the freeze

Once the game gets to the menu screen (after intros) it shows a white screen (as expected, but for too long). After a few seconds the white screen goes away, the fan stops, the monitor goes into standby, and the whole os is unresponsive (no sysrq keys). Rebooting shows no sign that the kernel even knows anything happened (in dmesg, etc).

This only occurs if you use wine with glsl=enabled. glsl=disabled shows a semi-corrupt menu which you can exit without killing your system.

I'm on kernel 2.6.39-rc2 (built with NMI) and mesa git from 2011/04/08 (xorg-edgers ppa). The card is a Barts chip (6870), and glxinfo shows I'm using r600g. Wine is version 1.3.17.

If it matters, the NMI never comes. The kernel is built with CONFIG_FB_RADEON_DEBUG=y , but it's still rather quiet around the crash.
Comment 1 Mike Kaplinskiy 2011-04-10 18:09:21 UTC
Created attachment 45463 [details]
Better dmesg from the freeze

I managed to get a better log, but unfortunately the stack trace is cut off before it gets completely printed. Any suggestions on what logs might be useful?
Comment 2 Martin Peres 2019-11-19 08:18:57 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/188.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.