public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Thomas Renninger <trenn@suse.de>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Len Brown <len.brown@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ACPI modpost failure in 2.6.23-rc1-git2
Date: Mon, 06 Aug 2007 16:59:02 +0100	[thread overview]
Message-ID: <46B74546.2090501@shadowen.org> (raw)
In-Reply-To: <6bffcb0e0708060453l372e15c2h703ede437b4d8935@mail.gmail.com>

Michal Piotrowski wrote:
> Hi Andy,
> 
> On 06/08/07, Andy Whitcroft <apw@shadowen.org> wrote:
>> Between 2.6.23-rc1-git1 and 2.6.23-rc1-git2 we started getting the
>> following fatal error during modpost on an x86_64 machine:
>>
>>   FATAL: drivers/acpi/video: sizeof(struct acpi_device_id)=20 is not a
>>   modulo of the size of section __mod_acpi_device_table=48.
>>   Fix definition of struct acpi_device_id in mod_devicetable.h
>>   make[1]: *** [__modpost] Error 1
>>
>> This check seems to have been added as part of the following commit:
>>
>>   commit 29b71a1ca74491fab9fed09e9d835d840d042690
>>   Author: Thomas Renninger <trenn@suse.de>
>>   Date:   Mon Jul 23 14:43:51 2007 +0200
>>
>>       ACPI: autoload modules - Create ACPI alias interface
>>
>> Compiler version:
>>   Reading specs from /usr/lib/gcc/i486-linux/3.4.4/specs
>>   Configured with: ../src/configure -v
>>   --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
>>   --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4
>>   --enable-shared --with-system-zlib --enable-nls
>>   --without-included-gettext --program-suffix=-3.4 --enable-__cxa_atexit
>>   --enable-libstdcxx-allocator=mt --enable-clocale=gnu
>>   --enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk
>>   --disable-werror i486-linux
>>   Thread model: posix
>>   gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13sarge1)
>>
>> We are compiling a 64bit kernel on a machine with a pretty old
>> userspace which is 32bit.
>>
>> Let me know if you need more info.
>>
>> -apw
> 
> similar to
> 
> Subject         : modpost bug breaks ia64 cross compilation
> References      : http://lkml.org/lkml/2007/7/27/30
>                   http://lkml.org/lkml/2007/7/27/418
> Last known good : ?
> Submitter       : Jan Dittmer <jdi@l4x.org>
> Caused-By       : Thomas Renninger <trenn@suse.de>
>                   commit 29b71a1ca74491fab9fed09e9d835d840d042690
> Handled-By      : ?
> Patch           : http://lkml.org/lkml/2007/8/2/211
> Status          : patch was suggested
> 
> Please try this patch http://lkml.org/lkml/2007/8/2/211

Will do.  That is vile though.

It feels like we should be generating this information in the kernel
build and extracting it from the built kernel.

-apw

  reply	other threads:[~2007-08-06 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 11:43 ACPI modpost failure in 2.6.23-rc1-git2 Andy Whitcroft
2007-08-06 11:53 ` Michal Piotrowski
2007-08-06 15:59   ` Andy Whitcroft [this message]
2007-08-07 12:14     ` 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=46B74546.2090501@shadowen.org \
    --to=apw@shadowen.org \
    --cc=kay.sievers@vrfy.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=trenn@suse.de \
    /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