RE: Windows implementation of iSCSI

["ERICKSON,SHAWN (HP-Roseville,ex1)" <shawn_erickson@hp.com>]

I would switch to using a check build of Windows 2000 and building symbols
for your driver. Then get it to fail again and read the page fault
information to understand when and where it is happening.

You are accessing memory that you should not be, are accessing memory that
is not locked and wired into RAM (it has to be if you are going to do any
DMA) or some other piece of software is failing.

In a miniport you usually get locked and wired buffers so its hard to know
what is going on from the simple report below.

Anyways... this is really a Window development issue not a iSCSI issue. So I
don't think this list will be of much help, try Windows kernel dev or SCSI
miniport related lists (I know ones exist).

-Shawn

-----Original Message-----
From: Sarita_Padoshi [mailto:Sarita_Padoshi@satyam.com]
Sent: Monday, April 14, 2003 6:10 AM
To: ips@ece.cmu.edu
Subject: Windows implementation of iSCSI
Importance: High


Hi,

	We are developing an iSCSI initiator on Windows 2000 as a SCSI
miniport driver.

	The initiator passes through the SCSI commands INQUIRY and READ
CAPACITY. 

	After this, a READ command for the block address 0 is received at
the initiator.

	This command is executed at the target and the response is SUCCESS.
	The same response is sent back to the scsi port driver with
SrbStatus = SRB_STATUS_SUCCESS and
	ScsiStatus = SUCCESS and the data copied to DataBuffer in the SRB.
	
	Next ,We receive a second READ command for the same block address 0
with same transfer length. 
	Now,when we copy the data received from the target to the DataBuffer
in the SRB, there is a
	Page Fault.

	Could you please help us in understanding why a second read command
is issued and why there is
	a page fault.

	Thanks in advance.

Rgds,
Sarita
************************************************************************** 
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**************************************************************************