Mikael Pettersson writes: > Mike Cui writes: > > If you want the full kernel boot log I can get it to you in a couple > > of days. But here is what I remember from the kernel logs. It probes > > each of the 4 ports, and it always thinks that the first port is "link > > down". The drives I have plugged into it are samsung HD753LJ > > 1. Have you tried with different disks on port 0? Preferably also > with different models or from different manufacturers. > 2. Does it matter if all ports are populated? Is there any difference > if only port 0 is populated as opposed to all 4 being populated? > > Full boot logs from the last working kernel and first non-working one would > be useful. And please make them www.kernel.org kernels, not Ubuntu ones. I loaded my sata_promise test box with a SATA300TX4 and one SATA disk on each of the four ports. 2.6.29-rc6 and 2.6.28 booted and worked with no issues whatsoever. 2.6.27 and 2.6.26 experienced slight boot delays as the disk on the first port (a Samsung HD501LJ) got a failed COMRESET which EH had to recover from (and it did). The sata_promise COMRESET problem was fixed in 2.6.28, and the fix was backported to the 2.6.27 stable series in 2.6.27.5 (current is 2.6.27.19). I suggest that you skip 2.6.26 and update to 2.6.27.19 or newer. /Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
