Created attachment 32712 [details] dmesg log I have a Verbatim ExpressCard SSD that uses the phison driver from staging. On recent kernels when loading the module I see a lot of errors and the driver is eventually unable to read the partition table off the device, rendering the device useless on those kernels. (log attached) I tested it with 2.6.35 and 2.6.36rc7, same behaviour. 2.6.32 works find. I haven't had the chance yet to test .33 and .34.
Can you run 'git bisect' to try to track down the patch that caused this problem? I can't seem to find my device to test this out myself, sorry.
Sure thing. Took a while, but according to my test the first bad commit is 1c5afdf7a629d2e77de8dd043b97a33dcd7e6dfa. Hope that helps :)
Wonderful, it does, can you test out the patch attached here to see if it solves the problem or not for the driver?
Created attachment 32912 [details] proposed patch due to libata api change
Which version is the patch for? It doesn't apply for me for either 2.6.36rc7 or 1c5afdf
On Sat, Oct 09, 2010 at 09:01:11AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > Which version is the patch for? It doesn't apply for me for either 2.6.36rc7 > or > 1c5afdf It should apply to 2.6.36-rc7. It's just changing one function call to another one, so if it somehow doesn't apply, can you do it by hand and test it?
ok, done, and it seems to work fine here. Thank you very much! :)
Wonderful, thanks for testing. Sorry about the patch, now I see what I did wrong, that was my fault. I've commited this to the staging-next tree and it will go into the .37 merge and backported to the proper kernels (.35 and .36)
No problem! Thank you for fixing this issue so fast!
fixed in .37-rc1: commit cf10700bf8047f0668dd874b607f89516612e6c7 Author: Greg Kroah-Hartman <gregkh@suse.de> Date: Sat Oct 9 13:26:12 2010 -0700 Staging: phison: fix problem caused by libata change