linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geoff Levand <geoff@infradead.org>
To: Phileas Fogg <phileas-fogg@mail.ru>,
	Michael Ellerman <michael@ellerman.id.au>
Cc: cbe-oss-dev@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: PS3 platform is broken on Linux 3.7.0
Date: Tue, 12 Feb 2013 23:32:59 -0800	[thread overview]
Message-ID: <1360740779.28936.20.camel@clam> (raw)
In-Reply-To: <1355488506.55692113@f147.mail.ru>

Hi,

On Fri, 2012-12-14 at 16:35 +0400, Phileas Fogg wrote:
> I wanted to bring to your attention the fact that the PS3 platform is broken on Linux 3.7.0.

> So i cloned the Linux powerpc GIT repository and tried to find out which commits broke the PS3 platform.

> ---------------------------------------------------------------------------------------------
> 
> commit 407821a34fce89b4f0b031dbab5cec7d059f46bc
> Author: Michael Ellerman <michael@ellerman.id.au>
> Date:   Fri Sep 7 15:31:44 2012 +0000
> 
>     powerpc: Initialise paca.data_offset with poison

I did a little more work on this, and it seems the change below
will fix the problem introduced by Michael's change.  I can only
guess we need to use udbg_printf() here.  I'll look at it some more
as I have time.

-Geoff

diff --git a/arch/powerpc/kernel/paca.c b/arch/powerpc/kernel/paca.c
index 5c56834..6b4f613 100644
--- a/arch/powerpc/kernel/paca.c
+++ b/arch/powerpc/kernel/paca.c
@@ -184,8 +185,8 @@ void __init allocate_pacas(void)
 	paca = __va(memblock_alloc_base(paca_size, PAGE_SIZE, limit));
 	memset(paca, 0, paca_size);
 
-	printk(KERN_DEBUG "Allocated %u bytes for %d pacas at %p\n",
-		paca_size, nr_cpu_ids, paca);
+//	printk(KERN_DEBUG "Allocated %u bytes for %d pacas at %p\n",
+//		paca_size, nr_cpu_ids, paca);
 
 	allocate_lppacas(nr_cpu_ids, limit);
 

> 

  parent reply	other threads:[~2013-02-13  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 12:35 PS3 platform is broken on Linux 3.7.0 Phileas Fogg
2012-12-19 21:53 ` Benjamin Herrenschmidt
2013-01-12  2:12   ` Geoff Levand
2013-01-14 23:37     ` Geoff Levand
2013-02-10  8:59       ` Re[2]: " Phileas Fogg
2013-02-10  9:16         ` Re[3]: " Phileas Fogg
2013-02-10 16:11           ` Aneesh Kumar K.V
2013-02-11 10:26             ` Aneesh Kumar K.V
2013-02-11 16:57               ` Re[5]: " Phileas Fogg
2013-02-12  1:11               ` Re[3]: " Geoff Levand
2013-02-11 20:56         ` Re[2]: " Geoff Levand
2013-02-10 11:45   ` Phileas Fogg
2013-02-10 12:17     ` Re[3]: " Phileas Fogg
2013-02-10 15:46       ` Aneesh Kumar K.V
2013-02-10 17:51         ` Re[5]: " Phileas Fogg
2013-02-11  3:39           ` Michael Ellerman
2013-02-13  7:32 ` Geoff Levand [this message]
2013-02-13 22:37   ` Michael Ellerman

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=1360740779.28936.20.camel@clam \
    --to=geoff@infradead.org \
    --cc=cbe-oss-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=phileas-fogg@mail.ru \
    /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).