On Tue, 4 Aug 2009, Praveen G K wrote: > >> This locks up the device completely, I am not even able to use the > >> magic sysrq keys to determine the Program counter location. I > >> connected the device to the debugger, but I am still not able to know > >> where it is getting locked up. > >> > >> Could this be due to a corrupt fat file system? What is a possible > >> workaround to avoid this error message? > >> > >> (Initially I thought that this issue was related to the bad usb cable > >> issue I posted earlier!!) > > > > You should give us more complete information. Which version of Linux > > are you running on the device? What kind of device is it? What > > command do you use to load g_file_storage? How do you initiate the > > file copy? And so on... > I am using 2.6.22 kernel version on the device. I use What kind of device is it? Which USB peripheral driver are you using? Does the same thing happen if you upgrade to 2.6.30? A lot of bugs have been fixed in the last two years... > modprobe g_file_storage file='vfat-parition-address' removable=y stall=1 vfat-parition-address is a normal file, right? > Once the vfat partition is mounted on windows, I just drag and copy > the file from windows > to the device. This does not happen every single time. It happens at > random intervals > (maybe once in ten times). The device is not workable until it is > reset completely. This could be caused by a bug in the peripheral driver. If you enable debugging in the driver and send all the kernel messages to the screen by typing Alt-SysRq-8, what do you see when the device locks up? 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
