From: Evgenii Lepikhin <johnlepikhin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel OOPS in MM(?)
Date: Thu, 10 Mar 2016 15:31:36 +0300 [thread overview]
Message-ID: <87io0ua507.fsf@eugene-vaio.home> (raw)
Hi,
We need help to understand the source of the problem and may be to create a bugreport. Here is crash report:
Mar 10 04:03:51 l28 kernel: [2075560.434445] BUG: unable to handle kernel paging request at 0000000040008021
Mar 10 04:03:51 l28 kernel: [2075560.434669] IP: [<ffffffff810ee519>] __kmalloc+0x69/0x100
Mar 10 04:03:51 l28 kernel: [2075560.434800] PGD b7e462067 PUD 0
Mar 10 04:03:51 l28 kernel: [2075560.434913] Oops: 0000 [#1] SMP
Mar 10 04:03:51 l28 kernel: [2075560.435044] Modules linked in: tcm_loop iscsi_target_mod target_core_pscsi target_core_file target_core_iblock target_core_mod ipt_NETFLOW(O) configfs iscsi_tcp libis
csi_tcp libiscsi scsi_transport_iscsi fuse [last unloaded: ipfw_mod]
Mar 10 04:03:51 l28 kernel: [2075560.435539] CPU: 4 PID: 27141 Comm: rm Tainted: G O 3.12.51-jl-2015-12-25 #1
Mar 10 04:03:51 l28 kernel: [2075560.435734] Hardware name: Intel Corporation S2600IP ........../S2600IP, BIOS SE5C600.86B.01.08.0003.022620131521 02/26/2013
Mar 10 04:03:51 l28 kernel: [2075560.435939] task: ffff880e622ccba0 ti: ffff880eeb008000 task.ti: ffff880eeb008000
Mar 10 04:03:51 l28 kernel: [2075560.436131] RIP: 0010:[<ffffffff810ee519>] [<ffffffff810ee519>] __kmalloc+0x69/0x100
Mar 10 04:03:51 l28 kernel: [2075560.436333] RSP: 0018:ffff880eeb009b38 EFLAGS: 00010282
Mar 10 04:03:51 l28 kernel: [2075560.436439] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000a8a73dc2
Mar 10 04:03:51 l28 kernel: [2075560.436632] RDX: 00000000a8a73dc1 RSI: 0000000000000000 RDI: 0000000000013500
Mar 10 04:03:51 l28 kernel: [2075560.438248] RBP: ffff880eeb009b58 R08: ffff88103fc13500 R09: ffffffff811a0267
Mar 10 04:03:51 l28 kernel: [2075560.438446] R10: ffff880eeb009d84 R11: 0000000000000000 R12: ffff88081f803a00
Mar 10 04:03:51 l28 kernel: [2075560.438656] R13: 0000000040008021 R14: 0000000000000250 R15: ffff880250e833b0
Mar 10 04:03:51 l28 kernel: [2075560.438851] FS: 00007fe2316dd700(0000) GS:ffff88103fc00000(0000) knlGS:0000000000000000
Mar 10 04:03:51 l28 kernel: [2075560.439045] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 10 04:03:51 l28 kernel: [2075560.439152] CR2: 0000000040008021 CR3: 0000000a20736000 CR4: 00000000000407e0
Mar 10 04:03:51 l28 kernel: [2075560.439343] Stack:
Mar 10 04:03:51 l28 kernel: [2075560.439439] 0000000000000000 0000000000000250 0000000000000060 0000000000000000
Mar 10 04:03:51 l28 kernel: [2075560.439663] ffff880eeb009b88 ffffffff811a0267 ffff881015fb7fe0 0000000000000060
Mar 10 04:03:51 l28 kernel: [2075560.439898] ffff880250e83490 0000000000000000 ffff880eeb009ba8 ffffffff811a02f8
Mar 10 04:03:51 l28 kernel: [2075560.440153] Call Trace:
Mar 10 04:03:51 l28 kernel: [2075560.440257] [<ffffffff811a0267>] kmem_alloc+0x67/0xe0
Mar 10 04:03:51 l28 kernel: [2075560.440365] [<ffffffff811a02f8>] kmem_zalloc+0x18/0x40
Mar 10 04:03:51 l28 kernel: [2075560.440473] [<ffffffff811e0523>] xfs_log_commit_cil+0x373/0x4c0
Mar 10 04:03:51 l28 kernel: [2075560.440585] [<ffffffff811aab00>] ? xfs_bmap_search_multi_extents+0xe0/0x110
Mar 10 04:03:51 l28 kernel: [2075560.440783] [<ffffffff8119fb6c>] xfs_trans_commit+0x6c/0x250
Mar 10 04:03:51 l28 kernel: [2075560.440899] [<ffffffff811875d7>] xfs_bmap_finish+0xb7/0x1a0
Mar 10 04:03:51 l28 kernel: [2075560.441017] [<ffffffff811cedd3>] xfs_itruncate_extents+0xe3/0x200
Mar 10 04:03:51 l28 kernel: [2075560.441131] [<ffffffff811cf60c>] xfs_inactive+0x27c/0x3a0
Mar 10 04:03:51 l28 kernel: [2075560.441275] [<ffffffff8105d010>] ? wake_atomic_t_function+0x40/0x40
Mar 10 04:03:51 l28 kernel: [2075560.441386] [<ffffffff8119c033>] xfs_fs_evict_inode+0x73/0x80
Mar 10 04:03:51 l28 kernel: [2075560.441498] [<ffffffff811107aa>] evict+0xaa/0x1b0
Mar 10 04:03:51 l28 kernel: [2075560.441604] [<ffffffff81110ed3>] iput+0x103/0x1a0
Mar 10 04:03:51 l28 kernel: [2075560.441713] [<ffffffff81104e0f>] do_unlinkat+0x1cf/0x240
Mar 10 04:03:51 l28 kernel: [2075560.441823] [<ffffffff810fc585>] ? SyS_newfstatat+0x25/0x30
Mar 10 04:03:51 l28 kernel: [2075560.441932] [<ffffffff8110727d>] SyS_unlinkat+0x1d/0x40
Mar 10 04:03:51 l28 kernel: [2075560.442044] [<ffffffff8148d8c2>] system_call_fastpath+0x16/0x1b
Mar 10 04:03:51 l28 kernel: [2075560.442155] Code: 65 4c 03 04 25 48 bc 00 00 49 8b 50 08 4d 8b 28 49 8b 40 10 4d 85 ed 74 6b 48 85 c0 74 66 49 63 44 24 20 48 8d 4a 01 49 8b 3c 24 <49> 8b 5c 05 00 4c 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 bd 49
Mar 10 04:03:51 l28 kernel: [2075560.442904] RIP [<ffffffff810ee519>] __kmalloc+0x69/0x100
Mar 10 04:03:51 l28 kernel: [2075560.443020] RSP <ffff880eeb009b38>
Mar 10 04:03:51 l28 kernel: [2075560.443122] CR2: 0000000040008021
Mar 10 04:03:51 l28 kernel: [2075560.443809] ---[ end trace 92cd2d4bad1896f4 ]---
Kernel 3.12.51. Gdb listing:
(gdb) list *(__kmalloc+0x69)
0xffffffff810ee519 is in __kmalloc (mm/slub.c:260).
[...]
258 static inline void *get_freepointer(struct kmem_cache *s, void *object)
259 {
260 return *(void **)(object + s->offset);
261 }
What whould be the next step? Thank you.
--
UNIX/Ocaml engineer at 1Gb.ru. Telegram: johnlepikhin
next reply other threads:[~2016-03-10 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 12:31 Evgenii Lepikhin [this message]
[not found] <fa.X8mpRPMnGYqyi5owF2ArQdnZWSQ@ifi.uio.no>
2016-03-16 4:42 ` kernel OOPS in MM(?) Evgenii Lepikhin
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=87io0ua507.fsf@eugene-vaio.home \
--to=johnlepikhin@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.