mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bunk@kernel.org, clameter@sgi.com,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much
Date: Tue, 08 Jan 2008 14:57:05 +0530	[thread overview]
Message-ID: <478341E9.9000703@linux.vnet.ibm.com> (raw)
In-Reply-To: <47833231.3080801@linux.vnet.ibm.com>

Kamalesh Babulal wrote:
> Andrew Morton wrote:
>> On Mon, 07 Jan 2008 16:06:20 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>>
>>> The defconfig make fails on x86_64 (AMD box) with following error
>>>
>>>   CHK     include/linux/utsrelease.h
>>>   CALL    scripts/checksyscalls.sh
>>>   CHK     include/linux/compile.h
>>>   GEN     .version
>>>   CHK     include/linux/compile.h
>>>   UPD     include/linux/compile.h
>>>   CC      init/version.o
>>>   LD      init/built-in.o
>>>   LD      .tmp_vmlinux1
>>> drivers/built-in.o(.init.text+0x8d76): In function `dmi_id_init':
>>> : undefined reference to `__you_cannot_kmalloc_that_much'
>>> make: *** [.tmp_vmlinux1] Error 1
>>>
>>>
>>> # gcc --version
>>> gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-59)
>>>
>>> This was reported by Adrian Bunk http://lkml.org/lkml/2007/12/1/39
>> That's odd.  afacit the only kmalloc in dmi_id_init() is
>>
>>         dmi_dev = kzalloc(sizeof(*dmi_dev), GFP_KERNEL);
>>
>> and even gcc-3.2.3 should be able to get that right.
>>
>> Could you please a) verify that simply removing that line fixes the build
>> error and then b) try to find some way of fixing it?
>>
>> Try replacing `sizeof(*dmi_dev)' with `sizeof(struct dmi_device_attribute)'
>> and any other tricks you can think of to try to make the compiler process
>> the code differently.
>>
> 
> removing the line fixes the issue, but changing the sizeof(*dmi_dev) to
> sizeof(struct device) is not helping.
> 

Hi, Andrew,

We tried the following, generated stabs information. The size of struct
device is 560 bytes. We found that dead code was not being eliminated
(__you_cannot_kmalloc_that_much), even though no one called that
function. I suspect builtin_constant_p() and dead code elimination as
the root causes of this error.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  reply	other threads:[~2008-01-08  9:27 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 22:19 Linux 2.6.24-rc7 Linus Torvalds
2008-01-06 23:52 ` Mark Lord
2008-01-07  0:08   ` Linus Torvalds
2008-01-07  0:35     ` Tejun Heo
2008-01-07  8:48 ` Linux 2.6.24-rc7 Build Failure on headers_install Kamalesh Babulal
2008-01-07 10:12   ` Sam Ravnborg
2008-01-08 10:51     ` Kamalesh Babulal
2008-01-08 13:10       ` Sam Ravnborg
2008-01-07 10:36 ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Kamalesh Babulal
2008-01-07 18:07   ` Andrew Morton
2008-01-07 18:31     ` Christoph Lameter
2008-01-07 19:38       ` Andrew Morton
2008-01-08  9:56         ` Jean Delvare
2008-01-08 10:44           ` Kamalesh Babulal
2008-01-08 12:34           ` Fix for __you_cannot_kmalloc_that_much failure with gcc 3.2 Jean Delvare
2008-01-08  4:20       ` Linux 2.6.24-rc7 Build-Failure at __you_cannot_kmalloc_that_much Arjan van de Ven
2008-01-08  5:23         ` Christoph Lameter
2008-01-08  8:20     ` Kamalesh Babulal
2008-01-08  9:27       ` Balbir Singh [this message]
2008-01-08  7:48   ` Jean Delvare
2008-01-07 12:13 ` Linux 2.6.24-rc7 kernel BUG at kernel/sched.c:5156! Kamalesh Babulal
2008-01-08 16:16   ` [powerpc crash] " Ingo Molnar
2008-01-07 15:53 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:27   ` smpboot_64 section mismatch warning Sam Ravnborg
2008-01-07 16:31   ` section mismatch warning in head_64.S Sam Ravnborg
2008-01-15 10:18     ` Alejandro Riveira Fernández
2008-01-07 23:27   ` smpboot_64 section mismatch warning David Howells
2008-01-08  9:14     ` Alejandro Riveira Fernández
2008-01-08 11:17   ` David Howells
2008-01-07 16:14 ` Linux 2.6.24-rc7 Alejandro Riveira Fernández
2008-01-07 16:24   ` Michael Buesch
2008-01-07 16:52     ` Alejandro Riveira Fernández
2008-01-07 17:30       ` Michael Buesch
2008-01-07 20:23         ` Alejandro Riveira Fernández
2008-01-08 15:30           ` Michael Buesch
2008-01-08 15:55             ` Alejandro Riveira Fernández
2008-01-08  0:50 ` J.A. Magallón
2008-01-09  1:32   ` Avuton Olrich
2008-01-09  1:56   ` Tejun Heo
2008-01-10  9:25     ` J.A. Magallón
2008-01-10 13:10       ` Tejun Heo
2008-01-13 23:19         ` J.A. Magallón
2008-01-13 23:57           ` Tejun Heo
2008-01-14 23:38             ` J.A. Magallón
2008-01-14 23:56               ` Tejun Heo
2008-01-08 18:42 ` Linux 2.6.24-rc7: sparc64: WARNING: at kernel/lockdep_proc.c:267 lockdep_stats_show() Mariusz Kozlowski
2008-01-08 21:00   ` Randy Dunlap
2008-01-08 22:39     ` Mariusz Kozlowski
2008-01-08 22:45       ` Randy Dunlap
2008-01-09 16:31         ` Mariusz Kozlowski
2008-01-08 22:50   ` David Miller
2008-01-08 22:56     ` Ingo Molnar
2008-01-08 23:06       ` David Miller
2008-01-09  0:52         ` Ingo Molnar
2008-01-09  1:17 ` Linux 2.6.24-rc7 Willy Tarreau

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=478341E9.9000703@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=bunk@kernel.org \
    --cc=clameter@sgi.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome