| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4DB70E92.2020209@teksavvy.com> Date: Tue, 26 Apr 2011 14:27:30 -0400 From: Mark Lord <kernel@...savvy.com> To: Tejun Heo <htejun@...il.com> CC: Bruce Stenning <b.stenning@...igovision.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org> Subject: Re: sata_mv port lockup on hotplug (kernel 2.6.38.2) On 11-04-25 07:30 AM, Tejun Heo wrote: > On Mon, Apr 25, 2011 at 12:07:04PM +0100, Bruce Stenning wrote: >> Tejun, what does it mean to limit a sata link to UDMA/100? I thought that this >> was only for ata devices, and sata devices have the choice of 1.5Gbps, 3Gbps, >> or 6 Gbps. Is that a false assumption? Is it related to early sata devices that >> were still somewhat based on parallel ata designs? > > Yeap, devices behind SATA-PATA bridge were still affected by the > transfer mode so libata tries to slow them down too along with link > speed when limiting speed due to errors. Shouldn't affect native SATA > devices. Yeah, what he said. :) First generation SATA devices were merely PATA transports with a SATA-to-PATA converter chip onboard. Some of those require that we set the transfer modes. Ditto for various more modern setups, where CF-cards, PATA drives, and other weirdos are connected through a discrete SATA bridge device. Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists