On Mon, Jun 03, 2019 at 01:13:48PM +0200, Andrea Vai wrote: > Il giorno gio, 30/05/2019 alle 06.25 -0700, Greg KH ha scritto: > > [...] > Hi, > > > Any chance you can use 'git bisect' to find the offending commit? > Yes, I am doing it as I managed to build the kernel from source Great! What did you find? > > And did you accidentally turn on "sync" for the filesystem? > Sorry, I don't think so but actually I don't know exactly what it is > nor how to check it... > > > How do you > > know the old kernel really flushed the buffers out in 1 minute? > > I used to try to unmount the usb media (e.g. "eject" using Nautilus > file manager), and got a message stating the filesystem was in use and > could not be mounted, so always answered to not eject it until it was > unmounted without any warning... does it make sense? That does not mean that the data is not flushed to the device yet, that just means that some userspace program is still accessing the device. You need to run some other type of test to validate how long it taks for the data to get to the device. > > But 12 > > minutes is really long, did anything else change in your userspace > > between the kernel changes as well? > I am not sure if I understand correctly the "userspace" you mention: > if you mean my home directory and contents, settings etc, then yes, > maybe... but while I am doing the tests I am quite sure I didn't > change anything, and double-checked many times that the 4.20 kernel is > always working (I usually boot up with it when I need to do the usual > day work). I mean, did any other programs on your machine change between the upgrade of your kernel? Maybe some gnome-tracker is going off and indexing all of the data on that device after you mount it, and it wasn't previously doing that before. As it is still busy, something has some open files on that device. good luck! greg k-h
