[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1fy2rxpje.fsf@ebiederm.dsl.xmission.com>
Date: Fri, 10 Aug 2007 11:33:41 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Gabriel C <nix.or.die@...glemail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Netdev <netdev@...r.kernel.org>,
coreteam@...filter.org
Subject: Re: 2.6.23-rc2-mm2
Gabriel C <nix.or.die@...glemail.com> writes:
> Michal Piotrowski wrote:
>> Andrew Morton pisze:
>>>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc2/2.6.23-rc2-mm2/
>>>
>>
>> Yet another sysctl table check failed
>>
>> [ 88.949055] Netfilter messages via NETLINK v0.30.
>> [ 89.485399] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
>> [ 89.491892] sysctl table check failed:
> /net/netfilter/nf_conntrack_generic_timeout .3.19.13 Missing strategy
>> [ 89.558178] xt_state: Unknown symbol nf_conntrack_untracked
>> [ 89.563942] xt_state: Unknown symbol nf_ct_l3proto_module_put
>> [ 89.569870] xt_state: Unknown symbol nf_ct_l3proto_try_module_get
>> [ 90.852319] NET: Registered protocol family 17
>>
>
> And maybe this ?
Could be.
sysctl table check failure looks legitimate.
At a quick skim I can't tell for certain if failure to register the
sysctl table will keep the module from loading but it might.
It looks like another canidate on the pile of kill the broken
binary sysctl.
Eric
-
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