From: Pete Clements <clem@clem.clem-digital.net>
To: akpm@osdl.org (Andrew Morton)
Cc: corwin@amber.kn-bremen.de, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: 2.6.0-test10: Badness in local_bh_enable at kernel/softirq.c:121
Date: Wed, 26 Nov 2003 10:27:22 -0500 (EST) [thread overview]
Message-ID: <200311261527.KAA00655@clem.clem-digital.net> (raw)
In-Reply-To: <20031126055258.7526a09d.akpm@osdl.org> from Andrew Morton at "Nov 26, 2003 5:52:58 am"
Quoting Andrew Morton
> Christian Schlittchen <corwin@amber.kn-bremen.de> wrote:
> >
> >
> > When trying to establish a ppp/pppoe connection I get the following
> > and the connection fails:
> >
> > Badness in local_bh_enable at kernel/softirq.c:121
> > Call Trace:
> > [<c011feac>] local_bh_enable+0x8c/0x90
> > [<e096ccae>] ppp_sync_push+0x6e/0x1a0 [ppp_synctty]
> > [<c015cdc0>] __lookup_hash+0x70/0xd0
> > [<e096c651>] ppp_sync_wakeup+0x31/0x70 [ppp_synctty]
> > [<c0207b79>] pty_unthrottle+0x59/0x60
> > [<c02043ba>] check_unthrottle+0x3a/0x40
> > [<c0204463>] n_tty_flush_buffer+0x13/0x60
> > [<c0207f6d>] pty_flush_buffer+0x6d/0x70
> > [<c0200c0e>] do_tty_hangup+0x3fe/0x460
>
> The warning is a pest, and is due to do_tty_hangup() bogusly disabling
> interrupts in the hope that it does something useful. It needs to be fixed
> up.
>
> But it is unrelated to the PPP failure. I'm afraid it is so long since I
> used PPP and pppd that I cannot suggest how you should set about gathering
> extra info on that.
>
What network card? Multi-cards? Is the card detected?
Around 2.5.71 the 3c509 init/detect changed such that the
second card is not detected. Will get the badness when attempting
to bring up ppp/ppoe on a non-existent card.
The 3c509 multi card breakage still exists at test10. I replace the
driver with 2.5.7x version to get my pppoe.
--
Pete Clements
prev parent reply other threads:[~2003-11-26 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 10:42 Christian Schlittchen
2003-11-26 13:52 ` Andrew Morton
2003-11-26 15:27 ` Pete Clements [this message]
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=200311261527.KAA00655@clem.clem-digital.net \
--to=clem@clem.clem-digital.net \
--cc=akpm@osdl.org \
--cc=corwin@amber.kn-bremen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®