All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	<yellowdog-devel@lists.terrasoftsolutions.com>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: funny kernel death with ksoftirqd_CPUX taking up almost 100% of cpu?
Date: Wed, 10 Jul 2002 13:18:33 -0400	[thread overview]
Message-ID: <200207101318.33120.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <20020710162403.16035@192.168.4.1>


Well,

I still have to debug that damn OOo 1.0.1 bridge problem so I have to go
back into OOo and gdb (which uses alot of memory) and try again.

If I run into it again, I will let you know.

If so, is there anything debug wise I can do that would help pinpoint the
problem.

Thanks,

Kevin

On July 10, 2002 12:24, Benjamin Herrenschmidt wrote:
> >I just experienced an alarming form of kernel death running a self
> > compiled SMP kernel with HIGHMEM enabled on my dual G4 -1gig machine.
> >
> >The kernel tree used is Ben's 2.4.19-pre10 one rebuilt for SMP support,
> > aec IDE driver and otherwise basically stock.
> >
> >I was debugging in gdb a large program and noticed typing got slower
> > and slower.  I quick check of top showed that ksoftirqd_CPU was taking
> > up almost 100% of the cpu.  I exited out of gdb and killed every
> > process I could think of but the usage of that kernel demaon stayed at
> > near 100%.
>
> BTW. It would be interesting to know if you can ever reproduce it...
>
> Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-07-10 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 16:36 funny kernel death with ksoftirqd_CPUX taking up almost 100% of cpu? Kevin B. Hendricks
2002-07-10 16:11 ` Benjamin Herrenschmidt
2002-07-10 16:24 ` Benjamin Herrenschmidt
2002-07-10 17:18   ` Kevin B. Hendricks [this message]
2002-07-10 17:20 ` Kevin B. Hendricks

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=200207101318.33120.kevin.hendricks@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-devel@lists.terrasoftsolutions.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 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.