http://bugzilla.kernel.org/show_bug.cgi?id=14583 --- Comment #26 from Andrew Simpson <andrewnz.simpson@xxxxxxxxx> 2009-12-09 06:29:53 --- Thanks. I'm not a kernel developer, but I get the general gist of that. However, there are several reasons that I don't think this is necessarily a bug in the SSD device. Firstly, it affects a range of SSD devices from different manufacturers and different production dates. I guess they could share common firmware (and hence the same bug), but that has to be rather remote possibility. Secondly, the SSD devices are performing without issue on 2.6.28 (and one report of 2.6.30), but the same machines fail on 2.6.31/2.6.32. This suggests something changed in the kernel that affects the SSD between 2.6.30 and 2.6.31. Thirdly, these machines were often sold with factory installed Linux. O.K., so it was an earlier kernel, but the SSD has clearly worked enough to met the manufacturer's satisfaction. Fourthly, (and this where I show I'm not a developer), we are only seeing the end result of the transaction (the HSM violation). Could there have been several erroneous - but not out-of-band - command/response exchanges leading up to the HSM violation? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
