From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Christoph Lameter <cl@linux.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: linux-next: kernel BUG at mm/slub.c:1447!
Date: Thu, 1 Oct 2015 09:06:15 -0700 [thread overview]
Message-ID: <560D59F7.4070002@roeck-us.net> (raw)
Seen with next-20151001, running qemu, simulating Opteron_G1 with a non-SMP configuration.
On a re-run, I have seen it with the same image, but this time when simulating IvyBridge,
so it is not CPU dependent. I did not previously see the problem.
Log is at
http://server.roeck-us.net:8010/builders/qemu-x86-next/builds/259/steps/qemubuildcommand/logs/stdio
I'll try to bisect. The problem is not seen with every boot, so that may take a while.
Guenter
---
gfp: 2
------------[ cut here ]------------
invalid opcode: 0000 [#1] PREEMPT
Modules linked in:
CPU: 0 PID: 121 Comm: udevd Not tainted 4.3.0-rc3-next-20151001-yocto-standard #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
task: ced90000 ti: ced8c000 task.ti: ced8c000
EIP: 0060:[<c1128873>] EFLAGS: 00000092 CPU: 0
EIP is at new_slab+0x353/0x360
EAX: 00000006 EBX: 00000000 ECX: 00000001 EDX: 80000001
ESI: cf8019c0 EDI: 00000000 EBP: ced8daa4 ESP: ced8da7c
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
CR0: 8005003b CR2: 080791c0 CR3: 0ed6c000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: 00000000 DR7: 00000000
Stack:
c19a42cf 00000002 c137542e ced8da90 c137544c ffffffff c144c8a8 00000000
cf8019c0 00000000 ced8db28 c1129ca8 0203128a c144f346 00004e20 cec2e740
c10ee933 0203128a cf8019c0 c181d6c0 c181d460 000001a1 00150015 c0011c00
Call Trace:
[<c137542e>] ? __delay+0xe/0x10
[<c137544c>] ? __const_udelay+0x1c/0x20
[<c144c8a8>] ? ide_execute_command+0x68/0xa0
[<c1129ca8>] ___slab_alloc.constprop.75+0x248/0x310
[<c144f346>] ? do_rw_taskfile+0x286/0x320
[<c10ee933>] ? mempool_alloc_slab+0x13/0x20
[<c1457d12>] ? ide_do_rw_disk+0x222/0x320
[<c1136219>] __slab_alloc.isra.72.constprop.74+0x18/0x1f
[<c112a2f2>] kmem_cache_alloc+0x122/0x1c0
[<c10ee933>] ? mempool_alloc_slab+0x13/0x20
[<c10ee933>] mempool_alloc_slab+0x13/0x20
[<c10eebe5>] mempool_alloc+0x45/0x170
[<c1345202>] bio_alloc_bioset+0xd2/0x1b0
[<c1172e9f>] mpage_alloc+0x2f/0xa0
[<c1037979>] ? kmap_atomic_prot+0x59/0xf0
[<c1173523>] do_mpage_readpage+0x4d3/0x7e0
[<c10f31b8>] ? __alloc_pages_nodemask+0xf8/0x8c0
[<c134ed67>] ? blk_queue_bio+0x267/0x2d0
[<c112a24a>] ? kmem_cache_alloc+0x7a/0x1c0
[<c138357f>] ? __this_cpu_preempt_check+0xf/0x20
[<c1173894>] mpage_readpage+0x64/0x80
[<c119fa90>] ? __ext2_truncate_blocks+0x450/0x450
[<c10f8dfd>] ? lru_cache_add+0xd/0x10
[<c10ec367>] ? add_to_page_cache_lru+0x57/0x90
[<c119f3b4>] ext2_readpage+0x14/0x20
[<c10ec62b>] do_read_cache_page+0x7b/0x1c0
[<c119f3a0>] ? ext2_writepages+0x20/0x20
[<c10ec7c4>] read_cache_page+0x24/0x30
[<c119d1e3>] ext2_get_page.isra.10+0x23/0x250
[<c114c663>] ? __d_rehash+0x43/0x60
[<c114c6ca>] ? d_rehash+0x4a/0x70
[<c114dbec>] ? d_splice_alias+0x7c/0x280
[<c11a0dba>] ? ext2_iget+0x1fa/0x370
[<c119d7b0>] ext2_find_entry+0x80/0x200
[<c114e44a>] ? d_alloc+0x4a/0x70
[<c114151e>] ? lookup_real+0x1e/0x50
[<c114e082>] ? __d_alloc+0x22/0x120
[<c119d99b>] ext2_inode_by_name+0x1b/0x40
[<c11a1d92>] ext2_lookup+0x42/0xa0
[<c114e44a>] ? d_alloc+0x4a/0x70
[<c114151e>] lookup_real+0x1e/0x50
[<c11453d1>] path_openat+0x791/0xdc0
[<c139da03>] ? device_show+0x23/0x30
[<c11991fe>] ? kernfs_put_open_node.isra.7+0x7e/0xa0
[<c1105715>] ? kvfree+0x45/0x50
[<c1146940>] do_filp_open+0x60/0xb0
[<c1152a47>] ? __alloc_fd+0xb7/0x100
[<c1138043>] do_sys_open+0x123/0x220
[<c113a2cc>] ? fput+0x4c/0x90
[<c1138162>] SyS_open+0x22/0x30
[<c17be051>] syscall_call+0x7/0x7
Code: 8b 46 7c d3 e2 89 d1 89 fa e8 1a ae 00 00 85 c0 0f 85 dc fe ff ff e9 34 fd ff ff 89 44 24 04 c7 04 24 cf 42 9a c1 e8 b9 1f fc ff <0f> 0b 8d 74 26 00 8d bc 27 00 00 00 00 55 89 e5 57 56 53 83 ec
EIP: [<c1128873>] new_slab+0x353/0x360 SS:ESP 0068:ced8da7c
---[ end trace 7503d0e5896d8e13 ]---
Kernel panic - not syncing: Fatal exception
Kernel Offset: disabled
---[ end Kernel panic - not syncing: Fatal exception
qemu: terminating on signal 15 from pid 18056
next reply other threads:[~2015-10-01 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:06 Guenter Roeck [this message]
2015-10-01 16:58 ` linux-next: kernel BUG at mm/slub.c:1447! Christoph Lameter
2015-10-01 20:49 ` Andrew Morton
2015-10-01 20:49 ` Andrew Morton
2015-10-02 7:25 ` Michal Hocko
2015-10-02 7:25 ` Michal Hocko
2015-10-02 8:53 ` Michal Hocko
2015-10-02 8:53 ` Michal Hocko
2015-10-02 20:49 ` Andrew Morton
2015-10-02 20:49 ` Andrew Morton
2015-10-05 13:47 ` Michal Hocko
2015-10-05 13:47 ` Michal Hocko
2015-10-05 19:29 ` Andrew Morton
2015-10-05 19:29 ` Andrew Morton
2015-10-06 2:12 ` Andrew Morton
2015-10-06 2:12 ` Andrew Morton
2015-10-06 5:12 ` Dave Chinner
2015-10-06 5:12 ` Dave Chinner
2015-10-02 13:36 ` Guenter Roeck
2015-10-02 13:36 ` Guenter Roeck
2015-10-02 13:42 ` Michal Hocko
2015-10-02 13:42 ` Michal Hocko
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=560D59F7.4070002@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=kirill.shutemov@linux.intel.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.