From: Andrew Morton <akpm@linux-foundation.org>
To: Larry Keegan <lk@pfw.demon.co.uk>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 'vmap allocation failed' with 2 graphics cards and kernel 2.6.28
Date: Wed, 4 Feb 2009 15:53:08 -0800 [thread overview]
Message-ID: <20090204155308.6efa5dc8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090204194923.30bab978@cs2.al.itld>
On Wed, 4 Feb 2009 19:49:23 +0000
Larry Keegan <lk@pfw.demon.co.uk> wrote:
> Dear Chaps,
>
> I'm experiencing a problem on a Gigabyte GA-G31M-S2L. The problem did
> not occur on kernel 2.6.25, but does on 2.6.28 and 2.6.28.2. I am using
> virgin kernels.
>
> During boot I swapon <logical_volume>. This worked fine until 2.6.28
> came along. Now, the kernel boots fine, but when I run swapon the
> following error message is displayed:
>
> vmap allocation failed: use vmalloc=<size> to increase size.
Nick, we should add a dump_stack() there too.
> The error seems to be directly related to the second graphics card
> installed in this machine. Here are the details of the on-board
> graphics chip:
>
> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
> Integrated Graphics Controller (rev 10) (prog-if 00 [VGA controller])
> Subsystem: Giga-byte Technology Device d000 Flags: bus master, fast
> devsel, latency 0, IRQ 2300 Memory at e6200000 (32-bit,
> non-prefetchable) [size=512K] I/O ports at e400 [size=8]
> Memory at d0000000 (32-bit, prefetchable) [size=256M]
> Memory at e6100000 (32-bit, non-prefetchable) [size=1M]
> Capabilities: [90] MSI: Mask- 64bit- Count=1/1 Enable+
> Capabilities: [d0] Power Management version 2
>
> and here are the details of the graphics card I added:
>
> 01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300
> SE] (rev a1) (prog-if 00 [VGA controller]) Flags: fast devsel, IRQ 16
> Memory at e0000000 (32-bit, non-prefetchable) [size=16M]
> Memory at c0000000 (64-bit, prefetchable) [size=256M]
> Memory at e1000000 (64-bit, non-prefetchable) [size=16M]
> [virtual] Expansion ROM at e2000000 [disabled] [size=128K]
> Capabilities: [60] Power Management version 2
> Capabilities: [68] MSI: Mask- 64bit+ Count=1/1 Enable-
> Capabilities: [78] Express Endpoint, MSI 00
> Capabilities: [100] Virtual Channel <?>
> Capabilities: [128] Power Budgeting <?>
>
> When I set the BIOS to initialise the nVidia PCI-Express graphics card
> first I see the vmap error. When I set the BIOS to initialise the
> on-board Intel graphics card first I do not.
>
> I have upgraded to the latest (F9) BIOS revision, but to no avail. Has
> anyone else come across this before?
This is the first report I've seen.
Unfortunately pre-2.6.28 kernels didn't have /proc/vmallocinfo.
Please send the contents of /proc/vmallocinfo. Try to avoid
wordwrapping it.
Did we intend to make /proc/vmallocinfo root-only?
Please gather the contents of /proc/iomem for 2.6.25 and for 2.6.28,
perhaps we can work something out from that.
Thanks.
next prev parent reply other threads:[~2009-02-04 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 19:49 'vmap allocation failed' with 2 graphics cards and kernel 2.6.28 Larry Keegan
2009-02-04 23:53 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 11:30 Larry Keegan
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=20090204155308.6efa5dc8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@pfw.demon.co.uk \
--cc=nickpiggin@yahoo.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox