Date: Wed, 06 Aug 2003 15:03:32 -0600 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Dave Dolson <ddolson@sandvine.com>, "'freebsd-scsi@freebsd.org'" <freebsd-scsi@freebsd.org> Subject: Re: Swapping deadlock due to aic/scsi errors? Message-ID: <1787590000.1060203812@aslan.scsiguy.com> In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C8533701919089@mail.sandvine.com> References: <FE045D4D9F7AED4CBFF1B3B813C8533701919089@mail.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> We have a reproducible bug characterized by the system > becoming unresponsive (but db may be entered). > System is based on FreeBSD 4.7 (i386) > Using the aic79xx scsi driver. If you are using the stock aic79xx driver found in 4.7, I would start by pulling in the latest 4.X aic79xx driver into your system. > I would like to add some debugging to detect the lost command > and possibly retry it. Can someone suggest where the lost > command is supposed to be detected, and where the retry is > supposed to occur. The "lost command" is supposed to be detected by the timeout handler in the ahd driver. The timeout handler just forces a bus reset which should cause the command to be returned to the SCSI layer and then retried. It's not clear to me why this might not be happening, but the ahd driver was relatively green in 4.7 and you may just be tripping over a known (and later corrected) bug manifesting itself in an unusual way. -- Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1787590000.1060203812>