Hi Jeff > A complete dmesg is definitely useful. It's at the end of my previous post. > Posting one from the failing kernel would be preferred, though. Any ideas as to how I can capture it? Since the SATA disc interfaces stop working long before they are mounted none of the early boot messages make it to disc. All the interesting bits are therefore scrolled into the bit bucket. A serial console might be doable (is there documentation about how to set one up?) but that would take some time to arrange - I'm only physically at the machine in question sporadically and I'd have to rustle up another PC ready for my next visit. It could be done, but might take some time. > That will show us libata boot messages as well as the failures you are > seeing, in full detail. For sure. In terms of the detailed failure messages what I posted previously is about all that was shown. > Also, please try the latest 2.6.34-rc kernel, as that has several fixes > for both pata_via and sata_via which did not make 2.6.33. I'll see if I can squeeze this in this afternoon and report back. Regards jonathan -- 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
