Ok, well we didn't have to wait long. Once again one of my drives failed to appear. This time it was a different drive than the times before. I have attached the output from dmesg. Can you tell me from this output what the problem is? Regards, Paul > Hello, > > On 07/14/2010 07:58 PM, Paul Check wrote: >> 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? > > The kernel boot log should suffice. ie. dmesg output after boot. > >> 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? > > It should give more information but seems to actually make the other > reporter's problem go away. It looks like SIDPR SCR access can be > flaky depending on timing but I'm still trying to determine how to > work around it. > > 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 >
Attachment:
dmesg.out
Description: Binary data
