Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Doc/teaching/lab/kernel_modules: Fix typos #370

Merged
merged 2 commits into from
Jul 3, 2023
Merged

Doc/teaching/lab/kernel_modules: Fix typos #370

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0966920
Doc/teaching/lab/kernel_modules: Fix typos
Jun 30, 2023
1936e62
Doc/teaching/labs/kernel_api: Fix reference to error header files
Jul 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Documentation/teaching/labs/kernel_modules.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -386,7 +386,7 @@ Next line
Tells us that it's the first oops (#1). This is important in the context that
an oops can lead to other oopses. Usually only the first oops is relevant.
Furthermore, the oops code (``0002``) provides information about the error type
(see :file:`arch/x86/include/asm/traps.h`):
(see :file:`arch/x86/include/asm/trap_pf.h`):


* Bit 0 == 0 means no page found, 1 means protection fault
Expand Down Expand Up @@ -558,7 +558,7 @@ A more simplistic way to find the code that generated an oops is to use the
/root/lab-01/modul-oops/oops.c:23

Where ``0x5`` is the value of the program counter (``EIP = c89d4005``) that
generated the oops, minus the base address of the module (``0xc89c4000``)
generated the oops, minus the base address of the module (``0xc89d4000``)
according to :file:`/proc/modules`

minicom
Expand Down