All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: Dave Jones <davej@redhat.com>,
	"Michael L. Semon" <mlsemon35@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	d.hatayama@jp.fujitsu.com, akpm@linux-foundation.org
Subject: Re: [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit
Date: Wed, 10 Jul 2013 13:27:36 -0400	[thread overview]
Message-ID: <CAJzLF9=vWCd2JZTNG0dX4YmLAc=B05x-+bZgU0RaSZCaR5D38g@mail.gmail.com> (raw)
In-Reply-To: <20130710015936.GC13855@redhat.com>

Thanks.  I'll re-review this, anyway, and re-bisect if time allows.
The kernel/SGI-XFS combo pulled last night did much better in this
regard.  The problem is down to a different and single backtrace about
vmalloc, and the PC is controllable now.  The old git was moved to a
different folder, though, in case it's still needed.

Michael

On Tue, Jul 9, 2013 at 9:59 PM, Dave Jones <davej@redhat.com> wrote:
> On Tue, Jul 09, 2013 at 09:51:32PM -0400, Michael L. Semon wrote:
>
>  > kernel: [ 2580.395592] vmap allocation for size 20480 failed: use vmalloc=<size> to increase size.
>  > kernel: [ 2580.395761] vmalloc: allocation failure: 16384 bytes
>
> I was seeing a lot of these recently too.
> (Though I also saw memory corruption afterwards possibly caused by
>  a broken fallback path somewhere when that vmalloc fails)
>
> http://comments.gmane.org/gmane.linux.kernel.mm/102895
>
>         Dave
>

WARNING: multiple messages have this Message-ID (diff)
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: Dave Jones <davej@redhat.com>,
	"Michael L. Semon" <mlsemon35@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	d.hatayama@jp.fujitsu.com, akpm@linux-foundation.org
Subject: Re: [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit
Date: Wed, 10 Jul 2013 13:27:36 -0400	[thread overview]
Message-ID: <CAJzLF9=vWCd2JZTNG0dX4YmLAc=B05x-+bZgU0RaSZCaR5D38g@mail.gmail.com> (raw)
In-Reply-To: <20130710015936.GC13855@redhat.com>

Thanks.  I'll re-review this, anyway, and re-bisect if time allows.
The kernel/SGI-XFS combo pulled last night did much better in this
regard.  The problem is down to a different and single backtrace about
vmalloc, and the PC is controllable now.  The old git was moved to a
different folder, though, in case it's still needed.

Michael

On Tue, Jul 9, 2013 at 9:59 PM, Dave Jones <davej@redhat.com> wrote:
> On Tue, Jul 09, 2013 at 09:51:32PM -0400, Michael L. Semon wrote:
>
>  > kernel: [ 2580.395592] vmap allocation for size 20480 failed: use vmalloc=<size> to increase size.
>  > kernel: [ 2580.395761] vmalloc: allocation failure: 16384 bytes
>
> I was seeing a lot of these recently too.
> (Though I also saw memory corruption afterwards possibly caused by
>  a broken fallback path somewhere when that vmalloc fails)
>
> http://comments.gmane.org/gmane.linux.kernel.mm/102895
>
>         Dave
>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2013-07-10 17:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10  1:51 [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit Michael L. Semon
2013-07-10  1:51 ` Michael L. Semon
2013-07-10  1:59 ` Dave Jones
2013-07-10  1:59   ` Dave Jones
2013-07-10 17:27   ` Michael L. Semon [this message]
2013-07-10 17:27     ` Michael L. Semon

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='CAJzLF9=vWCd2JZTNG0dX4YmLAc=B05x-+bZgU0RaSZCaR5D38g@mail.gmail.com' \
    --to=mlsemon35@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.