From owner-freebsd-current@FreeBSD.ORG Sun Oct 5 17:07:02 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8017A16A4B3 for ; Sun, 5 Oct 2003 17:07:02 -0700 (PDT) Received: from secundus.notanet.net (secundus.notanet.net [66.92.213.25]) by mx1.FreeBSD.org (Postfix) with SMTP id 7119643FF5 for ; Sun, 5 Oct 2003 17:07:01 -0700 (PDT) (envelope-from fbsdc@notanet.net) Received: (qmail 8691 invoked by uid 1001); 6 Oct 2003 00:07:00 -0000 Date: Sun, 5 Oct 2003 20:07:00 -0400 From: Barry Miller To: current@freebsd.org Message-ID: <20031006000700.GA8588@secundus.notanet.net> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: ATAng primary-secondary drive oddness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2003 00:07:02 -0000 None of the previous posts on this seem to describe exactly what I'm seeing: 5.1-REL always detects the secondary drive. 5.1-CUR never detects the secondary. 5.1-CUR + ata-lowlevel 1.11 detects it the FIRST time it's booted immediately after 5.1-REL. Always. On subsequent boots, no luck. A = 1st CUR + ata-lowlevel 1.11 after running REL. B = 2nd and following boots of same. B ata0-slave: stat=0x10 err=0x01 lsb=0x00 msb=0x00 A ata0-slave: stat=0x50 err=0x01 lsb=0x00 msb=0x00 A ata0: reset tp2 mask=03 stat0=50 stat1=50 devices=0x3 B ata0: reset tp2 mask=03 stat0=50 stat1=10 devices=0x1 A ata0-slave: pio=0x0c wdma=0x22 udma=0x45 cable=80pin A ad1: setting UDMA100 on Intel ICH4 chip A ad1: ATA-6 disk at ata0-slave I'll provide more info or try something different if it might help. -barry