Re: [REGRESSION] x86 vmalloc issue from recent 3.10.0+ commit

[Michael L. Semon]

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@xxxxxxxxxx> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/