Lines Matching refs:kernel
9 Find the Oops and send it to the maintainer of the kernel area that seems to be
16 linux-kernel@vger.kernel.org. Thanks for your help in making Linux as
22 Normally the Oops text is read from the kernel buffers by klogd and
25 in which case you can run dmesg > file to read the data from the kernel
45 extract the kernel ring buffer from old memory with using dmesg
52 NOTE: the message from Linus below applies to 2.4 kernel. I have preserved it
58 How to track down an Oops.. [originally a mail to linux-kernel]
74 Oh, it helps if the report happens on a kernel that is compiled with the
130 programs to search for specific patterns in the kernel code segment, and
132 that really requires pretty good knowledge of the kernel just to be able
145 In order to help Linus and the other kernel developers there has been
151 translates important addresses in the kernel log messages to their
152 symbolic equivalents. This translated kernel message is then
155 and forwarded to the kernel developers.
165 Dynamic address translation is important when kernel loadable modules
166 are being used. Since memory for kernel modules is allocated from the
167 kernel's dynamic memory pools there are no fixed locations for either
170 The kernel supports system calls which allow a program to determine
173 to debug a protection fault which occurs in a loadable kernel module.
180 Since the kernel module environment can be dynamic there must be a
191 kernel loadable modules.
196 Aug 29 09:51:01 blizard kernel: Unable to handle kernel paging request at virtual address f15e97cc
197 Aug 29 09:51:01 blizard kernel: current->tss.cr3 = 0062d000, %cr3 = 0062d000
198 Aug 29 09:51:01 blizard kernel: *pde = 00000000
199 Aug 29 09:51:01 blizard kernel: Oops: 0002
200 Aug 29 09:51:01 blizard kernel: CPU: 0
201 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
202 Aug 29 09:51:01 blizard kernel: EFLAGS: 00010212
203 Aug 29 09:51:01 blizard kernel: eax: 315e97cc ebx: 003a6f80 ecx: 001be77b edx: 00237c0c
204 Aug 29 09:51:01 blizard kernel: esi: 00000000 edi: bffffdb3 ebp: 00589f90 esp: 00589f8c
205 Aug 29 09:51:01 blizard kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
206 Aug 29 09:51:01 blizard kernel: Process oops_test (pid: 3374, process nr: 21, stackpage=00589000)
207 Aug 29 09:51:01 blizard kernel: Stack: 315e97cc 00589f98 0100b0b4 bffffed4 0012e38e 00240c64 003a6f…
208 Aug 29 09:51:01 blizard kernel: 00000000 00237810 bfffff00 0010a7fa 00000003 00000001 000000…
209 Aug 29 09:51:01 blizard kernel: bffffdb3 bffffed4 ffffffda 0000002b 0007002b 0000002b 000000…
210 Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system_…
211 Aug 29 09:51:01 blizard kernel: Code: c7 00 05 00 00 00 eb 08 90 90 90 90 90 90 90 90 89 ec 5d c3
225 counter. This indicates that the kernel has been tainted by some
237 3: 'S' if the oops occurred on an SMP kernel running on hardware that
254 8: 'D' if the kernel has died recently, i.e. there was an OOPS or BUG.
258 10: 'W' if a warning has previously been issued by the kernel.
263 12: 'I' if the kernel is working around a severe bug in the platform
268 14: 'E' if an unsigned module has been loaded in a kernel supporting
273 16: 'K' if the kernel has been live patched.
275 The primary reason for the 'Tainted: ' string is to tell kernel
276 debuggers if this is a clean kernel or if anything unusual has
278 unloaded, the tainted value remains to indicate that the kernel is not