On Sat, 10 Aug 2013, Thomas Richter wrote: > Hi Alan, > > >> Will try and report back, thanks. I've bisected it down in the meantime > >> to a change from 2.6.31.6 to 2.6.32.6. Interestingly, this is very much > >> the same time when the udev userland changed. It works with 2.6.31.6 old > >> udev, but not with 2.6.36.2, new udev. > > > > Can't you use the new udev with the old kernel? > > Nope. udevd refuses to start and says that it requires at least 2.6.32, > which means that apparently something changed in the kernel-userland > interface in 2.6.32. Thus, my conclusion that there's probably something > nasty going on in userland with udev.
What about the old udev with the newer kernel? > Here's what I got: "messages" - output from /var/log/messages. Note that > the mount hangs exactly at the SCSI 2A command you see there, then tries > to reset the device after probably 20 seconds or so. It looks like the controller is having trouble sending the large packets for the write. I have no idea why. At this point, bisection continues to look like the best approach. Maybe you can confine the search to just the commits that touch files under drivers/usb/host; then perhaps the intermediate kernels will continue to work with the old udev. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
