http://bugs.winehq.org/show_bug.cgi?id=20048
Summary: DeviceIoControl() return size of zero returned not returned correctly to lpBytesReturned Product: Wine Version: 1.1.29 Platform: PC URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs@winehq.org ReportedBy: ray@pobox.co.uk
Created an attachment (id=23594) --> (http://bugs.winehq.org/attachment.cgi?id=23594) Screen inage showing returned size of 0x511D24
SIV (http://rh-software.com/) is reporting PCI device information after HalGetBusData() has returned a size of zero which it then passed back to complete the I/O control with a success status, however it does not come back as zero (See attached screen image), but a large pseudo random number, 0x511D24 on this osasion. To reproduce this downlaod and run SIV 4.01, press [PCI Bus] and then select a device.
http://bugs.winehq.org/show_bug.cgi?id=20048
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|DeviceIoControl | Severity|normal |enhancement
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-14 20:38:49 --- What IOCTL code and to what device did you sent? Did it succeeded?
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #2 from red-ray ray@pobox.co.uk 2009-09-15 07:56:03 --- (In reply to comment #1)
What IOCTL code and to what device did you sent? Did it succeeded?
As regards "Did it succeeded?" that is an imprecise question, it all depends what you mean my "succeeded". I think you are asking did my driver pass back a status of STATUS_SUCCESS, to which the answer is YES.
The request was processed by my SIVDRIVER with the device name being \Device\SIVDRIVER and the Symbolic Link being SIVDRIVER. The function being used by the failure I reported is defined as:
#define IOCTL_SIV_PCIBUS CTL_CODE( 0, 0x10, METHOD_BUFFERED, FILE_ANY_ACCESS )
The actual function code does not really matter, ALL the METHOD_BUFFERED I have tested fail in the same way.
Given an incorrect length is returned, this is clearly an error (at least), what makes you incorrectly classify this as an enhancement ?
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2009-09-15 08:39:50 --- Please attach +vxd,+ntoskrnl,+ntdll log.
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #4 from red-ray ray@pobox.co.uk 2009-09-15 10:59:37 --- Created an attachment (id=23610) --> (http://bugs.winehq.org/attachment.cgi?id=23610) +vxd,+ntoskrnl,+ntdll log
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #5 from red-ray ray@pobox.co.uk 2009-09-15 11:00:54 --- (In reply to comment #4)
Created an attachment (id=23610)
--> (http://bugs.winehq.org/attachment.cgi?id=23610) [details]
+vxd,+ntoskrnl,+ntdll log
The length I actually got back for the attached log was 2130440043/0x7EFBEF6B
http://bugs.winehq.org/show_bug.cgi?id=20048
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #23610|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=20048
Saulius K. saulius2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=20048
ray@pobox.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ray@pobox.co.uk
http://bugs.winehq.org/show_bug.cgi?id=20048
ray@rh-software.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |minor
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #6 from ray@rh-software.com 2011-04-16 17:49:40 CDT --- Given an incorrect length is returned, this is clearly an error (at least), what makes you incorrectly classify this as an enhancement ?
http://bugs.winehq.org/show_bug.cgi?id=20048
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |RESOLVED CC| |focht@gmx.net Resolution| |FIXED Summary|DeviceIoControl() return |SIV (System Information |size of zero returned not |Viewer) shows incorrect PCI |returned correctly to |device information |lpBytesReturned |
--- Comment #7 from Anastasius Focht focht@gmx.net 2011-12-22 05:02:04 CST --- Hello,
can't reproduce. The current version 4.24 doesn't exhibit this behaviour. Unfortunately older versions of the app are not available to test with (even external sites have their old downloads pulled).
Marking fixed. Reopen if you can reproduce with _recent_ Wine version.
$ sha1sum siv.zip 2d4b3f431db2f8d10b6b6553b26e195cf5d7d56a siv.zip
$ wine --version wine-1.3.35-117-g27e3e1a
Regards
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #8 from Saulius K. saulius2@gmail.com 2011-12-22 11:44:47 CST --- Given the caption in the screen image and following forum msgs, that could be very much v4.00 - v4.01 we are interested in: http://forum.lowyat.net/index.php?showtopic=1162493&st=0&p=28613988
I've got v4.01 here: http://www.downdownz.com/download/view-software-9456.html
The link called 电信下载.
But my wine (not very recent, v1.3.10) exhibits different bug (it's unable to start SIVDRIVER svc / SIVNT4.SYS).
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #9 from Anastasius Focht focht@gmx.net 2011-12-22 14:10:25 CST --- Hello Saulius,
-- quote --- I've got v4.01 here: http://www.downdownz.com/download/view-software-9456.html
The link called 电信下载. -- quote ---
the initial bug report talked about "To reproduce this downlaod and run SIV 4.01, press [PCI Bus] and then select a device" so v4.01 seems to be correct.
-- quote --- But my wine (not very recent, v1.3.10) exhibits different bug (it's unable to start SIVDRIVER svc / SIVNT4.SYS). -- quote ---
$ wine --version wine-1.3.35-117-g27e3e1a
--- snip --- 0027:trace:loaddll:load_native_dll Loaded L"C:\windows\system32\Drivers\SIVNT4.sys" at 0x540000: native 0027:fixme:ntoskrnl:HalGetBusData (4 0 0 0x111564 4) stub! 0027:trace:seh:raise_exception code=c0000096 flags=0 addr=0x5427c7 ip=005427c7 tid=0027 0027:trace:seh:raise_exception eax=00000020 ebx=001113a8 ecx=0000002e edx=0053002e esi=001113a8 edi=001113c0 0027:trace:seh:raise_exception ebp=0053e5d4 esp=0053e5b8 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010246 0027:trace:seh:call_vectored_handlers calling handler at 0x683f63f6 code=c0000096 flags=0 0027:trace:seh:call_vectored_handlers handler at 0x683f63f6 returned 0 0027:trace:seh:call_stack_handlers calling handler at 0x7bc919e1 code=c0000096 flags=0 wine: Unhandled privileged instruction at address 0x5427c7 (thread 0027), starting debugger... ... <restarting driver over and over again> --- snip ---
The reason is direct i/o port access in driver entry using "out dx,al" -> not the problem that is reported here.
Regards
http://bugs.winehq.org/show_bug.cgi?id=20048
--- Comment #10 from Saulius K. saulius2@gmail.com 2011-12-22 14:33:05 CST --- That confirms your verdict from comment #7 :). Finished, thanks.
http://bugs.winehq.org/show_bug.cgi?id=20048
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org 2011-12-30 12:56:16 CST --- Closing bugs fixed in 1.3.36.