**** BEGIN LOGGING AT Mon Jun 26 03:00:04 2017 Jun 26 16:55:47 ravikp7: I sent an email about a second bisect that I performed Jun 26 16:56:31 let me know if you need any help approaching the u-boot mailinglist Jun 26 17:02:36 m_w: yeah, I was looking at the patch. Thanks for putting time into this. Jun 26 17:03:08 I sent an email to uboot mailing list with the first bisect, it waits for moderator's approval Jun 26 17:03:44 okay CC me on further correspondence Jun 26 17:04:35 if you join the mailinglist the approval for each email is not needed Jun 26 17:05:09 I joined and did used the digest format for the emails that are sent and it is not so bad Jun 26 17:05:50 though I sit on quite a few mailinglists :) Jun 26 17:10:12 m_w: thanks, I joined the mailing list, but I guess the last email still needs approval ? Jun 26 17:11:36 yes Jun 26 17:11:51 it will take a while for the moderator to approve Jun 26 17:12:34 m_w: please do cc your findings and second bisect to the mailing list after my email Jun 26 17:16:49 since I use the digest I would need to be CC'd on the email to respond Jun 26 17:34:35 m_w: this commit [ return error from rx_submit if no request ] is an old one, why it's not hindering the transfer before the first bad commit of first bisect ? Jun 26 17:38:57 maybe I didn't finish the bisect or it was merged with a large number of other commits Jun 26 17:39:07 or I did it wrong :) Jun 26 17:39:30 either way commenting out those lines let me find when bootp started failing Jun 26 17:56:29 m_w: so, that error on no request probably isn't the cause of TFTP fail, it just works there by commenting that out, something else is causing a no request. Jun 26 17:57:37 that commit is from sep 2013, and TFTP is working even after that Jun 26 17:58:43 m_w: in the first bad commit of the second bisect, even the bootp broadcast fails ? Jun 26 18:17:57 ravikp7: yes Jun 26 18:18:18 the TFTP transfer never starts Jun 26 20:44:30 hmm **** ENDING LOGGING AT Tue Jun 27 03:00:07 2017