On Fri, 19 Feb 2010, Andrew Morton wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=15321 > > > > Summary: vfat usb device cannot be mounted on 2.6.32, works on > > 2.6.26 ... > > Hi, > > > > This is my first kernel bug, I hope the report is filled correctly. I am filing > > it on advice from Moritz Muehlenhoff of the Debian kernel team, see > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569906 > > > > Repeating the story for your convenience: The device is a so-called MP4 Player. > > I can mount it on a machine running Debian Stable, that is, kernel 2.6.26, by > > just specifying the vfat filesystem type. I cannot mount it on Debian unstable, > > running kernel 2.6.32, nor on Ubuntu 9.10, which uses 2.6.31-19. What do you mean exactly? That is, what happens when you try to mount it? > > I am copying below the relevant part of dmesg output from 2.6.32 (as collected > > by Debian's reportbug utility), and attaching three files: dmesg from 2.6.26, > > and "lsusb -v" from both systems when the device is attached. These inputs (and > > perhaps others which are on the Debian bug) led mr. Muehlenhoff to the > > conclusion that the problem is related to the "list of USB mass storage > > devices, which are not fully standards compliant and to which several > > workarounds are applied". Muehlenhoff wasn't entirely correct; 2.6.26 does include an entry with idVendor=10d6, but it has idProduct=2200 instead of 1101. The best way to find the cause of the problem is for you to collect a usbmon trace under 2.6.32, showing what happens when you plug in the drive and try to mount it. See the kernel source file Documentation/usb/usbmon.txt for instructions. Attach the trace to the bug report and then reply to this email to let us know it's ready. It wouldn't hurt to collect an analogous usbmon trace under 2.6.26; the differences between the two traces might be informative. 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
