RE: Re[5]: [ros-kernel] Finally have good stack trace on crash I' m experiencing...

[Hey M. <Mat...@NB...>]

Is it missing a Retries++ in the for loop by any chance????

-----Original Message-----
From: Royce Mitchell III [mailto:ro...@ev...]
Sent: Thursday, 5 September 2002 8:48 a.m.
To: rea...@li...
Subject: Re[5]: [ros-kernel] Finally have good stack trace on crash I'm
experiencing...


Eric,

I put in the following code where you suggested. The OS is locking up
before it gets to the page fault. I don't have the screen capture, but
will get it to you as soon as I get a chance.

>  if (DeviceStatus & IDE_SR_BUSY)
>  {
>    /* Wait for BUSY to drop */
>    for (Retries = 0; Retries < IDE_MAX_BUSY_RETRIES; Retries)
>    {
>      DeviceStatus = IDEReadStatus(CommandPortBase);
>      if (!(DeviceStatus & IDE_SR_BUSY))
>      {
>        break;
>      }
>      ScsiPortStallExecution(10);
>    }
>    if (Retries >= IDE_MAX_BUSY_RETRIES)
>    {
>      DPRINT1("Drive is BUSY for too long\n");
>      /* FIXME: handle timeout */
>    }
>  }



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
reactos-kernel mailing list
rea...@li...
https://lists.sourceforge.net/lists/listinfo/reactos-kernel
This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or retain it.
If you have received it in error please immediately notify me by return email
and delete the emails.
Thank you.