From: Martin Bligh <mbligh@google.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andy Whitcroft <apw@shadowen.org>
Subject: Re: xfs fails dbench in 2.6.18-rc1-mm1
Date: Wed, 12 Jul 2006 14:31:27 -0700 [thread overview]
Message-ID: <44B56A2F.5010204@google.com> (raw)
In-Reply-To: <1152739939.22840.1.camel@dyn9047017100.beaverton.ibm.com>
> I am not able to "insmod xfs.ko" on my x86-64 machine :(
>
> elm3b29:~ # modprobe xfs
> FATAL: Error inserting xfs (/lib/modules/2.6.18-rc1-
> mm1/kernel/fs/xfs/xfs.ko): Cannot allocate memory
>
> #dmesg shows ..
>
> Could not allocate 8 bytes percpu data
> Could not allocate 8 bytes percpu data
> Could not allocate 8 bytes percpu data
> Could not allocate 8 bytes percpu data
> Could not allocate 8 bytes percpu data
> Could not allocate 8 bytes percpu data
> Could not allocate 328 bytes percpu data
> Could not allocate 328 bytes percpu data
> Could not allocate 328 bytes percpu data
>
>
> Whats happening here ?
Dunno, but I built it statically, and didn't have that problem ;-)
The default config on elm3b6 should work.
http://ftp.kernel.org/pub/linux/kernel/people/mbligh/config/abat/amd64
next prev parent reply other threads:[~2006-07-12 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:58 xfs fails dbench in 2.6.18-rc1-mm1 Martin Bligh
2006-07-12 17:12 ` Eric Dumazet
2006-07-12 17:36 ` Andy Whitcroft
2006-07-12 20:13 ` Martin Bligh
2006-07-12 20:25 ` Badari Pulavarty
2006-07-12 20:26 ` Martin Bligh
2006-07-12 21:32 ` Badari Pulavarty
2006-07-12 21:31 ` Martin Bligh [this message]
2006-07-12 21:53 ` Keith Mannthey
2006-07-13 0:43 ` Badari Pulavarty
2006-07-13 14:42 ` Andy Whitcroft
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=44B56A2F.5010204@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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