lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <6278d2220706121001r38a1752axba90de1b4e315f75@mail.gmail.com>
Date:	Tue, 12 Jun 2007 18:01:08 +0100
From:	"Daniel J Blueman" <daniel.blueman@...il.com>
To:	"Jon Dufresne" <jon.dufresne@...initevideocorporation.com>
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: allocation failed: out of vmalloc space - use vmalloc=<size> to increase size.

On 12 Jun, 14:30, Jon Dufresne
<jon.dufresne@...initevideocorporation.com> wrote:
> I am writing a linux kernel driver for a custom pci device. I am
> developing against the stock fedora 6 kernel on an x86. This device has
> 512 MB of IO memory reserved by BAR 3. Whenever I try to ioremap this
> space I get the error:
>
> allocation failed: out of vmalloc space - use vmalloc=<size> to increase
> size.
>
> I think I understand why this is happening. I obviously don't have
> enough vmalloc space to map such a large chunk of memory. I have been
> using Corbet's et el's "Linux Device Drivers", Love's "Linux Kernel
> Development", and many websites as a guide in this development process
> but have yet to come across information that will help me.
>
> I'm curious if there is a way around this issue. Or a better way of
> handling it so that I can properly map the entire io memory space.

You can boot with kernel parameter vmalloc=384M or so. I have
experienced problems with booting with other values, but YMMV.

Daniel

> Thanks for any help,
> Jon
-- 
Daniel J Blueman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ