From: Uladzislau Rezki <urezki@gmail.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-mm@kvack.org, "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Subject: Re: linux-next: general protection fault in __free_vmap_area
Date: Mon, 3 Jun 2019 10:54:05 +0200 [thread overview]
Message-ID: <20190603085405.hypqfabymvhto3ay@pc636> (raw)
In-Reply-To: <CANaxB-x6C_=CWhfXf0Uqi6FeAkyG-onRf9E==y_V1182GqjF6A@mail.gmail.com>
On Mon, Jun 03, 2019 at 01:02:20AM -0700, Andrei Vagin wrote:
> Hello all,
>
> I tried to boot linux-next in a kvm virtual machine, but it always panics:
>
> [ 5.897542] general protection fault: 0000 [#1] SMP PTI
> [ 5.898716] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> 5.2.0-rc3-next-20190603-00001-g13841016de38 #1
> [ 5.900872] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS ?-20180724_192412-buildhw-07.phx2.fedoraproject.org-1.fc29
> 04/01/2014
> [ 5.903238] RIP: 0010:__free_vmap_area+0x7b/0x340
> [ 5.904070] Code: ad de 48 89 5d 20 48 89 45 38 48 83 c0 22 48 89
> 45 40 48 8b 05 0e 24 77 02 48 85 c0 0f 84 9e 02 00 00 48 8b 7d 00 48
> 8b 75 08 <48> 8b 50 e0 48 3b 78 e8 73 07 48 39 f2 73 19 0f 0b 48 39 f2
> 73 f9
> [ 5.907811] RSP: 0000:ffffb92f80637db0 EFLAGS: 00010202
> [ 5.908883] RAX: 6b6b6b6b6b6b6b6b RBX: ffff8f6838de9460 RCX: 6b6b6b6b6b6b6b6b
> [ 5.910349] RDX: ffff8f6838de9a80 RSI: ffffb92f81281000 RDI: ffffb92f8127c000
> [ 5.911766] RBP: ffff8f6838de9440 R08: ffff8f6838de9280 R09: ffff8f6838de9550
> [ 5.913138] R10: ffff8f6838de95c8 R11: 0000000000000000 R12: ffff8f6838de93c8
> [ 5.914594] R13: 0000000000008000 R14: ffffffff8b9fb8b0 R15: ffffffff8a61771b
> [ 5.916362] FS: 0000000000000000(0000) GS:ffff8f683ba00000(0000)
> knlGS:0000000000000000
> [ 5.918360] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 5.919926] CR2: 0000000000000000 CR3: 000000006581e001 CR4: 00000000003606f0
> [ 5.921482] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 5.923032] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ 5.924642] Call Trace:
> [ 5.925358] __purge_vmap_area_lazy+0xd0/0x170
> [ 5.926543] _vm_unmap_aliases+0x1c6/0x200
> [ 5.927498] change_page_attr_set_clr+0xbc/0x2d0
> [ 5.928540] set_memory_nx+0x37/0x40
> [ 5.929294] free_init_pages+0x53/0x90
> [ 5.930110] free_kernel_image_pages+0x1f/0x40
> [ 5.931064] ? rest_init+0x24c/0x24c
> [ 5.931832] kernel_init+0x19/0x104
> [ 5.932585] ret_from_fork+0x3a/0x50
> [ 5.933326] Modules linked in:
> [ 5.934015] ---[ end trace 07dd6f9c635fabc2 ]---
> [ 5.934992] RIP: 0010:__free_vmap_area+0x7b/0x340
>
> The kernel config is attached. Let me know if you need any additional
> information.
>
> Thanks,
> Andrei
Hello, Andrei.
I have some questions. Are you able to see the entire kernel log? I mean
what happened before 5.897542 time-stamp. Also, could you please provide
details how you run your KVM machine?
Thank you in advance!
--
Vlad Rezki
prev parent reply other threads:[~2019-06-03 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 8:02 Andrei Vagin
2019-06-03 8:54 ` Uladzislau Rezki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190603085405.hypqfabymvhto3ay@pc636 \
--to=urezki@gmail.com \
--cc=avagin@gmail.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox