From: Pablo Neira Ayuso <pablo@eurodev.net>
To: Krzysztof Oledzki <olenf@ans.pl>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: kernel BUG at kernel/sched.c:2833!
Date: Fri, 25 Nov 2005 03:52:44 +0100 [thread overview]
Message-ID: <43867C7C.8070002@eurodev.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511212208550.13610@bizon.gios.gov.pl>
Hi,
Krzysztof Oledzki wrote:
> On Mon, 21 Nov 2005, Pablo Neira wrote:
>
>> Krzysztof Oledzki wrote:
>>
>>>> I can't reproduce that problem that you're reporting. I don't see how
>>>> the ctnetlink code can trigger that at the moment :(
>>>
>>> What information should I provide to help tracking this bug?
>>
>> Any extra patch applied to your vanilla kernel?
>
> From pom-ng:
> ROUTE TARPIT TTL iprange ipv4options policy comment time set u32 random
> unclean
A lot of patches from pom-ng. I tried with a vanilla 2.6.14.2 and I'm
not able to reproduce the problem, always with preemption and SMP
enabled but nothing.
Could you try to reproduce it without the extra patches? That will help
to know if any of those are spotting that error.
BTW, iprange is already in mainline.
--
Pablo
next prev parent reply other threads:[~2005-11-25 2:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 9:50 kernel BUG at kernel/sched.c:2833! Krzysztof Oledzki
2005-11-14 12:27 ` Pablo Neira
2005-11-16 21:16 ` Krzysztof Oledzki
2005-11-17 0:36 ` Pablo Neira
2005-11-17 15:11 ` Harald Welte
2005-11-18 3:19 ` Pablo Neira
2005-11-18 3:25 ` Pablo Neira
2005-11-21 9:48 ` Krzysztof Oledzki
2005-11-18 8:37 ` Harald Welte
2005-11-17 22:04 ` Krzysztof Oledzki
2005-11-21 14:24 ` Pablo Neira
2005-11-21 14:42 ` Krzysztof Oledzki
2005-11-21 14:46 ` Pablo Neira
2005-11-21 17:05 ` Patrick McHardy
2005-11-21 21:20 ` Krzysztof Oledzki
2005-11-25 2:52 ` Pablo Neira Ayuso [this message]
2005-11-25 11:43 ` Krzysztof Oledzki
2005-11-22 11:40 ` Krzysztof Oledzki
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=43867C7C.8070002@eurodev.net \
--to=pablo@eurodev.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=olenf@ans.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.