Thanks a lot! Now I understand how to work with bisect in general. However, its log is unlikely to be of help because I use my distro tools to make a kernel package. So I dropped down into the merge commit and for now I am here: index : kernel/git/davem/net-next.git commit - time&date - works or not 80f232121b69cc69a31ccb2b38c1665d770b0710 - 2019-05-07 22:03:58 -0700 - y 5d438e200215f61ca6a7aa69f3c4e035ac54d8ee - 2019-04-25 11:03:52 +0200 - y 6f6a407a591ebe3e4c6bd2329b29862b3980a3ca - 2019-05-03 18:00:15 +0200 - bug introduced? Not sure: Jun 06 18:57:33 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000370 But no log-in issues which were preventing me from logging in as whole merge 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a did, so there must be something else after this commit too. For now I marked it as "bad". e823d948b7e53dc982c867ac4ce7877fc0418897 - 2019-04-30 17:55:08 +0200 - this is being built at the moment. Bisect log, just in case: git bisect start # bad: [132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a] Merge tag 'usb-5.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb git bisect bad 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a # good: [86dc59e39031fb0d366d5b1f92db015b24bef70b] net: dsa: sja1105: Make 'sja1105et_regs' and 'sja1105pqrs_regs' static git bisect good 86dc59e39031fb0d366d5b1f92db015b24bef70b # good: [80f232121b69cc69a31ccb2b38c1665d770b0710] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next git bisect good 80f232121b69cc69a31ccb2b38c1665d770b0710 # good: [5d438e200215f61ca6a7aa69f3c4e035ac54d8ee] usb: typec: ucsi: ccg: add get_fw_info function git bisect good 5d438e200215f61ca6a7aa69f3c4e035ac54d8ee # bad: [6f6a407a591ebe3e4c6bd2329b29862b3980a3ca] Merge tag 'usb-serial-5.2-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-next git bisect bad 6f6a407a591ebe3e4c6bd2329b29862b3980a3ca Have a good day, Vladimir чт, 6 июн. 2019 г. в 02:59, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>: > > On Wed, Jun 05, 2019 at 04:36:23PM +1000, Vladimir Yerilov wrote: > > Good day Mr. Kroah-Hartman, > > > > I've found the culprit commit. It took a while though but now I'm sure: > > > > commit - brief decription - time - works (y) or not (n) > > 670784fb4ebe54434e263837390e358405031d9e - rc1 2019-05-20 > > e260ad01f0aa9e96b5386d5cd7184afd949dc457 - rc0 2019-05-14 19:52:51 -0700 n > > 8ea5b2abd07e2280a332bd9c1a7f4dd15b9b6c13 - rc0 2019-05-09 19:35:41 -0700 n > > 54516da1ea859dd4f56ebba2e483d2df9d7c8a32 - rc0 2019-05-05 21:58:36 -0700 y > > 71ae5fc87c34ecbdca293c2a5c563d6be2576558 - rc0 2019-05-06 20:29:45 -0700 y > > 80f232121b69cc69a31ccb2b38c1665d770b0710 - rc0 2019-05-07 22:03:58 -0700 y > > a2d635decbfa9c1e4ae15cb05b68b2559f7f827c - rc0 2019-05-08 21:35:19 -0700 n > > 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a - rc0 2019-05-08 10:03:52 -0700 n > > 86dc59e39031fb0d366d5b1f92db015b24bef70b - rc0 2019-05-08 09:46:44 -0700 y > > > > So 86dc59e39031fb0d366d5b1f92db015b24bef70b is the last working for > > me, and 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a is the breaking one: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc3&id=132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a > > 132d68d37d33 ("Merge tag 'usb-5.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb") > is a merge point, which is odd, you should be able to drop down into > that and find the exact wrong commit. > > what does 'git bisect log' show? > > thanks, > > greg k-h -- ---- Best regards, Vladimir Yerilov
