http://bugs.winehq.org/show_bug.cgi?id=25087
Summary: GPU-Z shows no informations Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: testing.tigerwolf@mail.com
Created an attachment (id=31809) --> (http://bugs.winehq.org/attachment.cgi?id=31809) GPU-Z launching back trace
GPU-Z shows any information : all fields remains empty.
OS : Ubuntu 10.10 amd-64 GPU : ATI Radeon HD Tested version : GPU-Z v0.4.8 Wine : 1.3.6
http://bugs.winehq.org/show_bug.cgi?id=25087
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-10 00:45:03 CST --- Do not create duplicates.
*** This bug has been marked as a duplicate of bug 11908 ***
http://bugs.winehq.org/show_bug.cgi?id=25087
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-10 00:45:18 CST --- Closing duplicate.
http://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #3 from testing.tigerwolf@mail.com 2010-11-10 01:34:46 CST --- Is it really the same bug as described in #11908 ?
This one concerns GPU-Z instead of CPU-Z for #11908.
Moreover the back traces are different.
http://bugs.winehq.org/show_bug.cgi?id=25087
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|DUPLICATE |
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-10 04:21:23 CST --- Sorry, missed G vs. C difference.
http://bugs.winehq.org/show_bug.cgi?id=25087
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |http://www.techpowerup.com/ | |downloads/1969/TechPowerUp_ | |GPU-Z_v0.5.2.html Ever Confirmed|0 |1
--- Comment #5 from Austin English austinenglish@gmail.com 2011-04-02 17:56:13 CDT --- Confirming in 1.3.17.
Bit more info now though: ixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created device: \Device\GPU-Z fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created link: ??\GPU-Z -> \Device\GPU-Z fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x117348 wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 0032), starting debugger... fixme:systray:wine_notify_icon unhandled tray message: 4 fixme:wininet:set_cookie persistent cookies not handled (L"expires=Sun, 01-Apr-2012 22:54:42 GMT; path=/; domain=.techpowerup.com") fixme:wininet:set_cookie persistent cookies not handled (L"expires=Sun, 01-Apr-2012 22:54:42 GMT; path=/; domain=.techpowerup.com") fixme:wininet:InternetLockRequestFile STUB err:service:service_send_control service protocol error - failed to write pipe!
Setting win98 mode doesn't workaround the ntoskrnl problem.
http://bugs.winehq.org/show_bug.cgi?id=25087
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=25087
testing.tigerwolf@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #31809|0 |1 is obsolete| |
--- Comment #6 from testing.tigerwolf@mail.com 2011-04-09 09:34:13 CDT --- Created an attachment (id=34002) --> (http://bugs.winehq.org/attachment.cgi?id=34002) GPU-Z 0.5.3 execution backtrace on wine 1.3.17
http://bugs.winehq.org/show_bug.cgi?id=25087
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #34002|application/octet-stream |text/plain mime type| | Attachment #34002|backtrace_GPUZ |backtrace_GPUZ.txt filename| |
http://bugs.winehq.org/show_bug.cgi?id=25087
testing.tigerwolf@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #34002|0 |1 is obsolete| |
--- Comment #7 from testing.tigerwolf@mail.com 2011-11-05 16:43:10 CDT --- Created attachment 37328 --> http://bugs.winehq.org/attachment.cgi?id=37328 GPU-Z 0.5.4 execution backtrace on wine 1.3.32
http://bugs.winehq.org/show_bug.cgi?id=25087
testing.tigerwolf@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #37328|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #8 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-06 09:42:51 CST --- This would probably be a won't fix. Windows drivers that talk to hardware won't work on Wine.
http://bugs.winehq.org/show_bug.cgi?id=25087
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Summary|GPU-Z shows no informations |GPU-Z shows no informations | |(helper kernel driver uses | |privileged rdmsr and wrmsr | |instructions to access | |MSRs)
--- Comment #9 from Anastasius Focht focht@gmx.net 2011-11-06 10:56:12 CST --- Hello,
the GPU-Z helper kernel driver tries to read MSR which requires ring 0 privileges, hence the exception:
--- snip --- 002b:trace:seh:raise_exception code=c0000005 flags=0 addr=0x541b9c ip=00541b9c tid=002b 002b:trace:seh:raise_exception info[0]=00000000 002b:trace:seh:raise_exception info[1]=ffffffff 002b:trace:seh:raise_exception eax=00000004 ebx=0053e700 ecx=0000002a edx=0053ef8c esi=0053e690 edi=0011aa30 002b:trace:seh:raise_exception ebp=0053e668 esp=0053e658 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210246 002b:trace:seh:call_vectored_handlers calling handler at 0x7ece433f code=c0000005 flags=0 002b:trace:seh:call_vectored_handlers handler at 0x7ece433f returned 0 002b:trace:seh:call_stack_handlers calling handler at 0x7bc98061 code=c0000005 flags=0 002b:Call KERNEL32.UnhandledExceptionFilter(0053e130) ret=7bc9809b wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 002b), starting debugger...
Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:00541b9c ESP:0053e658 EBP:0053e668 EFLAGS:00210246( R- -- I Z- -P- ) EAX:00000004 EBX:0053e700 ECX:0000002a EDX:0053ef8c ESI:0053e690 EDI:0011aa30 Stack dump: 0x0053e658: 0053e700 0000002b 7ecfbff4 00000000 0x0053e668: 0053e778 7ece4afa 00121cc0 0053e690 0x0053e678: 00541b00 00121cc0 0053e690 00000008 0x0053e688: 00000002 7ffd0000 55555555 0053e724 0x0053e698: 55555555 0011aa30 55555555 55555555 0x0053e6a8: 55555555 55555555 55555501 55555555 Backtrace: =>0 0x00541b9c in gpu-z.sys (+0x1b9c) (0x0053e668) 1 0x7ece4afa process_ioctl+0x226(device=0x121cc0, code=0x80006448, in_buff=0x11aa30, in_size=0x4, out_buff=0x11aa48, out_size=0x53e7b8) [/home/focht/projects/wine/wine-git/dlls/ntoskrnl.exe/ntoskrnl.c:182] in ntoskrnl (0x0053e778) 2 0x7ece4f3a wine_ntoskrnl_main_loop+0x3a8(stop_event=0x30) [/home/focht/projects/wine/wine-git/dlls/ntoskrnl.exe/ntoskrnl.c:252] in ntoskrnl (0x0053e898) 3 0x7bc6843e call_entry_point+0x29() in ntdll (0x0053e8b8) 4 0x7bc68669 relay_call+0x1bb(descr=0x7ed09ff4, idx=0x105cb, stack=0x53e91c) [/home/focht/projects/wine/wine-git/dlls/ntdll/relay.c:434] in ntdll (0x0053e908) 5 0x7ece3405 in ntoskrnl (+0x13404) (0x0053e988) 6 0x7ed8b6a0 ServiceMain+0x156(argc=0, argv=0x11a7a0) [/home/focht/projects/wine/wine-git/programs/winedevice/device.c:297] in winedevice (0x0053e988) 7 0x7ed4e431 service_thread+0x165(arg=0x1192d0) [/home/focht/projects/wine/wine-git/dlls/advapi32/service.c:294] in advapi32 (0x0053ea28) 8 0x7bc7f3e4 call_thread_func_wrapper+0xb() in ntdll (0x0053ea38) 9 0x7bc7f42d call_thread_func+0x3e(entry=0x7ed4e2cb, arg=0x1192d0, frame=0x53eb38) [/home/focht/projects/wine/wine-git/dlls/ntdll/signal_i386.c:2532] in ntdll (0x0053eb18) 10 0x7bc7f3c2 call_thread_entry_point+0x11() in ntdll (0x0053eb38) 11 0x7bc86fdf start_thread+0x1c6(info=0x7ffd0fb8) [/home/focht/projects/wine/wine-git/dlls/ntdll/thread.c:405] in ntdll (0x0053f398) 12 0xb75a4d31 start_thread+0xd0() in libpthread.so.0 (0x0053f498) 0x00541b9c: rdmsr Modules: Module Address Debug info Name (29 modules) PE 540000- 54b000 Export gpu-z.sys --- snip ---
MSR read code (driver ioctl handler):
--- snip --- ... .text:00541B97 mov edi, [esi+0Ch] .text:00541B9A mov ecx, [edi] .text:00541B9C rdmsr .text:00541B9E mov [edi], eax .text:00541BA0 mov [edi+4], edx ... --- snip ---
MSR write code (driver ioctl handler):
--- snip --- ... .text:00541BCF mov edx, [esi+0Ch] .text:00541BD2 mov ecx, [edx] .text:00541BD4 mov eax, [edx+4] .text:00541BD7 mov edx, [edx+8] .text:00541BDA wrmsr ... --- snip ---
Both instructions cause exceptions hence you could emulate them - at least to prevent the crash.
For real data you would need "msr" kernel module configured/loaded that allows userspace apps to access those registers though the drivers ioctl interface.
Regards
http://bugs.winehq.org/show_bug.cgi?id=25087
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |hardware
http://bugs.winehq.org/show_bug.cgi?id=25087
Christian Costa titan.costa@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |titan.costa@gmail.com
--- Comment #10 from Christian Costa titan.costa@gmail.com 2012-10-17 14:29:53 CDT --- I've just tested and I don't see any crash with rdmsr or wrmsr instructions. Nothing is displayed though.
http://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #11 from Austin English austinenglish@gmail.com 2012-10-17 15:26:42 CDT --- (In reply to comment #10)
I've just tested and I don't see any crash with rdmsr or wrmsr instructions. Nothing is displayed though.
I see a crash (no backtrace though, even with winedbg): fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:thread:GetThreadPreferredUILanguages 52, 0x32b800, 0x32ba7c 0x32b808 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created device: \Device\GPU-Z fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created link: ??\GPU-Z -> \Device\GPU-Z fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x113478 wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 003a), starting debugger...
http://bugs.winehq.org/show_bug.cgi?id=25087
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |levanchelidze@gmail.com
--- Comment #12 from Austin English austinenglish@gmail.com 2013-03-15 16:49:18 CDT --- *** Bug 33215 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #13 from testing.tigerwolf@mail.com 2013-06-26 05:05:58 CDT --- Created attachment 44985 --> http://bugs.winehq.org/attachment.cgi?id=44985 GPU-Z 0.7.2 execution backtrace on wine 1.6-rc3
Same problem using wine 1.6-rc3
http://bugs.winehq.org/show_bug.cgi?id=25087
Jarkko K jarkko_korpi@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi@hotmail.com
--- Comment #14 from Jarkko K jarkko_korpi@hotmail.com --- There is no change wine 1.7.18, still not showing anything.
debug shows
fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:thread:GetThreadPreferredUILanguages 52, 0x33b7f0, 0x33ba6c 0x33b7f8 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created device: \Device\GPU-Z fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPU-Z(IRQL 00): Created link: ??\GPU-Z -> \Device\GPU-Z fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x1124a8 fixme:systray:wine_notify_icon unhandled tray message: 4 fixme:urlmon:InternetBindInfo_GetBindString not supported string type 20
https://bugs.winehq.org/show_bug.cgi?id=25087
Teras teras@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |teras@luukku.com
--- Comment #15 from Teras teras@luukku.com --- the same wine-1.7.37-143-g3b2cf06
https://bugs.winehq.org/show_bug.cgi?id=25087
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #16 from super_man@post.com --- still an issue
1.7.51
https://bugs.winehq.org/show_bug.cgi?id=25087
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
https://bugs.winehq.org/show_bug.cgi?id=25087
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
https://bugs.winehq.org/show_bug.cgi?id=25087
exposight exposight@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |exposight@gmail.com
--- Comment #17 from exposight exposight@gmail.com --- On wine 4.18 x64 the GPU-Z 2.26.0 shows and error message "Could not start driver" and closes. Console:
DbgPrint says: (null) (IRQL 00): INFO Driver compiled at 16:10:42 on Jul 25 2019 002f:fixme:ntoskrnl:MmGetSystemRoutineAddress L"IoCreateDeviceSecure" not found wine: Unhandled page fault on read access to 0xffffffff at address 0000000140008C1C (thread 002f), starting debugger...
GPU-Z 1.9.0 opens without error, but shows no info.
https://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #18 from Artem S. Tashkinov aros@gmx.com --- (In reply to exposight from comment #17)
On wine 4.18 x64 the GPU-Z 2.26.0 shows and error message "Could not start driver" and closes. Console:
DbgPrint says: (null) (IRQL 00): INFO Driver compiled at 16:10:42 on Jul 25 2019 002f:fixme:ntoskrnl:MmGetSystemRoutineAddress L"IoCreateDeviceSecure" not found wine: Unhandled page fault on read access to 0xffffffff at address 0000000140008C1C (thread 002f), starting debugger...
GPU-Z 1.9.0 opens without error, but shows no info.
Don't expect this bug report to be solved ever.
Wine can't and won't load Windows drivers.
https://bugs.winehq.org/show_bug.cgi?id=25087
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #19 from Zebediah Figura z.figura12@gmail.com --- (In reply to Artem S. Tashkinov from comment #18)
Don't expect this bug report to be solved ever.
Wine can't and won't load Windows drivers.
May or may not be true, but ultimately in this case probably the better solution is to use native utilities.
https://bugs.winehq.org/show_bug.cgi?id=25087
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #20 from testing.tigerwolf@mail.com --- GPUZ 2.36.0 crashes with error window "waiting times exceeded"
Backtraces added
https://bugs.winehq.org/show_bug.cgi?id=25087
--- Comment #21 from testing.tigerwolf@mail.com --- Created attachment 68758 --> https://bugs.winehq.org/attachment.cgi?id=68758 GPU-Z 2.36.0 execution backtrace on wine 5.22