From owner-freebsd-current@FreeBSD.ORG  Sat Sep 13 20:53:13 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 EB9ED16A4BF; Sat, 13 Sep 2003 20:53:13 -0700 (PDT)
Received: from lexi.unloved.org (lexi.unloved.org [212.74.113.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D949643FA3; Sat, 13 Sep 2003 20:53:12 -0700 (PDT)
	(envelope-from ashp@unloved.org)
Received: from localhost (unknown [127.0.0.1])
	by lexi.unloved.org (Postfix) with ESMTP
	id 9935E1709E; Sun, 14 Sep 2003 03:53:11 +0000 (GMT)
Received: from lexi.unloved.org ([127.0.0.1])
 by localhost (lexi.unloved.org [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 80586-07; Sun, 14 Sep 2003 04:51:46 +0100 (BST)
Received: by lexi.unloved.org (Postfix, from userid 1001)
	id 52041170A9; Sun, 14 Sep 2003 04:51:46 +0100 (BST)
Date: Sun, 14 Sep 2003 04:51:46 +0100
From: Ashley Penney <ashp@unloved.org>
To: freebsd-current@freebsd.org
Message-ID: <20030914035146.GB71243@lexi.unloved.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Subject: ATAng ate my hampster...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Sep 2003 03:53:14 -0000

Hiya,

I recently upgraded my -current box, only to have my Serial ATA device move
from ar0 to ad6, making things cry.

Here's the relevant information currently in dmesg, my main concern is not
the name change, but more the reporting of the disk as UDMA133, which it
clearly isn't!  Soren, if I can give you any more useful information, please
let me know.

atapci0: <Promise PDC20376 SATA150 controller> port 0xcc00-0xcc7f,0xc800-0xc80f,
0xc400-0xc43f mem 0xee000000-0xee01ffff,0xee020000-0xee020fff irq 11 at device 1
1.0 on pci1
atapci0: [MPSAFE]
ata2: at 0xee020000 on atapci0
ata2: [MPSAFE]
ata3: at 0xee020000 on atapci0
ata3: [MPSAFE]
ata4: at 0xee020000 on atapci0
ata4: [MPSAFE]
atapci1: <nVidia nForce2 UDMA133 controller> port 0xf000-0xf00f at device 9.0 on
 pci0
ata0: at 0x1f0 irq 14 on atapci1
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci1
ata1: [MPSAFE]
GEOM: create disk ad6 dp=0xc625b570
ad6: 76319MB <ST380023AS> [155061/16/63] at ata3-master UDMA133

-- 
[+CrtxReavr] ashp, some supposedly skilled unix developer where I work hosed a
box (Solaris for Intel) by doing a 'chmod -R 447 /etc'.
[+CrtxReavr]: When I confronted him about he he claimed that "Intel
architecture was 'little-endian.'"