From owner-freebsd-current Fri Dec 10 22:59:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id B603C14E2B for ; Fri, 10 Dec 1999 22:59:07 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id OAA20899 for freebsd-current@freebsd.org; Sat, 11 Dec 1999 14:21:26 +0800 (WST) From: Michael Kennett Message-Id: <199912110621.OAA20899@laurasia.com.au> Subject: Re: HEADSUP: wd driver will be retired! In-Reply-To: <199912110553.VAA00494@mass.cdrom.com> from Mike Smith at "Dec 10, 99 09:53:30 pm" To: freebsd-current@freebsd.org Date: Sat, 11 Dec 1999 14:21:25 +0800 (WST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, here are my experiences with the new ATA driver. Firstly, I've been following the discussion on -current, and decided that this weekend I'd convert over to the new ata drivers - but with a bit of trepidation, given the discussion that's been going on. Anyway, I've rebuild my kernel, rebooted once, rebooted again, and the system seems to be holding together. The sky has not fallen on my head... Firstly, my old set up had: controller wdc0 at isa? port IO_WD1 irq14 controller wdc1 at isa? port IO_WD2 irq15 device wd0 at wdc0 drive 0 device wd2 at wdc2 drive 0 Note that wd1 is not present. This caused a mild hickup when rebooting the new kernel, since the new ata controller assigned the labels ad0 and ad1 to the drives. It was not possible to boot into multiuser mode without changing the /etc/fstab file to rename the /dev/wd2* entries to /dev/ad1*. That was easy to fix, however for a newbie it might cause problems. I mention it now, since the upgrade from 3.x might need special handling of this case (?). Finally, I've noticed the following messages: Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying Dec 11 13:54:50 rabbit last message repeated 2 times Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 falling back to PIO mode It strikes me that these aren't serious - just that my hardware is rather crappy (and doesn't support the faster UDMA modes) :-) In case the developers are interested, here are selected portions of dmesg of the pre/post changes... Dec 11 13:41:29 rabbit /kernel.991204: FreeBSD 4.0-CURRENT #0: Sat Dec 4 19:07:15 WST 1999 Dec 11 13:41:29 rabbit /kernel.991204: pcib0: on motherboard Dec 11 13:41:29 rabbit /kernel.991204: pci0: on pcib0 Dec 11 13:41:29 rabbit /kernel.991204: isab0: at device 7.0 on pci0 Dec 11 13:41:29 rabbit /kernel.991204: isa0: on isab0 Dec 11 13:41:29 rabbit /kernel.991204: chip1: at device 7.1 on pci0 Dec 11 13:41:29 rabbit /kernel.991204: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 Dec 11 13:41:29 rabbit /kernel.991204: wdc0: unit 0 (wd0): Dec 11 13:41:29 rabbit /kernel.991204: wd0: 696MB (1427328 sectors), 1416 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:41:29 rabbit /kernel.991204: wdc1 at port 0x170-0x177 irq 15 on isa0 Dec 11 13:41:29 rabbit /kernel.991204: wdc1: unit 0 (wd2): Dec 11 13:41:29 rabbit /kernel.991204: wd2: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: FreeBSD 4.0-CURRENT #0: Sat Dec 11 13:34:57 WST 1999 Dec 11 13:54:50 rabbit /kernel: pcib0: on motherboard Dec 11 13:54:50 rabbit /kernel: pci0: on pcib0 Dec 11 13:54:50 rabbit /kernel: isab0: at device 7.0 on pci0 Dec 11 13:54:50 rabbit /kernel: isa0: on isab0 Dec 11 13:54:50 rabbit /kernel: ata-pci0: at device 7.1 on pci0 Dec 11 13:54:50 rabbit /kernel: ata-pci0: Busmastering DMA supported Dec 11 13:54:50 rabbit /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Dec 11 13:54:50 rabbit /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Dec 11 13:54:50 rabbit /kernel: ata-isa0: already registered as ata0 Dec 11 13:54:50 rabbit /kernel: ata-isa1: already registered as ata1 Dec 11 13:54:50 rabbit /kernel: ad0: ATA-? disk at ata0 as master Dec 11 13:54:50 rabbit /kernel: ad0: 696MB (1427328 sectors), 1416 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: ad0: 16 secs/int, 1 depth queue, PIO Dec 11 13:54:50 rabbit /kernel: ad1: ATA-4 disk at ata1 as master Dec 11 13:54:50 rabbit /kernel: ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 13:54:50 rabbit /kernel: ad1: 16 secs/int, 1 depth queue, UDMA66 Dec 11 13:54:50 rabbit /kernel: Mounting root from ufs:/dev/ad0a Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 retrying Dec 11 13:54:50 rabbit last message repeated 2 times Dec 11 13:54:50 rabbit /kernel: ad1: UDMA CRC READ ERROR blk# 0 falling back to PIO mode To summarise, I've experienced no difficulty in changing to the new ATA drivers. I'm in the midst of rebuilding world, and so far there have been no errors in the process (and I don't expect any) Thank you to the Soren, and the developers of this new driver. Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message