All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Aboriginal Linux <aboriginal@lists.landley.net>,
	linux-kernel@vger.kernel.org, davem@davemloft.net, tytso@mit.edu,
	sparclinux@vger.kernel.org
Subject: Sparc-32 doesn't work in 3.1.
Date: Sat, 12 Nov 2011 17:22:34 +0000	[thread overview]
Message-ID: <4EBEAB5A.5020809@landley.net> (raw)

Still trying to ship an Aboriginal Linux release with the 3.1 kernel,
but the sparc target broke, as in QEMU's OpenBios goes:

  Boot time fixup v1.6. 4/Mar/98 Jakub Jelinek (jj@ultra.linux.cz).
  Patching kernel for srmmu[Fujitsu TurboSparc]/iommu
  Fixup i f029ddfc doesn't refer to a valid instruction at
  f00de648[95eea000]
  halt, power off

And doesn't even boot Linux.  A sparc-objdump -a on vmlinux says that
chunk has:

f00de63c:       84 0b 60 ff     and  %o5, 0xff, %g2
f00de640:       91 32 20 10     srl  %o0, 0x10, %o0
f00de644:       85 28 a0 08     sll  %g2, 8, %g2
f00de648:       98 0a 20 ff     and  %o0, 0xff, %o4
f00de64c:       03 00 00 3f     sethi  %hi(0xfc00), %g1
f00de650:       82 10 63 00     or  %g1, 0x300, %g1     ! ff00
<cputypvallen+0xfef4>
f00de654:       90 0a 00 01     and  %o0, %g1, %o0

Which means nothing to me.

I bisected it to this:

commit 9933fc0ac1ac14b795819cd63d05ea92112f690a
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Mon Aug 1 08:45:02 2011 -0400

    ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree()

    Introduce new helper functions which try kmalloc, and then fall back
   to vmalloc if necessary, and use them for allocating and deallocating
    s_flex_groups.

    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

The commit before that builds fine, this one doesn't.

I think it's triggering bad behavior in arch/sparc/mm/btfixup.c (at
least that's where the "valid instruction" error message comes from),
but I have no idea what this file is doing, and it was last touched in
2008.  (I'm building with gcc 4.2.1 and binutils 2.17, both of which
were last touched around 2006, so that's not new either...)

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Aboriginal Linux <aboriginal@lists.landley.net>,
	linux-kernel@vger.kernel.org, davem@davemloft.net, tytso@mit.edu,
	sparclinux@vger.kernel.org
Subject: Sparc-32 doesn't work in 3.1.
Date: Sat, 12 Nov 2011 11:22:34 -0600	[thread overview]
Message-ID: <4EBEAB5A.5020809@landley.net> (raw)

Still trying to ship an Aboriginal Linux release with the 3.1 kernel,
but the sparc target broke, as in QEMU's OpenBios goes:

  Boot time fixup v1.6. 4/Mar/98 Jakub Jelinek (jj@ultra.linux.cz).
  Patching kernel for srmmu[Fujitsu TurboSparc]/iommu
  Fixup i f029ddfc doesn't refer to a valid instruction at
  f00de648[95eea000]
  halt, power off

And doesn't even boot Linux.  A sparc-objdump -a on vmlinux says that
chunk has:

f00de63c:       84 0b 60 ff     and  %o5, 0xff, %g2
f00de640:       91 32 20 10     srl  %o0, 0x10, %o0
f00de644:       85 28 a0 08     sll  %g2, 8, %g2
f00de648:       98 0a 20 ff     and  %o0, 0xff, %o4
f00de64c:       03 00 00 3f     sethi  %hi(0xfc00), %g1
f00de650:       82 10 63 00     or  %g1, 0x300, %g1     ! ff00
<cputypvallen+0xfef4>
f00de654:       90 0a 00 01     and  %o0, %g1, %o0

Which means nothing to me.

I bisected it to this:

commit 9933fc0ac1ac14b795819cd63d05ea92112f690a
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Mon Aug 1 08:45:02 2011 -0400

    ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree()

    Introduce new helper functions which try kmalloc, and then fall back
   to vmalloc if necessary, and use them for allocating and deallocating
    s_flex_groups.

    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

The commit before that builds fine, this one doesn't.

I think it's triggering bad behavior in arch/sparc/mm/btfixup.c (at
least that's where the "valid instruction" error message comes from),
but I have no idea what this file is doing, and it was last touched in
2008.  (I'm building with gcc 4.2.1 and binutils 2.17, both of which
were last touched around 2006, so that's not new either...)

Rob

             reply	other threads:[~2011-11-12 17:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-12 17:22 Rob Landley [this message]
2011-11-12 17:22 ` Sparc-32 doesn't work in 3.1 Rob Landley
2011-11-13  0:07 ` Rob Landley
2011-11-13  0:07   ` Rob Landley
2011-12-11  8:17   ` Sergei Trofimovich
2011-12-11  8:17     ` Sergei Trofimovich
2011-12-14  2:23     ` Rob Landley
2011-12-14  2:23       ` Rob Landley
2011-12-14 17:42       ` Sergei Trofimovich
2011-12-14 17:42         ` Sergei Trofimovich
2011-12-14 17:49         ` Eric Dumazet
2011-12-14 17:49           ` Eric Dumazet
2011-12-14 17:53         ` David Miller
2011-12-14 17:53           ` David Miller
2011-12-14 17:54         ` David Miller
2011-12-14 17:54           ` David Miller
2011-12-14 18:18           ` David Miller
2011-12-14 18:18             ` David Miller
2011-12-14 18:55             ` Sergei Trofimovich
2011-12-14 18:55               ` Sergei Trofimovich
2011-12-14 19:13               ` David Miller
2011-12-14 19:13                 ` David Miller
2011-12-14 19:27                 ` Rob Landley
2011-12-14 19:27                   ` Rob Landley
2011-12-14 19:26             ` Rob Landley
2011-12-14 19:26               ` 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=4EBEAB5A.5020809@landley.net \
    --to=rob@landley.net \
    --cc=aboriginal@lists.landley.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.