From: Gabriel C <nix.or.die@googlemail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.23-rc3-mm1
Date: Wed, 22 Aug 2007 19:01:50 +0200 [thread overview]
Message-ID: <46CC6BFE.3020400@googlemail.com> (raw)
In-Reply-To: <20070822090953.78a3d90c.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 22 Aug 2007 15:33:27 +0200 Gabriel C <nix.or.die@googlemail.com> wrote:
>
>> ...
>>
>> CC arch/i386/boot/cpu.o
>> CC arch/i386/boot/cpucheck.o
>> WARNING: "div64_64" [net/netfilter/xt_connbytes.ko] has no CRC!
>> CC arch/i386/boot/edd.o
>> AS arch/i386/boot/header.o
>> CC arch/i386/boot/main.o
>
> Yeah, I get that too. I was hoping that someone who had a vague clue
> about what's causing it might fix it also.
Hmm.. I don't know ( added netdev to Cc ) I got one more :
...
WARNING: "div64_64" [net/ipv4/tcp_cubic.ko] has no CRC!
...
Btw when modprobing these the kernel gets tainted
...
[ 5498.536055] nf_conntrack version 0.5.0 (10240 buckets, 40960 max)
[ 5498.554844] xt_connbytes: no version for "div64_64" found: kernel tainted.
...
>
>> ...
>>
>> config : http://194.231.229.228/kernel/mm/2.6.23-rc3-mm1/config
>> build-log: http://194.231.229.228/kernel/mm/2.6.23-rc3-mm1/build-log
>>
next prev parent reply other threads:[~2007-08-22 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070822020648.5ea3a612.akpm@linux-foundation.org>
2007-08-22 15:30 ` net/ipv4/fib_trie.c - compile error (Re: 2.6.23-rc3-mm1) Gabriel C
2007-08-22 15:41 ` Adrian Bunk
2007-08-22 16:32 ` Gabriel C
2007-08-22 17:03 ` Paul E. McKenney
2007-08-27 6:36 ` Jarek Poplawski
2007-08-27 16:23 ` Paul E. McKenney
[not found] ` <46CC3B27.10604@googlemail.com>
[not found] ` <20070822090953.78a3d90c.akpm@linux-foundation.org>
2007-08-22 17:01 ` Gabriel C [this message]
2007-08-22 17:10 ` drivers/net/ppp_generic - __modpost error ( Re: 2.6.23-rc3-mm1 ) Gabriel C
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=46CC6BFE.3020400@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).