Re: [uml-devel] Unable to handle kernel paging request ...

[BlaisorBlade <blaisorblade_spam@yahoo.it>]

Alle 05:31, giovedì 8 luglio 2004, Michael Koehne ha scritto:
> Moin BlaisorBlade,

>   I'll stick to that combo for some more days (because of laziness ;)
>   and hope to be more patient writing down the kernel panic next time.
If you can, try also using, instead, a vanilla kernel. I'm highly suspicious 
your crash is not SKAS-related.

If you get that panic with a kernel without any SKAS patch, then you should 
report it onto the LKML (Linux Kernel Mailing List), hopefully with a stack 
trace (yes, it's painful to write it down... - at least try providing the 
names of the funcs involved - for instance, in this panic output (I've 
received it a few minutes ago) There are only some interesting part (I marked 
them with >):

> Jun 27 12:11:25 nimbus kernel: Unable to handle kernel paging request at
virtual address 00100104

Jun 27 12:11:25 nimbus kernel:  printing eip:
Jun 27 12:11:25 nimbus kernel: c011b31f
Jun 27 12:11:25 nimbus kernel: *pde = 00000000
Jun 27 12:11:25 nimbus kernel: Oops: 0002 [#1]
Jun 27 12:11:25 nimbus kernel: SMP 
Jun 27 12:11:25 nimbus kernel: CPU:    0
Jun 27 12:11:25 nimbus kernel: EIP:    0060:[<c011b31f>]    Not tainted
Jun 27 12:11:25 nimbus kernel: EFLAGS: 00010202   (2.6.5040422) 

> Jun 27 12:11:25 nimbus kernel: EIP is at mmput+0x23/0x68

Jun 27 12:11:25 nimbus kernel: eax: 00100100   ebx: ee2d3e00   ecx: ee2d3e34
edx: 00200200
Jun 27 12:11:25 nimbus kernel: esi: f5804c60   edi: 00000037   ebp: 00000000
esp: f085df80
Jun 27 12:11:25 nimbus kernel: ds: 007b   es: 007b   ss: 0068

> Jun 27 12:11:25 nimbus kernel: Process linux-2.6.5-a1- (pid: 8864,
threadinfo=f085c000 task=c1b5f290)

Jun 27 12:11:25 nimbus kernel: Stack: ee2d3e00 c010d0d4 ee2d3e00 00000037
00000044 00000037 f085c000 f085c000 
Jun 27 12:11:25 nimbus kernel:        f5804c60 f636f080 a696b5e8 0000001c
c0149aa4 00000044 bfc00000 00000001 
Jun 27 12:11:25 nimbus kernel:        c0108573 00000037 000022a2 00000000
00000044 00000037 a696b65c 0000001a 

> And finally, these lines are VERY important (I don't care the <c010...> 
part, just the "sys_ptrace"-"sys_write"-"syscall_call" part.

Jun 27 12:11:25 nimbus kernel: Call Trace:
Jun 27 12:11:25 nimbus kernel:  [<c010d0d4>] sys_ptrace+0x754/0x7d0
Jun 27 12:11:25 nimbus kernel:  [<c0149aa4>] sys_write+0x44/0x4c
Jun 27 12:11:25 nimbus kernel:  [<c0108573>] syscall_call+0x7/0xb

Jun 27 12:11:25 nimbus kernel: 
Jun 27 12:11:25 nimbus kernel: Code: 89 50 04 89 02 c7 43 34 00 01 10 00 c7
41 04 00 02 20 00 ff

So you could write down, for that panic:
----
Unable to handle kernel paging request at
virtual address???

EIP is at mmput

Call Trace:

sys_ptrace
sys_write
syscall_call
----
The other part are harder to decode and much less useful, in this situation 
(they can be used, but it's difficult).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel