From: Brad Laue <brad@brad-x.com>
To: linux-kernel@vger.kernel.org
Subject: Re: badness in kernel/softirq.c
Date: Sat, 20 Mar 2004 11:41:50 -0500 [thread overview]
Message-ID: <1079800910.13796.7.camel@Discovery.brad-x.com> (raw)
In-Reply-To: <1079800804.13796.5.camel@Discovery.brad-x.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Sat, 2004-03-20 at 11:40, Brad Laue wrote:
> This is a followup to my earlier mail 'ksoftirqd using mysteriously high
> amounts of CPU time'. After working briefly with Andrew Morton on the
> issue we seem to have identified the 'pppoe' userspace program as the
> culprit for that issue.
>
> After some playing with kernel options I switched my PPPoE connection
> options from asynctty to synctty, and observed almost no usage of
> ksoftirqd/0 at all, as it should be.
>
> However, the pppoe process maintains an extreme amount of CPU
> utilization, cutting off the machines ability to send and receive at its
> fastest possible rate. Additionally the attached error fills dmesg after
> a couple of days (vanilla 2.6.3 kernel).
>
> I'm hoping the PPP stuff in the kernel is well enough maintained that a
> problem/solution can be identified..
>
> Thanks in advance!
>
> Brad
I apparently need to be reminded to actually attach attachments. :-)
[-- Attachment #2: dmesg.log --]
[-- Type: text/plain, Size: 1224 bytes --]
Badness in local_bh_enable at kernel/softirq.c:126
Call Trace:
[<c0121d46>] local_bh_enable+0x86/0x90
[<d087ac3b>] ppp_sync_push+0x5b/0x170 [ppp_synctty]
[<d087a63d>] ppp_sync_wakeup+0x2d/0x60 [ppp_synctty]
[<c024363a>] do_tty_hangup+0x3ea/0x460
[<c0244bcd>] release_dev+0x62d/0x660
[<c0142d53>] unmap_page_range+0x43/0x70
[<c0168b62>] dput+0x22/0x210
[<c0244faa>] tty_release+0x2a/0x60
[<c0152ec0>] __fput+0x100/0x120
[<c0151529>] filp_close+0x59/0x90
[<c011f594>] put_files_struct+0x54/0xc0
[<c01201fd>] do_exit+0x18d/0x410
[<c012051a>] do_group_exit+0x3a/0xb0
[<c0109387>] syscall_call+0x7/0xb
Badness in local_bh_enable at kernel/softirq.c:126
Call Trace:
[<c0121d46>] local_bh_enable+0x86/0x90
[<d087ac3b>] ppp_sync_push+0x5b/0x170 [ppp_synctty]
[<d087a63d>] ppp_sync_wakeup+0x2d/0x60 [ppp_synctty]
[<c024363a>] do_tty_hangup+0x3ea/0x460
[<c0244bcd>] release_dev+0x62d/0x660
[<c0142d53>] unmap_page_range+0x43/0x70
[<c0168b62>] dput+0x22/0x210
[<c0244faa>] tty_release+0x2a/0x60
[<c0152ec0>] __fput+0x100/0x120
[<c0151529>] filp_close+0x59/0x90
[<c011f594>] put_files_struct+0x54/0xc0
[<c01201fd>] do_exit+0x18d/0x410
[<c012051a>] do_group_exit+0x3a/0xb0
[<c0109387>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2004-03-20 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 16:40 Brad Laue
2004-03-20 16:41 ` Brad Laue [this message]
2004-03-20 16:51 ` Ralf Hildebrandt
2004-03-20 17:50 ` Brad Laue
2004-03-20 21:53 ` Andrew Morton
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=1079800910.13796.7.camel@Discovery.brad-x.com \
--to=brad@brad-x.com \
--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
all inboxes | Powered by JetHome®