https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268490
--- Comment #29 from Kevin Bowling <kbowl...@freebsd.org> --- I think the intention there is to try and figure out what coincidental commit could be at fault because the offending commit is just enabling functionality but is not necessarily a smoking gun. I'm not sure if there is a streamlined way to do this kind of bisect, hopefully 'git cherry-pick' and 'git reset' will suffice in the build/test loop. Right now the likely suspects could be flag management changes in e1000 or some change in lagg(4) I am not privy to. -- You are receiving this mail because: You are the assignee for the bug.
