Date: Thu, 20 Nov 2003 04:20:46 +0100 From: Thomas Moestl <t.moestl@tu-bs.de> To: Kris Kennaway <kris@obsecurity.org>, sos@freebsd.org, sparc64@freebsd.org Subject: Re: ultra5/cmd646 hang Message-ID: <20031120032045.GB759@timesink.dyndns.org> In-Reply-To: <20031120031150.GA759@timesink.dyndns.org> References: <20031114105853.A92204@carver.gumbysoft.com> <20031114134001.D92204@carver.gumbysoft.com> <20031117130205.R22102@carver.gumbysoft.com> <20031117225453.GA35569@xor.obsecurity.org> <20031118011019.GA37617@xor.obsecurity.org> <20031120031150.GA759@timesink.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2003/11/20 at 04:11:50 +0100, Thomas Moestl wrote: > I think I've found the reason for this; the attached patch works around it. > > The issue is that the chip does not set ATA_BMSTAT_INTERRUPT, even though > it is DMA-capable. My hackaround is to add an interrupt handler for the > CMD646 that does only check this bit if a DMA transfer is in progress, I should add that this was observed on a rev. 3 CMD646 (aka CMD646U). - Thomas -- Thomas Moestl <t.moestl@tu-bs.de> http://www.tu-bs.de/~y0015675/ <tmm@FreeBSD.org> http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031120032045.GB759>