Lines Matching +full:no +full:- +full:dump +full:- +full:oops
4 Kernel bug reports often come with a stack dump like the one below::
6 ------------[ cut here ]------------
8 …Modules linked in: dvb_usb_gp8psk(-) dvb_usb dvb_core nvidia_drm(PO) nvidia_modeset(PO) snd_hda_co…
9 CPU: 1 PID: 28102 Comm: rmmod Tainted: P WC O 4.8.4-build.1 #1
10 Hardware name: MSI MS-7309/MS-7309, BIOS V1.12 02/23/2009
38 ---[ end trace 6ebc60ef3981792f ]---
42 the issue, it may also contain the word **Oops**, as on this one::
47 Oops: 0002 [#1] PREEMPT SMP
50 Despite being an **Oops** or some other sort of stack trace, the offended
52 we'll refer to "Oops" for all kinds of stack traces that need to be analyzed.
58 -----------------
62 file:`Documentation/admin-guide/tainted-kernels.rst`, "being loaded" is
63 annotated with "+", and "being unloaded" is annotated with "-".
66 Where is the Oops message is located?
67 -------------------------------------
69 Normally the Oops text is read from the kernel buffers by klogd and
86 the screen with a digital camera - not nice, but better than
93 :ref:`Documentation/admin-guide/serial-console.rst <serial_console>`),
97 (3) Use Kdump (see Documentation/admin-guide/kdump/kdump.rst),
99 gdbmacro in Documentation/admin-guide/kdump/gdbmacros.txt.
102 --------------------------
106 ``gdb`` is easier, but the Kernel should be pre-compiled with debug info.
112 number of the OOPS from the ``vmlinux`` file.
117 $ ./scripts/config -d COMPILE_TEST -e DEBUG_KERNEL -e DEBUG_INFO
120 EIP value from the OOPS::
124 And use GDB to translate that to human-readable form::
130 offset from the OOPS::
136 $ ./scripts/config -d COMPILE_TEST -e DEBUG_KERNEL -e DEBUG_INFO
147 294 ret = -EBUSY;
187 $ gdb drivers/media/usb/dvb-usb/dvb-usb.o
199 $ objdump -r -S -l --disassemble net/dccp/ipv4.o
207 dumps using the following method (example crash dump output as shown by
221 .byte .... /* bytes from Code: part of OOPS dump */
223 Compile it with "gcc -c -o foo.o foo.s" then look at the output of
224 "objdump --disassemble foo.o".
235 mov 0x8(%ebp), %ebx ! %ebx = skb->sk
236 mov 0x13c(%ebx), %eax ! %eax = inet_sk(sk)->opt
242 -----------------
254 $ ./scripts/get_maintainer.pl --bug -f drivers/media/usb/gspca/sonixj.c
259 linux-media@vger.kernel.org (open list:GSPCA USB WEBCAM DRIVER)
260 linux-kernel@vger.kernel.org (open list)
264 - The last developers that touched the source code (if this is done inside
267 - The driver maintainer (Hans Verkuil);
268 - The subsystem maintainer (Mauro Carvalho Chehab);
269 - The driver and/or subsystem mailing list (linux-media@vger.kernel.org);
270 - The Linux Kernel mailing list (linux-kernel@vger.kernel.org);
271 - The bug reporting URIs for the driver/subsystem (none in the above example).
275 development of the code (linux-media ML) copying the driver maintainer (Hans).
279 linux-kernel@vger.kernel.org.
284 --------------
294 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` though
298 ---------------------------------------------------------------------------
300 Notes on Oops tracing with ``klogd``
301 ------------------------------------
306 version 1.3-pl3 of the ``sysklogd`` package should be used.
325 kernel's dynamic memory pools there are no fixed locations for either
346 ``modules-2.0.0`` package to automatically signal klogd whenever a module
355 Aug 29 09:51:01 blizard kernel: current->tss.cr3 = 0062d000, %cr3 = 0062d000
357 Aug 29 09:51:01 blizard kernel: Oops: 0002
359 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
368 …Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system…
371 ---------------------------------------------------------------------------
379 Phone: 701-234-7556