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: possible lockdep crash
Date: Fri, 21 Mar 2008 17:23:30 +0200 [thread overview]
Message-ID: <20080321152045.M11363@visp.net.lb> (raw)
In-Reply-To: <20080321.040408.153242166.davem@davemloft.net>
I have very strange lockups on this machine, and i tried to catch them. But
seems it doesn't help me, till now lockdep catch only ifb false-positive.
I will try to compile and run now without lockdep.
On Fri, 21 Mar 2008 04:04:08 -0700 (PDT), David Miller wrote
> From: "Denys Fedoryshchenko" <denys@visp.net.lb>
> Date: Fri, 21 Mar 2008 12:54:50 +0200
>
> > Let me know if i can improve output to help debugging.
> > If possible it must be minimal risk to hang, cause router is in very
> > difficult to reach area.
>
> Can you disable lockdep and see if the problem persists?
>
> It's killing your routing performance anyways, I have no
> idea why you have it enabled.
> --
> 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.
next prev parent reply other threads:[~2008-03-21 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 9:33 kernel panic, ip_route_input, 2.6.25-rc6-git2 Denys Fedoryshchenko
2008-03-21 10:35 ` possible lockdep crash (was Re: kernel panic, ip_route_input, 2.6.25-rc6-git2) David Miller
2008-03-21 10:54 ` Denys Fedoryshchenko
2008-03-21 11:04 ` possible lockdep crash David Miller
2008-03-21 15:23 ` Denys Fedoryshchenko [this message]
2008-03-22 0:46 ` Denys Fedoryshchenko
2008-03-21 10:59 ` possible lockdep crash (was Re: kernel panic, ip_route_input, 2.6.25-rc6-git2) 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=20080321152045.M11363@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 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).