Event 9 Device Time Out in the System Log

NTDEV
1

I am investigating an issue with a driver that I don’t have source access…

I get the following error in the Win2K system log:

Error 6/25/2003 12:06:45 AM custdrvr 9 N/A The
device, \Device\Scsi\custdrvr, did not respond within the timeout period.

Can anyone tell me where it is coming from? File System I suppose? On what
kind of I/O? Does the File system launch a timeout on each I/O? What is
happening in the driver when the timeout triggers? Does the driver get a
cancel I/O call?

Thanks

Fred

2

Hi,
Time out happens whenever Device Doesnt respond in a
certain timeout peroid.
What kind of driver you are using.
It can be a miniport driver for a SCSI/RAID
controller.
Try increasing the timeout peroid in the Disk Service.
See if it makes any difference.
It is not the FileSystem which launches a timeout but
the port driver.
If the concerned driver is a miniport driver, then
Reset is called and all the outstanding IOs are
completed with a status SRB_STATUS_BUS_RESET.

Hope it helps.

— xxxxx@Dell.com wrote:

I am investigating an issue with a driver that I
don’t have source access…

I get the following error in the Win2K system log:

Error 6/25/2003 12:06:45 AM custdrvr 9 N/A The
device, \Device\Scsi\custdrvr, did not respond
within the timeout period.

Can anyone tell me where it is coming from? File
System I suppose? On what
kind of I/O? Does the File system launch a timeout
on each I/O? What is
happening in the driver when the timeout triggers?
Does the driver get a
cancel I/O call?

Thanks

Fred

You are currently subscribed to ntdev as:
xxxxx@yahoo.com
To unsubscribe send a blank email to
xxxxx@lists.osr.com

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

3

SCSIPORT restarts the CDB after 1 second timeout. Check your SCSI cabling.

Max

----- Original Message -----
From:
To: “Windows System Software Developers Interest List”
Sent: Friday, July 18, 2003 2:21 AM
Subject: [ntdev] Event 9 Device Time Out in the System Log

> I am investigating an issue with a driver that I don’t have source access…
>
> I get the following error in the Win2K system log:
>
> Error 6/25/2003 12:06:45 AM custdrvr 9 N/A The
> device, \Device\Scsi\custdrvr, did not respond within the timeout period.
>
> Can anyone tell me where it is coming from? File System I suppose? On what
> kind of I/O? Does the File system launch a timeout on each I/O? What is
> happening in the driver when the timeout triggers? Does the driver get a
> cancel I/O call?
>
> Thanks
>
> Fred
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com