On Thu, 22 Jul 1999, Gerard Roudier wrote:

>             --------------------------------
>             BRAVO!!!!!!!!!!!!!!!!!!!!!!!!!!!
>             --------------------------------

To you Lance, but not to me. :(

> The test against BUS connected was kind of check for safety, but indeed 
> it is not that smart. Will study the situation and let you know.
> For now, I am not sure if removing it is really safe.

This test is just stupid and must be removed.
Could you check if removing it fixes the problem?

> Your bug tracking has been kind of perfection. Obviously, if a bug has 
> to be stated, it is a driver bug. But, in normal situations, no SCSI 
> interrupts should happen, so it cannot be stated as a serious bug.
> If the driver recovers, then it is just usual "room for improvement", 
> in my opinion. :-)

Was "much room" here.

Thanks for your help,
   G�rard.

> On Thu, 22 Jul 1999, D. Lance Robinson wrote:
> 
> > Gerard,
> > 
> > Here is what seems to be happening.
> > 
> >  1) Send Write command to device X, it disconnects.
> >  2) Issue Test Test Unit Ready command to non-existant device Y.
> >  3) This times out and goes into the interrupt service routine (isr).
> >  4) The isr reads the status bits. Somehow the chip is enabled.
> >  5) Device X reselects (before the isr is finished)
> >  6) The isr thinks it is connected because of the error.
> >  7) The isr does a reset.
> >  8) More bad things happen.
> > 
> > NOTE:
> > To test this theory, I changed ncr_recover_scsi_int() with the following
> > code...
> > 
> >     if (scntl1 & ISCON) {
> >             if (hsts==HS_SEL_TIMEOUT)
> >                     printk( "SEL Timeout, but host is connected!?\n");
> >             goto reset_all;
> >     }
> > 
> > The message does get triggered.
> > 
> > Any clues on how to prevent the reconnect before the error handler has
> > done its thing? Is this a chip bug?   NOTE: where the printk statement
> > is, I tried to call ncr_complete() from there. That helped some, but the
> > middle scsi layer showed some timeout messages.
> > 
> > <>< Lance.


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]

Reply via email to