ATAng ate my hampster...

From: Ashley Penney <>
Date: Sun, 14 Sep 2003 04:51:46 +0100

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
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.'"
Received on Sat Sep 13 2003 - 18:53:13 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:22 UTC