From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: BUG? locking issue(networking?) with latest git
Date: Thu, 4 Sep 2008 07:21:56 +0000 [thread overview]
Message-ID: <20080904072155.GA4691@ff.dom.local> (raw)
In-Reply-To: <200809031422.24883.denys@visp.net.lb>
On 03-09-2008 13:22, Denys Fedoryshchenko wrote:
> I am getting strange lockup, all operations (tc, ifconfig,pppd) after few days running pppoe-server.
>
> Programgs getting blocked very strange way, i am not able to kill them even.
> Softlockup detection enabled, lock dependencies (except lock dependency engine debugging),
> RT mutexes and deadlock detection enabled too.
>
> I notice this bug few weeks ago, even before latest patches, and seems it still remains.
>
Do you mean this didn't happen with some 2.6.27-rc's? (There was quite
substantial change in ppp_generic with lock_kernel() in 2.6.27-rc1.)
>
> Here is result of SysRQ +T:
>
Alas it shows only some tasks waiting for locks. Maybe it's enough for
someone with better ppp knowledge, but unless there is such a response
I guess you should better try with PROVE_LOCKING turned on yet.
Jarek P.
next prev parent reply other threads:[~2008-09-04 7:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 11:22 BUG? locking issue(networking?) with latest git Denys Fedoryshchenko
2008-09-04 7:21 ` Jarek Poplawski [this message]
2008-09-04 9:03 ` Denys Fedoryshchenko
2008-09-04 9:38 ` Jarek Poplawski
2008-09-04 9:46 ` Denys Fedoryshchenko
2008-09-04 10:02 ` Jarek Poplawski
2008-09-04 10:11 ` Denys Fedoryshchenko
2008-09-04 14:14 ` Denys Fedoryshchenko
2008-09-04 21:48 ` Jarek Poplawski
2008-09-04 22:43 ` Denys Fedoryshchenko
2008-09-05 8:29 ` [PATCH] pkt_sched: Fix qdisc state in net_tx_action() Jarek Poplawski
2008-09-05 10:26 ` Herbert Xu
2008-09-05 22:41 ` Denys Fedoryshchenko
2008-09-06 12:02 ` Jarek Poplawski
2008-09-08 1:41 ` David Miller
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=20080904072155.GA4691@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--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.