From: "Nicolás Lichtmaier" <niqueco@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Bug in 2.6.1's PPP? Stack trace included.
Date: Tue, 03 Feb 2004 23:26:05 -0300 [thread overview]
Message-ID: <4020583D.7050605@hotmail.com> (raw)
Trying to build a tunnel with ppp+ssh I've been getting ESRCH whith
ping. And these kernel messages:
Badness in local_bh_enable at kernel/softirq.c:121
Call Trace:
[<c01206e4>] local_bh_enable+0x70/0x72
[<d009baac>] ppp_async_push+0x88/0x151 [ppp_async]
[<d009b402>] ppp_asynctty_wakeup+0x2d/0x5e [ppp_async]
[<c01c189f>] pty_unthrottle+0x58/0x5a
[<c01be685>] check_unthrottle+0x39/0x3b
[<c01be6f6>] n_tty_flush_buffer+0x13/0x55
[<c01c1c5a>] pty_flush_buffer+0x66/0x68
[<c01bb5a1>] do_tty_hangup+0x3a3/0x3f0
[<c01bc861>] release_dev+0x665/0x691
[<c013ce45>] zap_pmd_range+0x47/0x61
[<c013cea2>] unmap_page_range+0x43/0x69
[<c01bcbd5>] tty_release+0xf/0x15
[<c014b1f6>] __fput+0xdd/0xef
[<c0149b6f>] filp_close+0x59/0x86
[<c011e360>] put_files_struct+0x84/0xe9
[<c011eee4>] do_exit+0x14f/0x32f
[<c011f145>] do_group_exit+0x34/0x72
[<c0108f75>] sysenter_past_esp+0x52/0x71
Badness in local_bh_enable at kernel/softirq.c:121
I hope it helps.
Thanks.
reply other threads:[~2004-02-04 2:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4020583D.7050605@hotmail.com \
--to=niqueco@hotmail.com \
--cc=jnl@synapsis-sa.com.ar \
--cc=linux-kernel@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