Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Jun 2003 21:46:55 -0700 (PDT)
From:      "Justin T. Gibbs" <gibbs@FreeBSD.org>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/sys/dev/aic7xxx aic79xx.c
Message-ID:  <200306280446.h5S4ktPr058769@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
gibbs       2003/06/27 21:46:55 PDT

  FreeBSD src repository

  Modified files:
    sys/dev/aic7xxx      aic79xx.c 
  Log:
  Fix a race condition in the flushing of commands that
  have completed across the bus but not to the host before
  processing of an exception condition (busfree, bus reset,
  etc.).  When flushing the controller of completed commands,
  we also look for packetized commands that have completed
  with good status and are stored in the "good status fifo".
  The hardware will post to the good status fifo even if
  data for that command is still active in a FIFO.  In
  one particular failure case, a command outstanding on the
  bus reconnected, transferred data into a FIFO, and provided
  good status while the host driver was processing an expected
  busfree event (PPR message negotiation).  This resulted in
  an entry in the good status fifo that we completed, but
  since the sequencer was paused, the data in the data FIFO
  for this command had never been transferred to the host.
  Once the busfree processing was complete, the sequencer
  was unpaused, and the data completed its transfer to the
  host.  In some instances, the client for the data was notified
  of the completion and attempted to view the data before
  it arrived.  This case only occurred during FreeBSD's
  multi-target probe of the SCSI bus while some devices are
  negotiating to go packetized and some devices are already
  running in packetized.
  
  The fix is to run and FIFOs active with a context in the
  good status fifo to completion before completing the command
  to the SCSI layer.  This requies duplicating the FIFO rundown
  operations in the host driver that would usually be handled
  by the firmware, but there is no other alternative.
  
  Don't blindly shutdown the SCB dma engine when restarting
  the sequencer.  We may be killing an operation that is
  not supposed to be cancelled.  The cases where we need to
  shutdown these dma engines are already handled elsewhere in
  the driver.
  
  Fix a few more ahd_in?() -> ahd_in?_scbram() instances.
  
  Revision  Changes    Path
  1.24      +379 -49   src/sys/dev/aic7xxx/aic79xx.c



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306280446.h5S4ktPr058769>