All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Deti Fliegl <deti@fliegl.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: again oops: conntrack & 2.6.14-git14
Date: Thu, 01 Dec 2005 11:40:39 +0100	[thread overview]
Message-ID: <438ED327.8030509@trash.net> (raw)
In-Reply-To: <438ED11C.4090508@fliegl.de>

Deti Fliegl wrote:
> Patrick McHardy wrote:
> 
>> The crashes seem to be unrelated to conntrack. They all happen in
>> show_trace+489 because of accesses to 0xffffffff82800000, which
>> is the end of the kernel text mapping on x86_64. Your stress test
>> seems to trigger the softlockup watchdog, which is why you are
>> seeing these. I suggest you resend your report to lkml.
> 
> Then please explain to me why it does only happen when calling
> 'conntrack -L'. The system is 100% stable, there is no defective
> hardware and no weird configuration. Under same conditions I can run 
> kernel compilation jobs in a row...

See above. It seems to trigger the softlockup watchdog for some reason,
which calls show_trace, which is where the crash happens.

  reply	other threads:[~2005-12-01 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 15:34 again oops: conntrack & 2.6.14-git14 Deti Fliegl
2005-11-20 17:43 ` Patrick McHardy
2005-11-23 17:38   ` Deti Fliegl
2005-11-26 14:36     ` Patrick McHardy
2005-11-26 14:57       ` Deti Fliegl
2005-11-26 23:38         ` Patrick McHardy
2005-12-01 10:31           ` Deti Fliegl
2005-12-01 10:40             ` Patrick McHardy [this message]
2005-12-01 10:47               ` Deti Fliegl
2005-12-01 11:09                 ` Patrick McHardy

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=438ED327.8030509@trash.net \
    --to=kaber@trash.net \
    --cc=deti@fliegl.de \
    --cc=netfilter-devel@lists.netfilter.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 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.