http://bugs.winehq.org/show_bug.cgi?id=58335
--- Comment #52 from Bernhard Übelacker bernhardu@mailbox.org --- (In reply to Dmitry Timoshkov from comment #44)
I had similar reports that starting from wine-10.9 on machines without AVX wine no longer works, while wine-10.8 worked. Reverting at least commits e397ed180d6b85b8d410e29153c7bfd297708f55 9d4faa32d012300036b387a01aed872f807e0e06 4a5fade673955be5d647c0212846af4c2d7ed212 fixed the problem.
If load addresses match and symbol files are ok, then the instruction at 0x6fffffc4c5b3 is just a mov instruction, which I guess is available already before avx.
0x00006fffffc4c5b3 <parse_manifest+83>: mov 0x28(%rbp),%r8
This would mean the problematic instruction got executed before, unfortunately without logging output.
This time I have started my test Fedora VM with qemu option "-cpu Penryn", which results in lscpu also not showing avx. "Unfortunately" winecfg opens properly inside this VM.