From owner-freebsd-alpha@FreeBSD.ORG Wed Dec 22 22:03:49 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5218F16A4CE for ; Wed, 22 Dec 2004 22:03:49 +0000 (GMT) Received: from bsd.ee (bsd.ee [194.126.101.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 4675643D39 for ; Wed, 22 Dec 2004 22:03:48 +0000 (GMT) (envelope-from hadara@bsd.ee) Received: (qmail 32331 invoked by uid 1021); 22 Dec 2004 22:04:33 -0000 Received: from hadara@bsd.ee by daemon.bsd.ee by uid 82 with qmail-scanner-1.20 (spamassassin: 2.55. Clear:RC:1(62.65.205.81):. Processed in 0.052373 secs); 22 Dec 2004 22:04:33 -0000 Received: from unknown (HELO ?62.65.205.81?) (62.65.205.81) by bsd.ee with SMTP; 22 Dec 2004 22:04:32 -0000 From: Sven Petai Organization: NPO BSD Estonia To: Wilko Bulte Date: Thu, 23 Dec 2004 00:03:01 +0200 User-Agent: KMail/1.6.2 References: <200412221730.iBMHUJC6097807@freefall.freebsd.org> <20041222184436.GA50553@freebie.xs4all.nl> In-Reply-To: <20041222184436.GA50553@freebie.xs4all.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412230003.02588.hadara@bsd.ee> cc: freebsd-alpha@freebsd.org Subject: Re: alpha/75317: ATA DMA broken on PCalpha X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2004 22:03:49 -0000 On Wednesday 22 December 2004 20:44, Wilko Bulte wrote: > > anyway this still doesn't make things work correctly for me, > > because the real problem seems to be the Pyxis > > page crossing bug. Basically it comes down to corrupting > > DMA transfers larger than 8k. It didn't cause problems before, > > since we never did larger than PAGE_SIZE transfers before > > the ATA dma change mentioned in the original report. > > There's a detection code for the buggy chip @ > > src/sys/alpha/pci/cia.c > > but it's little too naive, since it assumes only DEC_ST550 can > > have it, in reality it seems to be used in some very early > > revisions of 164LX(SX too?). But there doesn't seem to be a > > Yes, the SX too: > what I actually meant was that sure enough ALL the SX and LX boxes have PYXIS chips but _maybe_ some of the early ones don't have the fix for 8k problem, since the fix consists of adding some off-chip logic, it's not detectable in the version of Pyxis chip itself. This seems to be only reasonable explanation to why everything works fine when I hack PAGE_SIZE to be the max segment size for ata dma and causes machine checks, unknown signals and other anomalies for anything larger. [snip] > cia0: Pyxis, pass 1 <<<<<---- pass 1 > cia0: extended capabilities: 1 > > Interestingly enough the pass 1 thing is not fully reliable as a trouble > indicator: yes, since the fix is implemented off-chip... [snip] > so without the warning. In Miatas using a 32bit slot instead of a 64bit > PCI slot avoided the problem. but that doesn't help you in the case of onboard ata... actually it would be nice to know if the early Miatas that are detected as having faulty Pyxis, have the same issue when using onboard ata in the CURRENT, they certainly should... > > My 164SX does not report any warning. yeah since the code currently only checks if it's early version of Miata, it doesn't try to trigger the bug to see if it exists or do anything else fancy like that...