Re: SATA question
On Sun, Feb 03, 2008 at 01:25:07AM -0800, Ted Mittelstaedt wrote: > > Looks like it isn't detecting it as a generic controller. > > But I think this is the problem. Note that the system is > applying ata2 and ata3 to atapci0, and ata0 and ata1 to > atapci1. This is backwards, I've not seen this before in > the ata driver. Normally, ata0 and ata1 are applied to the > first controller - atapci0 - and ata2 and ata3 are applied > to the second controller - atapci1 - and so on. I have seen that before on one of my computers: atapci0: port 0xd000-0xd007,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc00f,0xb800-0xb8ff irq 20 at device 15.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 It looks like ata0 and ata1 are assigned to whichever interface looks like the "standard" ATA interface, regardless of in what order various ATA controllers are detected. > > Søren Schmidt put the support in for this chipset to the > ata driver. I'd file a PR and put it down to a driver bug. > > Ted > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > > Sent: Friday, February 01, 2008 7:06 AM > > To: 'Ted Mittelstaedt'; freebsd-questions@freebsd.org > > Subject: RE: SATA question > > > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > > > Sent: Tuesday, January 29, 2008 6:59 AM > > > To: freebsd-questions@freebsd.org > > > Subject: SATA question > > > > > > > > > Well, > > > maybe I spoke to soon. While looking at dmesg in prep for doing > > > a custom kernel for my new server, I noticed an oddity. > > > > > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > > > ad4 - > > > > > > Is this telling me the system recognized my > > > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > > > a UDMA33 ? > > > > > > > >>No doubt, a pciconf followed by insertion of the ID into the > > >>ata detection routines would help - assuming your sata chipset > > >>is supported. > > > > >>You don't have the entire dmesg here but it looks like it's > > >>using the generic driver. > > > > >>Ted > > > > > > atapci0: port > > 0xecb0-0xecb7,0xeca0-0xeca > > 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem > > 0xefdfe000-0xefdf irq 6 > > at d > > evice 14.0 on pci3 > > ata2: on atapci0 > > ata3: on atapci0 > > > > atapci1: port > > 0x1f0-0x1f7,0x3f6,0x170-0x > > 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 > > ata0: on atapci1 > > ata1: on atapci1 > > > > acd0: CDRW at ata0-master UDMA33 > > ad4: DMA limited to UDMA33, device found non-ATA66 cable > > ad4: 152587MB at ata2-master UDMA33 > > ad6: DMA limited to UDMA33, device found non-ATA66 cable > > ad6: 152587MB at ata3-master UDMA33 > > > > This is the copied relevant portions of demsg's output. I have only used > > pciconf to > > list devices, so am basically unfamilar with it. > > > > So, how do I get the system to recognize the drives as SATA ? > > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA question
Looks like it isn't detecting it as a generic controller. But I think this is the problem. Note that the system is applying ata2 and ata3 to atapci0, and ata0 and ata1 to atapci1. This is backwards, I've not seen this before in the ata driver. Normally, ata0 and ata1 are applied to the first controller - atapci0 - and ata2 and ata3 are applied to the second controller - atapci1 - and so on. Søren Schmidt put the support in for this chipset to the ata driver. I'd file a PR and put it down to a driver bug. Ted > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > Sent: Friday, February 01, 2008 7:06 AM > To: 'Ted Mittelstaedt'; freebsd-questions@freebsd.org > Subject: RE: SATA question > > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > > Sent: Tuesday, January 29, 2008 6:59 AM > > To: freebsd-questions@freebsd.org > > Subject: SATA question > > > > > > Well, > > maybe I spoke to soon. While looking at dmesg in prep for doing > > a custom kernel for my new server, I noticed an oddity. > > > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > > ad4 - > > > > Is this telling me the system recognized my > > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > > a UDMA33 ? > > > > >>No doubt, a pciconf followed by insertion of the ID into the > >>ata detection routines would help - assuming your sata chipset > >>is supported. > > >>You don't have the entire dmesg here but it looks like it's > >>using the generic driver. > > >>Ted > > > atapci0: port > 0xecb0-0xecb7,0xeca0-0xeca > 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem > 0xefdfe000-0xefdf irq 6 > at d > evice 14.0 on pci3 > ata2: on atapci0 > ata3: on atapci0 > > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x > 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 > ata0: on atapci1 > ata1: on atapci1 > > acd0: CDRW at ata0-master UDMA33 > ad4: DMA limited to UDMA33, device found non-ATA66 cable > ad4: 152587MB at ata2-master UDMA33 > ad6: DMA limited to UDMA33, device found non-ATA66 cable > ad6: 152587MB at ata3-master UDMA33 > > This is the copied relevant portions of demsg's output. I have only used > pciconf to > list devices, so am basically unfamilar with it. > > So, how do I get the system to recognize the drives as SATA ? > > thanks, > Darryl > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA question
Darryl Hoar wrote: Well, maybe I spoke to soon. While looking at dmesg in prep for doing a custom kernel for my new server, I noticed an oddity. ad4 - DMA limited to UDMA33, device found non-ata66 cable. ad4 - Is this telling me the system recognized my 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as a UDMA33 ? atapci0: port 0xecb0-0xecb7,0xeca0-0xeca 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at d evice 14.0 on pci3 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: on atapci1 ata1: on atapci1 acd0: CDRW at ata0-master UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 152587MB at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 152587MB at ata3-master UDMA33 This is the copied relevant portions of demsg's output. I have only used pciconf to list devices, so am basically unfamilar with it. So, how do I get the system to recognize the drives as SATA ? I think you are placing a lot of faith in an error message and that your drives *may* be being recognised as SATA drives with just something spurious (in the driver) causing this message to appear. It looks like the same chipset is providing both IDE/UDMA and SATA, so maybe the driver is trying them as IDE first, producing the error messages, then finding they are SATA after all. Just a guess Have you tried any basic disk benchmarks? Even a diskinfo -t should show you the kind of throughput your are getting, or something like dd bs=64k if=/dev/zero of=/some/file/on/the/disk count=1 That takes ~10 secs on my machine. If your performance is better than UDMA33 then you could just ignore the message or file an informational PR (if there isn't one already). Don't forget to be careful about bits/sec versus bytes/sec UDMA 33 is 33MB/s which is 33*1000*1000 bytes but 8 times as many bits, which some applications report. Having failed to get a definitive answer here you could also try the driver maintainer whom I believe to be [EMAIL PROTECTED] Confirm that from the manpage and don't forget to mention the version of FreeBSD you have (6.3?) See also this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg01706.html hth, --Alex On a random SATA150 disk I get ~60017191 bytes/sec for a dd, which ~= 6 kbytes/sec from diskinfo and ~= 60MB/s or twice UDMA33. I believe that to be about par for a modern SATA disk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA question
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > Sent: Tuesday, January 29, 2008 6:59 AM > To: freebsd-questions@freebsd.org > Subject: SATA question > > > Well, > maybe I spoke to soon. While looking at dmesg in prep for doing > a custom kernel for my new server, I noticed an oddity. > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > ad4 - > > Is this telling me the system recognized my > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > a UDMA33 ? > >>No doubt, a pciconf followed by insertion of the ID into the >>ata detection routines would help - assuming your sata chipset >>is supported. >>You don't have the entire dmesg here but it looks like it's >>using the generic driver. >>Ted atapci0: port 0xecb0-0xecb7,0xeca0-0xeca 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at d evice 14.0 on pci3 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: on atapci1 ata1: on atapci1 acd0: CDRW at ata0-master UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 152587MB at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 152587MB at ata3-master UDMA33 This is the copied relevant portions of demsg's output. I have only used pciconf to list devices, so am basically unfamilar with it. So, how do I get the system to recognize the drives as SATA ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA question
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar > Sent: Tuesday, January 29, 2008 6:59 AM > To: freebsd-questions@freebsd.org > Subject: SATA question > > > Well, > maybe I spoke to soon. While looking at dmesg in prep for doing > a custom kernel for my new server, I noticed an oddity. > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > ad4 - > > Is this telling me the system recognized my > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > a UDMA33 ? > No doubt, a pciconf followed by insertion of the ID into the ata detection routines would help - assuming your sata chipset is supported. You don't have the entire dmesg here but it looks like it's using the generic driver. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SATA question
-Original Message- From: Wojciech Puchar [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 29, 2008 9:13 AM To: Darryl Hoar Cc: freebsd-questions@freebsd.org Subject: Re: SATA question > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > ad4 - > > Is this telling me the system recognized my > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > a UDMA33 ? >> at least with computer i use with SATA i had to set in it's crappy BIOS >> that SATA channels to "RAID" (while not defining any RAID actually) - and >> it helped, the disks are detected as SATA this system does not have "RAID". -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.15/1249 - Release Date: 1/29/2008 9:51 AM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA question
ad4 - DMA limited to UDMA33, device found non-ata66 cable. ad4 - Is this telling me the system recognized my 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as a UDMA33 ? at least with computer i use with SATA i had to set in it's crappy BIOS that SATA channels to "RAID" (while not defining any RAID actually) - and it helped, the disks are detected as SATA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
