BUT I didn't experience it with Debian Etch (Kernel 2.6.18), maybe because of fewer probing retries or shorter timeouts.
I haven't found a workaround. The kernel option ata2=noprobe doesn't work (as several other people pointed out with similar problems and different chips)
I can confirm this bug on the same machine.
The problem has been reported two years ago here: https:/ /lists. linux-foundatio n.org/pipermail /bugme- new/2006- October/ 015008. html
BUT I didn't experience it with Debian Etch (Kernel 2.6.18), maybe because of fewer probing retries or shorter timeouts.
I haven't found a workaround. The kernel option ata2=noprobe doesn't work (as several other people pointed out with similar problems and different chips)