All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: commit f6be75d03c88 broke qemu-system-mips64.
Date: Tue, 07 Sep 2010 09:29:28 -0700	[thread overview]
Message-ID: <4C866868.6060606@caviumnetworks.com> (raw)
In-Reply-To: <201009041754.28716.rob@landley.net>

On 09/04/2010 03:54 PM, Rob Landley wrote:
> linux-2.6.33 booted mips64 to a shell prompt, and 2.6.34 didn't.  The above
> commit is the one that broke it, and if you revert it the result boots again.
>
> To try it yourself, download this mips64 system image:
>
>    http://impactlinux.com/aboriginal/downloads/binaries/system-image-mips64.tar.bz2
>
> Extract it, cd into it, and "./run-emulator.sh".
>
> You'll need QEMU installed.  Note that Ubuntu's qemu package is actually
> kqemu, and doesn't support any non-x86 targets.  You need to install
> "qemu-kvm-extras" to get _actual_ qemu.  I don't know why they broke this.
>
> Once you've confirmed it used to work, replace the zImage-mips64 file with a
> vmlinux built using the attached .config and ./run-emulator.sh again.  If you
> build f6be75d03c88 it fails, but f6be75d03c88^1 works.  If you build 2.6.35
> but revert the f6be75d03c88 patch (all one line of it), it works.  If you don't
> revert it, v2.6.35 is still broken.
>
> Rob

Has anybody tried it on a real 64-bit Malta?  Perhaps the emulator is 
broken.

Rob, did you try to debug it at all?  Where is it going off into the weeds?

David Daney

  reply	other threads:[~2010-09-07 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 22:54 commit f6be75d03c88 broke qemu-system-mips64 Rob Landley
2010-09-07 16:29 ` David Daney [this message]
2010-09-08  7:42   ` Ralf Baechle

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=4C866868.6060606@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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 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.