On 08/07/2007 11:36 AM, Tejun Heo wrote: > Alan Cox wrote: >> On Tue, 7 Aug 2007 14:42:50 +0900 >> Tejun Heo <[EMAIL PROTECTED]> wrote: >> >>> HDS724040KLSA80 reports that it supports HPA && LBA48 but craps itself >>> on READ_NATIVE_MAX_EXT. Implement BROKEN_HPA horkage and apply it to >>> the drive. If the horkage is set, all HPA operations are skipped. >> I'd rather know what is going on here. A drive can legitimately >> support LBA48 and HPA and refuse READ_NATIVE_MAX_EXT. > > READ_NATIVE_MAX_EXT is mandatory if HPA && LBA48, no? > >> In addition just >> about every OS I know queries the HPA which means that something other >> than HPA support being broken is probably at the root. We thus want to >> find the real fix. >> >> What do the actual traces look like ? >> >> Does it crap out of it gets READ_NATIVE_MAX ? > > Haven't tried that but the problem is that the drive times out > READ_NATIVE_MAX_EXT so it doesn't really matter whether the drive > succeeds READ_NATIVE_MAX or not. For more detail, please read the > following thread. > > http://thread.gmane.org/gmane.linux.ide/21322 >
There's also this Fedora bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251047#c2 ...where after an error on the slave device the master starts throwing HPA errors after the port is reset. Don't know if it's related or not... - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
