From: "Gerhard Pircher" <gerhard_pircher@gmx•net>
To: benh@kernel•crashing.org
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Kernel locks up after calling kernel_execve()
Date: Fri, 09 Nov 2007 08:41:55 +0100 [thread overview]
Message-ID: <20071109074155.266120@gmx.net> (raw)
In-Reply-To: <1194564017.6561.21.camel@pasglop>
-------- Original-Nachricht --------
> Datum: Fri, 09 Nov 2007 10:20:17 +1100
> Von: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> An: Gerhard Pircher <gerhard_pircher@gmx•net>
> CC: linuxppc-dev@ozlabs•org
> Betreff: Re: Kernel locks up after calling kernel_execve()
>
> On Thu, 2007-11-08 at 22:47 +0100, Gerhard Pircher wrote:
> > Hi,
> >
> > I tested my patches for the AmigaOne platform with the lastest
> > 2.6.24-rc2 kernel snapshot. The kernel runs through all initcalls, but
> > locks up completely after calling INIT (/sbin/init) by kernel_execve().
> > Thus I couldn't capture any kernel oops or panic output. Also the magic
> > sysrq key doesn't work. Enabling debug code for soft lockups and
> > spinlock debugging didn't reveal any information.
> > I'm not sure, but I think it is the same problem I had with all kernels
> > >= 2.6.17. All of these kernels lock up shortly before or right at
> > calling the init program (resp. as soon as the kernel forks some kernel
> > theads).
> > Any suggestions on how to track down this problem?
>
> You don't have a HW debugger or anything like that ?
>
> Ben.
Unfortunately, no. A BDI2000 is too costly for me.
I tried to use /bin/sh as init program and was able to enter a command,
but then the machine locked up, too.
Could that be a problem with a CPU sleeping/idle code?
Gerhard
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
next prev parent reply other threads:[~2007-11-09 7:41 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 [this message]
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
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=20071109074155.266120@gmx.net \
--to=gerhard_pircher@gmx$(echo .)net \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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