On Thu, Feb 7, 2019 at 11:01 PM Ian Kumlien <[email protected]> wrote: > On Thu, Feb 7, 2019 at 7:43 PM Saeed Mahameed <[email protected]> > wrote: > > On Thu, Feb 7, 2019 at 2:17 AM Ian Kumlien <[email protected]> wrote: > > > On Thu, Feb 7, 2019 at 2:01 AM Saeed Mahameed <[email protected]> > > > wrote: > > > > On Wed, Feb 6, 2019 at 3:00 PM Ian Kumlien <[email protected]> > > > > wrote: > > > > > It changes directly after the first hw checksum failure, I don't know > > > > > why =/ > > > > > > > > weird, Maybe a real check-summing issue/corruption on the PCI ?! > > > > > > Actually, it seems to have been introduced in 4.20.6 - 4.20.5 works just > > > fine
> > Great, the difference is only 120 patches. > > that is bisect-able, it will only take 5 iterations to find the > > offending commit. > > I just wish it wasn't a server that takes, what feels like 5 minutes to > boot... > > All of these seas of sensors 2d and 3d... =P > > But, yep, that's the plan Huh, spent most of the day with two bisects and none of them yielded any results.... Looks like I'll have to start investigating the elrepo kernel-ml build =(
