Comment 13 for bug 352197

> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version
> after 2.6.28-11. In all this cases, using the ahci module produces the

A mainline kernel farther away (2.6.30) would be of interest as it could show
whether this is an issue upstream.

> timeouts, but ata_piix works fine. If only i could tell the 2.6.28
> kernels to use ata_piix instead of ahci, i'd take the bug as solved
> through a workaround.

It looks a bit strange as your lspci looks like ahci and ata_piix are loaded
but only ata_piix shows up as being the driver. Reading the code for the ahci
driver they have a comment in there that in both modes ahci and ide the
controller reports the same ids. So they do a test to see whether to use ahci
mode or not. I'd like to check with the lspci command mentioned above and the
dmesg what this decision might be. Actually, do you have the ability to change
the controller mode in the BIOS or is that hidden?

> If you tell me how i can recover the complete dmesg log from the boot
> sequence, i'd be happy to provide one. actually, i'd love it if you

I would try whether it is possible to save a dmesg on a USB stick, if that is
possible. But thats probably prevented by the problems with the disk and the
system trying to log the login. Depending on whether you got a second computer,
netconsole might be an option.

> sure if its not hardware related, but i have tested with smart tools
> and in windows and the drive seems to behave.

Windows normally would not use the ahci mode by default. And as you say, you
have no problems when blacklisting the ahci module. The question would be
whether the ahci driver for some reason believes the controller is in ahci mode
while it isn't.