All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kernel panic, ip_route_input, 2.6.25-rc6-git2
Date: Sun, 23 Mar 2008 19:17:55 +0200	[thread overview]
Message-ID: <20080323171730.M39052@visp.net.lb> (raw)
In-Reply-To: <20080323.031139.17629653.davem@davemloft.net>

What can i do to increase usability?

On Sun, 23 Mar 2008 03:11:39 -0700 (PDT), David Miller wrote
> From: "Denys Fedoryshchenko" <denys@visp.net.lb>
> Date: Sun, 23 Mar 2008 09:36:38 +0200
> 
> > Recently tested, it crashes also -git6 without lockdep compiled. So it 
seems 
> > actually networking code bug.
> 
> I'm still not so sure.
> 
> The IP is at ip_route_input but the rest of your backtrace
> shows an entirely different code path.
> 
> Nothing in the trace matches up, which severely decreases the
> usability of the debugging information you've provided.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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


  reply	other threads:[~2008-03-23 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23  7:36 kernel panic, ip_route_input, 2.6.25-rc6-git2 (was lockdep... ) Denys Fedoryshchenko
2008-03-23 10:11 ` kernel panic, ip_route_input, 2.6.25-rc6-git2 David Miller
2008-03-23 17:17   ` Denys Fedoryshchenko [this message]
2008-03-23 19:30     ` Arjan van de Ven
2008-03-23 19:59       ` Denys Fedoryshchenko
  -- strict thread matches above, loose matches on Subject: below --
2008-03-21  9:33 Denys Fedoryshchenko

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=20080323171730.M39052@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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.