Mailinglist Archive: opensuse (783 mails)

< Previous Next >
Re: [opensuse] BUG: Bad page state in process suse.de-cron-lo pfn:6db6db6db6e5d85e ??
Den 2017-10-07 kl. 06:42, skrev David C. Rankin:
I am no expert in kernel Call Traces.

Me neither. But I do it from time to time in our company. Mostly because
no one else does it :)


I can read them, I understand what the
stack pointer address are saying, I'm just not 100% sure what it is telling
me. I'm also at a loss to decipher the Code:

kernel: [44716.074017] Code: 8b 44 24 18 4d 8d 2c 07 4d 3b 6d 00 0f 84 e9 02
00 00 45 85 e4 0f 84 d3 02 00 00 4d 8b 6d 08 49 83 ed 20 49 8b 45 28 49 8b 55
20 <48> 89 42 08 48 89 10 48 b8 00 01 10 00 00 00 ad de 49 89 45 20


The Code-part is a hexdump of the machine code currently running at the
time of the crash. It can be deciphered with the objdump-command.
The instruction pointer is on <48> in your byte sequence at 0x2b so you
need to adjust for that. 0x48-0x2b=0x1d

Run this:

#!/bin/sh

cat <<EOF > yourmachinecode.s
        .text
        .globl foo

foo:
        .byte
0x8b,0x44,0x24,0x18,0x4d,0x8d,0x2c,0x07,0x4d,0x3b,0x6d,0x00,0x0f,0x84,0xe9,0x02,0x00,0x00,0x45,0x85,0xe4,0x0f,0x84,0xd3,0x02,0x00,0x00,0x4d,0x8b,0x6d,0x08,0x49,0x83,0xed,0x20,0x49,0x8b,0x45,0x28,0x49,0x8b,0x55,0x20,0x89,0x42,0x08,0x48,0x89,0x10,0x48,0xb8,0x00,0x01,0x10,0x00,0x00,0x00,0xad,0xde,0x49,0x89,0x45,0x20
EOF

gcc -c -o yourmachinecode.o yourmachinecode.s
objdump --adjust-vma=0x1d --disassemble yourmachinecode.o



Anybody here speak kernel Call Trace?

Unfortunately not fluently

regards,

--
/bengan



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
References