From owner-freebsd-alpha Wed Jun 28 17:26:27 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (peter1.corp.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id B06C137BA69 for ; Wed, 28 Jun 2000 17:26:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BDAA41CDF for ; Wed, 28 Jun 2000 17:26:16 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Subject: fdc driver problem on the Alpha (PC164SX) - anyone else? Date: Wed, 28 Jun 2000 17:26:16 -0700 From: Peter Wemm Message-Id: <20000629002616.BDAA41CDF@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm getting a hang during boot now under -current: ... vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 mcclock0: at port 0x70-0x71 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 Normally it looks like this: ... mcclock0: at port 0x70-0x71 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at ISA irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 First, is anybody else seeing this? Anybody else using fdc under the latest -current? The fdc code hasn't changed since the last time I built and ran a kernel. I don't see why the config(8) changes should affect just this driver. The thing that I am most suspicious of right now is this commit to the alpha isa_dma.c: revision 1.4 date: 2000/06/19 18:41:27; author: gallatin; state: Exp; lines: +29 -4 Support bounce buffers for ISA DMA on the alpha. This is required for the irongate chipset (used in the UP1000) which does not support scatter/gather DMA. We'll still use scatter gather if the core logic chipset supports it. It has one line in there that is not described in the commit message: @@ -105,6 +106,7 @@ * Reset the DMA hardware. */ outb(DMA1_RESET, 0); + outb((IO_DMA1 + 1*14), 0); outb(DMA2_RESET, 0); isa_dmacascade(4); I'm wondering if this could be related somehow. The driver seems to be hanging in a way that might be consistant with a dma initialization problem. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message