Lines Matching refs:kernel
5 ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops
9 and send the output the maintainer of the kernel area that seems to be
17 linux-kernel@vger.kernel.org. Thanks for your help in making Linux as
23 Normally the Oops text is read from the kernel buffers by klogd and
26 in which case you can run dmesg > file to read the data from the kernel
40 (3) Patch the kernel with one of the crash dump patches. These save
42 these are standard kernel patches so you have to find and apply
43 them yourself. Search kernel archives for kmsgdump, lkcd and
57 How to track down an Oops.. [originally a mail to linux-kernel]
73 Oh, it helps if the report happens on a kernel that is compiled with the
115 programs to search for specific patterns in the kernel code segment, and
117 that really requires pretty good knowledge of the kernel just to be able
130 In order to help Linus and the other kernel developers there has been
136 translates important addresses in the kernel log messages to their
137 symbolic equivalents. This translated kernel message is then
140 and forwarded to the kernel developers.
150 Dynamic address translation is important when kernel loadable modules
151 are being used. Since memory for kernel modules is allocated from the
152 kernel's dynamic memory pools there are no fixed locations for either
155 The kernel supports system calls which allow a program to determine
158 to debug a protection fault which occurs in a loadable kernel module.
165 Since the kernel module environment can be dynamic there must be a
176 kernel loadable modules.
181 Aug 29 09:51:01 blizard kernel: Unable to handle kernel paging request at virtual address f15e97cc
182 Aug 29 09:51:01 blizard kernel: current->tss.cr3 = 0062d000, %cr3 = 0062d000
183 Aug 29 09:51:01 blizard kernel: *pde = 00000000
184 Aug 29 09:51:01 blizard kernel: Oops: 0002
185 Aug 29 09:51:01 blizard kernel: CPU: 0
186 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
187 Aug 29 09:51:01 blizard kernel: EFLAGS: 00010212
188 Aug 29 09:51:01 blizard kernel: eax: 315e97cc ebx: 003a6f80 ecx: 001be77b edx: 00237c0c
189 Aug 29 09:51:01 blizard kernel: esi: 00000000 edi: bffffdb3 ebp: 00589f90 esp: 00589f8c
190 Aug 29 09:51:01 blizard kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
191 Aug 29 09:51:01 blizard kernel: Process oops_test (pid: 3374, process nr: 21, stackpage=00589000)
192 Aug 29 09:51:01 blizard kernel: Stack: 315e97cc 00589f98 0100b0b4 bffffed4 0012e38e 00240c64 003a6f…
193 Aug 29 09:51:01 blizard kernel: 00000000 00237810 bfffff00 0010a7fa 00000003 00000001 000000…
194 Aug 29 09:51:01 blizard kernel: bffffdb3 bffffed4 ffffffda 0000002b 0007002b 0000002b 000000…
195 Aug 29 09:51:01 blizard kernel: Call Trace: [oops:_oops_ioctl+48/80] [_sys_ioctl+254/272] [_system_…
196 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
210 counter, this indicates that the kernel has been tainted by some
222 The primary reason for the 'Tainted: ' string is to tell kernel
223 debuggers if this is a clean kernel or if anything unusual has
225 unloading the tainted value remains to indicate that the kernel is not