netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Denys" <nuclearcat@nuclearcat.com>
To: Andrew Morton <akpm@linux-foundation.org>, netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Bugme-new] [Bug 10324] New: kernel panic ip_route_input
Date: Wed, 26 Mar 2008 01:06:58 +0200	[thread overview]
Message-ID: <20080325225844.M82705@nuclearcat.com> (raw)
In-Reply-To: <20080325130302.d3f6757c.akpm@linux-foundation.org>

I upload whole netconsole file at
http://www.nuclearcat.com/files/ip_route_input_crash.txt 
There is two crashes.



On Tue, 25 Mar 2008 13:03:02 -0700, Andrew Morton wrote
> (switched to email.  Please respond via emailed reply-to-all, not 
> via the bugzilla web interface).
> 
> On Tue, 25 Mar 2008 12:48:37 -0700 (PDT)
> bugme-daemon@bugzilla.kernel.org wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=10324
> > 
> >            Summary: kernel panic ip_route_input
> >            Product: Networking
> >            Version: 2.5
> >      KernelVersion: 2.6.25-rc6-git6
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: IPV4
> >         AssignedTo: shemminger@linux-foundation.org
> >         ReportedBy: nuclearcat@nuclearcat.com
> > 
> > 
> > Latest working kernel version: 2.6.24.x
> > Earliest failing kernel version: 2.6.25-rc6
> 
> A post-2.6.24 regression.
> 
> > Distribution: Custom
> > Hardware Environment: Dual CPU, e100 + e1000
> > Software Environment: Custom build. FIB_TRIE enabled
> > Problem Description: Kernel panic after few seconds running network on heavy
> > traffic (around 350 Mbps). 
> > 
> > Steps to reproduce: It is complicated configuration. I can provide whole image
> > of system, around 128MB (it is semi-embedded), but it will need at least few
> > traffic generators similar to mine. So it is difficult to reproduce. I can
> > apply any patches required, but highly prefferable if they dont make server
> > unreachable. I have panic and oops autoreboot sysctl options, nmi-watchdog and
> > software watchdog enabled.
> > I think it is critical to fix this bug before releasing 2.6.25.
> > 
> > Here is latest message with panic:
> > CONFIG_DEBUG_RODATA, 4K stacks, Frame pointers, CONFIG_DEBUG_STACKOVERFLOW - 
> > enabled.
> > 
> > It reboots recently after bringing up networking. Sometimes even not reaching 
> > place where i am loading netconsole.
> > 
> > Always in ip_route_input. This is 2.6.25-rc6-git6, 2 panic's. They are easy 
> > to reproduce, but i cannot do bisect, cause this machine dont have power 
> > switch and in difficult to reach area.
> >
> 
> I've snipped the log output - it was such a wordwrapped mess :(
> 
> Can you please resend it in a reply-to-all to this email, after ensuring
> that it won't be wordwrapped?
> 
> Thanks.


--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.


  reply	other threads:[~2008-03-25 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10324-10286@http.bugzilla.kernel.org/>
2008-03-25 20:03 ` [Bugme-new] [Bug 10324] New: kernel panic ip_route_input Andrew Morton
2008-03-25 23:06   ` Denys [this message]
2008-03-25 23:12   ` Denys
2008-03-25 23:45     ` David Miller
2008-03-25 23:49     ` Stephen Hemminger
2008-03-26  8:20       ` Denys

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=20080325225844.M82705@nuclearcat.com \
    --to=nuclearcat@nuclearcat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@sisk.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 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).