Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752998AbbGNRbZ (ORCPT ); Tue, 14 Jul 2015 13:31:25 -0400 Received: from mail.kernel.org ([198.145.29.136]:52021 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752238AbbGNRbW (ORCPT ); Tue, 14 Jul 2015 13:31:22 -0400 MIME-Version: 1.0 In-Reply-To: <1436880417.1264.16.camel@intel.com> References: <1436880417.1264.16.camel@intel.com> Date: Tue, 14 Jul 2015 10:31:20 -0700 Message-ID: Subject: Re: [lkp] [block] 86ecb9456ac: From: Ming Lin To: Huang Ying Cc: Kent Overstreet , LKML , LKP ML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1353 Lines: 39 On Tue, Jul 14, 2015 at 6:26 AM, Huang Ying wrote: > FYI, we noticed the below changes on > > git://git.kernel.org/pub/scm/linux/kernel/git/mlin/linux.git block-generic-req > commit 86ecb9456ac74ba3996d05ca1b09a7756a31bfd7 ("block: make generic_make_request handle arbitrarily sized bios") > > We found the following new message in kernel log, do you increase vmalloc usage in your patch? > > [ 6.939422] vmap allocation for size 16384 failed: use vmalloc= to increase size. [ 6.939422] vmap allocation for size 16384 failed: use vmalloc= to increase size. [ 6.955278] lguest: could not map switcher pages high This actually comes from lguest. Several weeks ago I tried lguest on qemu-kvm-i386 and saw similar problem. I didn't debug it further, but it's OK if disable CONFIG_SMP. I just double-checked it with v4.2-rc1(without this patchset) CONFIG_SMP: see the vmalloc error !CONFIG_SMP: no problem Could you confirm? BTW, it seams "qemu-kvm-i386 guest" as "lguest host" doesn't work. Need to run lguest on bare metal. Thanks. > > > Thanks, > Ying Huang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/