Hi,

J.A. Magallón wrote:
quoted text
> It reproduces also with 2.6.23.13.
> Finally I think the problematic disk is sdc:

Okay, then, it's less likely a regression and more likely a newly
developed hardware problem.

quoted text
> ICH5 PATA -> sda
> ICH5 SATA0 -> sdb
> ICH5 SATA1 -> sdc
> Promise SATA -> sdd
> 
> The problem is that even I have commented out the entry for sdc in fstab,
> the system is still giving me errors. An my guess is that errors in sdc makes
> the ICH5 sata controller go nuts, and then I get errors also in sdb.
> Just a couple questions...

I've never seen ICHs or any other SATA controllers act that way.

quoted text
> - Can I say to ata_piix something like 'please, detect first SATA ports before
>   ATA', so my system disk (sdb) becomes sda ?

You do that using LABEL, UUID or device ID.  Just run 'ls -l
/dev/disk/by-*/' and see the result.

quoted text
> - Can I say 'plz, ignore port 1', so it does not try to detect/start/spin sdc ?
>   So I ban be sure it is the one to blame, before start to remove hardware...

Unfortunately not but you can boot into single mode where there's
nothing trying to access the disk without your explicit command and
verify access to each hard disk.

Hmm... You are seeing timeouts from multiple harddisks.  The first thing
I would try is to reseat the cables and connect the SATA hard drives to
a separate power supply and see whether that changes anything.

-- 
tejun
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/