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: Wed, 14 Nov 2007 11:15:24 +0100 [thread overview]
Message-ID: <20071114101524.297880@gmx.net> (raw)
In-Reply-To: <1195034697.28865.34.camel@pasglop>
-------- Original-Nachricht --------
> Datum: Wed, 14 Nov 2007 21:04:57 +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 Wed, 2007-11-14 at 10:39 +0100, Gerhard Pircher wrote:
> > Yeah, the northbridge hates the M bit! Thus the AmigaOne platform code
> > masks out the CPU_FTR_NEED_COHERENT flag and disables the L2 cache
> > prefetch engines (I don't care about the performance loss).
> > I couldn't find any other code that sets the M bit, except for huge
> > TLB
> > page support, but isn't that only for PPC64?
>
> Right, it's only 64 bits. You've double checked nothing broke the M bit
> thing ? In which case, I don't know what else...
Yes, I did. Otherwise the machine dies much earlier in the boot process.
Gerhard
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
next prev parent reply other threads:[~2007-11-14 10:15 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
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 [this message]
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=20071114101524.297880@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=benh@kernel.crashing.org \
--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 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.