Description of problem:

Was asked to move bug from #163419 to here and under anaconda. I still blame the
kernel ;)

"There's a nasty FC3 <-> FC4 regression too related to host protected areas.

IBM thinkpads have a few GB recovery area in the host protected area that FC3
happily ignored. FC4 overrides the BIOS/harddisk and thinks it can use the
entire disk. Which means anaconda makes partitions that fill the entire disk.
Everything is fine until you come back from suspend -> that part of the disk is
unaccessible since the bios has locked it -> your system gets very confused.

So there's two scenarios, some people really want to use that space and others
absolutely require that the kernel doesn't touch it. Lovely :)"

In the FC3 install kernel, that area just wasn't seen by anaconda (no
CONFIG_IDE_DISK_STROKE?). In the FC4 install kernel, during the boot there is
something like 

current capacity is 66055248 sectors (33820 MB)
native  capacity is 78165360 sectors (40020 MB)
hda: Host Protected Area disabled.

So anaconda is happy using the entire disk. And everything is happy, except
the XP recovery "partition" (not a real partition :) ) gets nuked. Not a huge
deal, I suppose. But the behaviour when coming out of suspend is a lot nastier,
then parts of your harddrive just vanish.