I applied your patch to the 2.6.34 kernel, and on my very first reboot had a drive missing. What information do you want? Just /var/log/messages? I don't want to keep rebooting forever. Was this patch supposed to fix the problem, or just give you information to debug? Is the problem even known? Regards, Paul > Hello, > > On 07/12/2010 06:36 PM, Paul Check wrote: >>> Tejun & Co: >>> >>> I have finally upgraded to the 2.6.34 kernel, and I am still having >>> problems with some of my drives not coming up some of the time >>> (different >>> drives, at different times, never more than one). >>> >>> Here are some lines from /var/log/messages on the most recent boot >>> below. >>> Do you have any suggestions for this? I'm getting tired of having to >>> reconstitute my raid 30-50% of the time, and will try anything to see >>> if >>> it fixes. Note the "link up (unknown)" and "link down" lines. I don't >>> know >>> what should appear, but I have 4 hard drives and one optical drive >>> plugged >>> into 5 of the 6 SATA ports on the board. > ... >>> Jul 12 12:25:22 min kernel: [ 2.078489] ata2.01: SATA link up >>> <unknown> >>> (SStatus 300 SControl 123) > > Hmm, yeah, it seems like SCR access via SIDPR is more flaky than > covered by the previous commit. There's another thread where similar > problem is being debugged. Can you please do the following? I'm > attaching patch here too. > > http://thread.gmane.org/gmane.linux.kernel/1005983/focus=46749 > > Thanks. > > -- > tejun > -- 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
