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


Hi,

If it matters at all the kernel was compiled with Franz's gcc 3.1-1a rpm
from his site on PenguinPPC.org

I have been tracking a problem with how structures that are inheritied
seemed to be aligned differntly then under gcc 2.95.4.

Kevin

On July 10, 2002 12:36, Kevin B. Hendricks wrote:
> Hi,
>
> 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%.
>
> It became so bad I could barely perform a straight shutdown (I had to
> hit return numerous times to allow the other cpu to get some time to
> handle the shutdown.
>
> There were lots of messages like the following as I tried to shutdown:
>
> Jul 10 11:56:24 localhost kernel: Serial port locked ON by debugger !
> Jul 10 11:56:24 localhost kernel:
> Jul 10 11:56:24 localhost kernel: wait_on_irq, CPU 0:
> Jul 10 11:56:24 localhost kernel: irq:  -1 [0 0]
> Jul 10 11:56:24 localhost kernel: bh:   0 [0 0]
> Jul 10 11:57:13 localhost kernel:
> Jul 10 11:57:13 localhost kernel: wait_on_irq, CPU 0:
> Jul 10 11:57:13 localhost kernel: irq:  -1 [0 0]
> Jul 10 11:57:13 localhost kernel: bh:   0 [0 0]
> Jul 10 11:57:31 localhost kernel:
> Jul 10 11:57:31 localhost kernel: wait_on_irq, CPU 0:
> Jul 10 11:57:31 localhost kernel: irq:  -1 [0 0]
> Jul 10 11:57:31 localhost kernel: bh:   0 [0 0]
> Jul 10 11:57:36 localhost kernel:
> Jul 10 11:57:36 localhost kernel: wait_on_irq, CPU 0:
> Jul 10 11:57:36 localhost kernel: irq:  -1 [0 0]
> Jul 10 11:57:36 localhost kernel: bh:   0 [0 0]
> Jul 10 11:57:37 localhost kernel:
> ...
>
> But I was able to finally get it to shutdown properly and it seems to
> have rebooted fine.
>
> Anyone with any ideas of what just hit me?  Anything I should do next
> time it happens (the were no relevant message in the /var/log/messages/
> that might indicate a problem excpet for the lines I quoted above.
>
> Any help would be greatly appreciated.
>
> Thanks,
>
> Kevin
>
>
> _______________________________________________
> yellowdog-devel mailing list
> yellowdog-devel@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-devel


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

      parent reply	other threads:[~2002-07-10 17:20 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
2002-07-10 17:20 ` Kevin B. Hendricks [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=200207101320.43818.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 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).