Thank you Valdis for the quick response. Noted, I will see with the developer if he can still create a branch to document his modifications...
On Thu, Mar 19, 2020, 10:54 AM Valdis Klētnieks <[email protected]> wrote: > On Thu, 19 Mar 2020 10:22:25 +0100, Karaoui mohamed lamine said: > > > I am currently encountering a kernel oops that indicate an "invalid > opcode: > > 0000 [#1] SMP" > > > > I am working on this project https://github.com/GiantVM/Linux-DSM > > Oh geez. Don't checkin a copy of the entire kernel. Make your project be > a > branch off the kernel. Ain't nobody gonna dig through that to find what > parts > of an old kernel the Linux-DSM code has messed with. > > And you'll get smacked around with a large trout for starting a project 13 > days > ago, and using an archaeological kernel as the base rather than 5.4 or > later. > 4.9 is close to 3 years ago. > > [/usr/src/linux-next] git diff --shortstat v4.9..HEAD > 71938 files changed, 10664587 insertions(+), 4767026 deletions(-) > > So yes... something probably splattered all over part of the kernel code. > Either that, or somebody did a branch to what they thought was a function > pointer but was actually a pointer to an anthill in eastern Zimbabwe or > something. > > But nobody wants to dig through your github tree to figure out what you > did.... > >
_______________________________________________ Kernelnewbies mailing list [email protected] https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
