Matthew Garrett wrote:
On boot, Linux will attempt to disable the host protected area on a
disk. After a suspend/resume cycle, the BIOS may reenable it (seen on a
Thinkpad T40 and R40). As a result, the kernel is now unable to access
the HPA.
Is there any issue with just adding a call to idedisk_check_hpa() in the
IDE resume code?
This has come up several times now. One thing I'm curious about is
why we are disabling HPA on boot without consent from the user. AFAIK,
HPA is mostly used to implement hidden recovery/suspend storage areas
and disabling automatically on boot increases the likeliness of
destroying them. What do we gain by disabling HPA on boot? Are there
some dumb machines which unnecessarily sets HPA and reduces the capacity
of drives excessively? Even in such cases, wouldn't it be better to do
idedisk_check_hpa() only when kernel parameter explicitly says so?
--
tejun
-
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
