linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel locks up after calling kernel_execve()
Date: Wed, 14 Nov 2007 08:43:38 +1100	[thread overview]
Message-ID: <1194990218.28865.1.camel@pasglop> (raw)
In-Reply-To: <20071113212320.85840@gmx.net>


On Tue, 2007-11-13 at 22:23 +0100, Gerhard Pircher wrote:
> > There are ways, sure, which probably involve adding prink's all over
> the
> > place to figure it out... could be some DMA issue for example, could
> be
> > pretty much anything. Have you tried booting an initrd with no disk
> > access ?
> I tried to boot with a ramdisk, but that didn't help much. I still
> locks up
> while loading an init program or after entering some commands in
> sh shell. Looks like the problem is hidden deep in the kernel.

Well, at least the above tells is it's not DMA related.

I don't know of any deeply hidden problem, so you are probably hitting
something else ... if you have disabled idle, then it may be useful to
try instrumenting locks or irq enable/disable.

Also, did you try booting with all kernel debug options enabled ?

Finally, since the problem seem to have started around a specific kernel
version, can you try to bisect the patch that causes it ?

Ben.

  reply	other threads:[~2007-11-13 21:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 21:47 Kernel locks up after calling kernel_execve() Gerhard Pircher
2007-11-08 23:20 ` Benjamin Herrenschmidt
2007-11-09  7:41   ` Gerhard Pircher
2007-11-09  7:50     ` Benjamin Herrenschmidt
2007-11-10 17:11       ` Gerhard Pircher
2007-11-11  3:55         ` Benjamin Herrenschmidt
2007-11-13 21:23           ` Gerhard Pircher
2007-11-13 21:43             ` Benjamin Herrenschmidt [this message]
2007-11-13 22:06               ` Gerhard Pircher
2007-11-13 23:37                 ` Benjamin Herrenschmidt
2007-11-14  9:39                   ` Gerhard Pircher
2007-11-14 10:04                     ` Benjamin Herrenschmidt
2007-11-14 10:15                       ` Gerhard Pircher
2007-11-14 21:54                     ` Paul Mackerras
2007-11-15  8:48                       ` Gerhard Pircher

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=1194990218.28865.1.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gerhard_pircher@gmx.net \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).