Best way to debug an invalid opcode
Karaoui mohamed lamine
moharaka at gmail.com
Thu Mar 19 07:12:54 EDT 2020
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 <valdis.kletnieks at vt.edu>
> On Thu, 19 Mar 2020 10:22:25 +0100, Karaoui mohamed lamine said:
> > I am currently encountering a kernel oops that indicate an "invalid
> > 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
> branch off the kernel. Ain't nobody gonna dig through that to find what
> 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
> ago, and using an archaeological kernel as the base rather than 5.4 or
> 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
> But nobody wants to dig through your github tree to figure out what you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kernelnewbies