On Wed, 2 Nov 2011, Axel Theilmann wrote: > hi, > > i have a type of usb-stick that works fine under older kernels (tested on > 2.6.34 and 2.6.37) but stopped working for 3.0 and 3.1 > but it seems that the reading of new sticks got a little stricter and now > under 3.0 and 3.1 it looks like this: > [80231.450605] sdl: detected capacity change from 1010826752 to 0 > [80231.451612] sd 12:0:0:0: [sdl] 1974271 512-byte logical blocks: (1.01 > GB/963 MiB) > [80231.452603] sd 12:0:0:0: [sdl] Asking for cache data failed > [80231.452605] sd 12:0:0:0: [sdl] Assuming drive cache: write through > [80231.454230] sd 12:0:0:0: [sdl] Asking for cache data failed > [80231.454233] sd 12:0:0:0: [sdl] Assuming drive cache: write through > [80231.455871] sdl: sdl1 > [80233.455182] sdl: detected capacity change from 1010826752 to 0 > [80233.456218] sd 12:0:0:0: [sdl] 1974271 512-byte logical blocks: (1.01 > GB/963 MiB) > > > the detection and changing of capacity to 0 repeats over and over. > > i have two sticks of the same type and they both show this behaviour. > it looks like initialization got a little stricter in recent kernels and now > the kernel rejects this stick. More likely it's the other way around; the stick rejects the kernel. > is this the case? > > does my interpretation make sense? > > > if yes, are there any settings that control timeouts/retries that i could > change to tune the initialization behaviour? > > > since the stick works fine on other systems, it would be nice if it worked > under recent linux kernels as well. > > > i recorded some usbmon logs, if those would help. Yes, usbmon logs will be very helpful. It will be best if you post two logs, one from a working kernel and one from a non-working kernel. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
