| 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: <20090419201132.GB2891@ime.usp.br> Date: Sun, 19 Apr 2009 17:11:32 -0300 From: Rogério Brito <rbrito@....usp.br> To: Jeff Garzik <jeff@...zik.org> Cc: Michael Tokarev <mjt@....msk.ru>, Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org Subject: Re: Quick question about libata and hdparm Hi, Jeff. On Apr 19 2009, Jeff Garzik wrote: > Michael Tokarev wrote: >> Well, the kernel does a good job here in *almost* all cases. >> The problematic case is when a device has some bad/unreadable >> blocks/sectors. When such a place occurs on read, libata >> (or whatever it is) performs several retries, each time >> using "less aggressive" settings - like reducing UDMA and >> PIO mode till the lowest possible PIO/33. And the device >> stays in that mode until reboot, even if the problematic >> sector has been relocated. So it'd be nice to be able to >> reset the mode back in such cases. > > Do you have a log? I have a log here of libata reducing UDMA speed. I don't know if this is any hardware problem or not (I think not), but I do see libata complaining and reducing the speed of the drive. Would you like it? Thanks, -- Rogério Brito : rbrito@...ckenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8 http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org -- 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