Hi, Il giorno mer, 05/06/2019 alle 16.55 +0200, Greg KH ha scritto: > On Wed, Jun 05, 2019 at 09:36:04AM +0200, Andrea Vai wrote: > > Hi, > > Il giorno mar, 04/06/2019 alle 07.43 +0200, Greg KH ha scritto: > > > 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? > > > > # first bad commit: [534903d60376b4989b76ec445630aa10f2bc3043] > > drm/atomic: Use explicit old crtc state in > > drm_atomic_add_affected_planes() > > > > By the way, as I am not expert, is there a way to double-check > that I > > bisected correctly? (such as, e.g., test with the version before > this > > one, and then with this commit applied?) > > How exactly are you "testing" this? > > I would recommend a script that does something like: > mount the disk somewhere > copy a big file to it > unmount the disk > > testing how long the whole process takes, especially the 'unmount' > is > important. Are you doing that? Well, not exactly, and thank you for pointing me out. I am doing the job in two ways, from the DE (when I am located at the PC), or in an ssh session when I am away. In ssh I manually mount the media, then run touch begin date <cp command> date touch end so I get the time kept looking at the output of "date", or at the date of the begin/end files. I understand that if I don't unmount the media I cannot be sure all data has been written, but if the cp command is still not finished after 20, 30 minutes then I can tag the commit as "bad". Since I obtained one "good" behavior only (1-2 minutes) among 10+ tests, I took for sure it was a"good" commit, and I may have made a mistake there (because I am not sure I actually unmounted the media). If I use the DE (where the media is mounted automatically) I used to "eject" the media after the copy finished, and took note of the time used until the media was correctly "ejected" (and, so, unmounted). Anyway, I know that I can do all of this in a better way, and will let you know. > > Also, you should probably just boot into text mode for this, most > graphical DEs like to auto-mount disks these days. Thank you for clarifying. As said above, actually I think I have took care of it, but I can do another bisect by turning off the automount feature of USB media in my DE, and mount/unmount only by command line. First of all, I will try to revert the commit, and see what happens. If the test fails, I will run another bisect. Thank you for your patience, Best regards Andrea
