kern/136438: ata - discrepancy between 8 and earlier rel. (?)
barbara.xxx1975 at libero.it
Tue Jul 7 20:00:13 UTC 2009
>Synopsis: ata - discrepancy between 8 and earlier rel. (?)
>Arrival-Date: Tue Jul 07 20:00:12 UTC 2009
>Release: 7-STABLE, 8-STABLE
FreeBSD satanasso.local.net 7.2-STABLE FreeBSD 7.2-STABLE #1: Wed Jul 1 20:39:38 CEST 2009 root at satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO i386
FreeBSD satanasso.local.net 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Jul 5 14:10:54 CEST 2009 root at satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO i386
On 8, my dmesg contains:
atapci2: <VIA 8237A UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
ata0: <ATA channel 0> on atapci2
ad0: DMA limited to UDMA33, device found non-ATA66 cable
ad0: 152627MB <MAXTOR STM3160212A 3.AAJ> at ata0-master UDMA33
ad1: 117246MB <Maxtor 6Y120L0 YAR41BW0> at ata0-slave UDMA133
# atacontrol info ata0
Master: ad0 <MAXTOR STM3160212A/3.AAJ> ATA/ATAPI revision 7
Slave: ad1 <Maxtor 6Y120L0/YAR41BW0> ATA/ATAPI revision 7
So, if ad0 and ad1 are both attached with the same cable, why ad0 should be limited while ad1 is not?
On 7, I have:
ad0: 152627MB <MAXTOR STM3160212A 3.AAJ> at ata0-master UDMA100
which seems correct.
as I always had since I had this mainboard (with 6.2).
I've also replaced the cable with a brand new one, with the same results.
So, what's wrong?
I wonder if 8 is exposing a HW problem that I should be worried about or simply something wrong was introduced.
More information about the freebsd-bugs