From: Jarek Poplawski <jarkao2@o2.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org,
"bugme-daemon\@kernel-bugs\.osdl\.org"
<bugme-daemon@bugzilla.kernel.org>,
jura@netams.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [Bugme-new] [Bug 8132] New: pptp server lockup in ppp_asynctty_receive()
Date: Thu, 8 Mar 2007 09:45:39 +0100 [thread overview]
Message-ID: <20070308084539.GA2423@ff.dom.local> (raw)
In-Reply-To: <20070305151331.3cdd98dd.akpm@linux-foundation.org>
On 06-03-2007 00:13, Andrew Morton wrote:
> On Mon, 5 Mar 2007 14:26:30 -0800
> bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=8132
>>
>> Summary: pptp server lockup in ppp_asynctty_receive()
>> Kernel Version: 2.6.20
>> Status: NEW
>> Severity: high
>> Owner: jgarzik@pobox.com
>> Submitter: jura@netams.com
>> CC: jura@netams.com
>>
>>
>> Already several kernel releases i've expirienced different lockups of vpn
>> (pptp) server.
>> There is more then 200 ppp connections sometimes.
>> With kernel debug i was able to retrive next information:
Could this be done with:
CONFIG_PROVE_LOCKING = y
CONFIG_4KSTACKS = n
and, if possible, to send the first full lockdep error
message with some lines before it? It would be nice to
try to be more exact when hand writing, too.
Regards,
Jarek P.
next prev parent reply other threads:[~2007-03-08 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703052226.l25MQUk4011469@fire-2.osdl.org>
2007-03-05 23:13 ` [Bugme-new] [Bug 8132] New: pptp server lockup in ppp_asynctty_receive() Andrew Morton
2007-03-08 8:45 ` Jarek Poplawski [this message]
2007-03-09 8:40 ` Yuriy N. Shkandybin
2007-03-09 10:21 ` Jarek Poplawski
2007-03-09 13:10 ` Jarek Poplawski
2007-03-19 7:49 ` Yuriy N. Shkandybin
2007-03-28 8:19 ` [PATCH] ppp_generic: lockdep warning Re: [Bug 8132] New: pptp server lockup Jarek Poplawski
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=20070308084539.GA2423@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jura@netams.com \
--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).