public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: Can't boot 2.6.30 powerpc kernel under qemu.
Date: Sun, 28 Jun 2009 10:33:09 +0800	[thread overview]
Message-ID: <200906281033.09842.jk@ozlabs.org> (raw)

Hi Rob,

> I bisected the problem in the linux kernel repository, and wound up
> here:
>
> 60ee031940c1b09c137b617a8829e2f081961fe0 is first bad commit
> commit 60ee031940c1b09c137b617a8829e2f081961fe0
> Author: Jeremy Kerr <jk@ozlabs.org>
> Date:   Tue Feb 17 11:44:14 2009 +1100
>
>     powerpc/spufs: Use correct return value for spu_handle_mm_fault

I think it's very unlikely that this commit would be causing the
problem, as qemu doesn't have any SPEs (they're specific to the Cell
architecture), which would be required to hit this code. Also, you're 
not compiling with CONFIG_SPU_BASE, so the file that this changed 
shouldn't even be built.

Perhaps try the bisect again?

> P.S.  Is there a powerpc list I should have cc:'d this to? 
> vger.kernel.org just has kvm-ppc, no other "ppc" or "power".  Google
> suggests ozlabs, but their mailing lists only see to have cell, which
> this isn't...

linuxppc-dev@lists.ozlabs.org is the one you want for this:

 https://lists.ozlabs.org/listinfo/linuxppc-dev

Cheers,


Jeremy


             reply	other threads:[~2009-06-28  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28  2:33 Jeremy Kerr [this message]
2009-06-29 23:34 ` Can't boot 2.6.30 powerpc kernel under qemu Rob Landley
2009-06-30  0:23   ` Tony Breeds
2009-06-30  0:24   ` Michael Ellerman
2009-06-30 10:50     ` Benjamin Herrenschmidt
2009-06-30 14:04       ` Michael Ellerman
2009-06-30 10:24   ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2009-06-27 23:08 Rob Landley

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=200906281033.09842.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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