[Bug 38953] Linux kernel version 4.2 will prevent Battle.net App from launching in Wine

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jul 20 12:36:09 CDT 2015


https://bugs.winehq.org/show_bug.cgi?id=38953

--- Comment #2 from Armin Altorffer <aapmak at gmail.com> ---
The offending event/output:

"wine: Unhandled page fault on write access to 0x0e03e9f6 at address 0x38607d98
(thread 004f), starting debugger..."

At which point it will simply abort execution and return to prompt. As stated,
4.1.x (and all versions prior) did not exhibit this phenomenon.

Personally bisecting the kernel is something that has always surprised me; even
though I do have the technical aptitude for it, it does remain something of a
time consuming and daunting process. It surprises me that people are requested
to personally do this sort of thing.

Moreover as in this particular case, the list of commits that is involved in
this phenomenon occurring is rather extensive. 4.1.2 is the last known working
kernel; 4.2.rc1 already sees it failing. The list of individual commits for
4.2.rc1 is quite extensive; it is one of the larger rc's in the history of the
Linux kernel. And as there are no individual compiles for each and every
individual commit, I would have to personally bisect the entire 4.2 rc1 kernel,
each individual commit. Compiling manually for every bisect attempt. Obviously,
it can be narrowed down a bit, but still, there are numerous possible causes.
Personally bisecting this on a less than cutting edge machine is probably going
to take weeks.

Most likely, it is related to low level ASM changes (a lot of work is being
done to migrate the low level ASM to C, in the kernel) but still, it could also
be related to some DRM work or maybe something else entirely.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list