From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira <pablo@eurodev.net>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: kernel BUG at kernel/sched.c:2833!
Date: Mon, 21 Nov 2005 18:05:19 +0100 [thread overview]
Message-ID: <4381FE4F.2000107@trash.net> (raw)
In-Reply-To: <4381DDCF.7090609@eurodev.net>
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? architecture? whatever
> that can give me a clue on what's wrong. Send me such info in private if
> you want.
Please don't send information related to the bug in private if not
necessary, the initial bug report is public so other people might
be looking into it or notice that they are affected by the same
problem.
next prev parent reply other threads:[~2005-11-21 17:05 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 [this message]
2005-11-21 21:20 ` Krzysztof Oledzki
2005-11-25 2:52 ` Pablo Neira Ayuso
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=4381FE4F.2000107@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
/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.