All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: Neil Brown <neilb@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: 2.6.21-rc5-mm[12]: Oops on bootup in xor_see_2
Date: Tue, 3 Apr 2007 11:02:40 +0000	[thread overview]
Message-ID: <200704031102.40863.bero@arklinux.org> (raw)
In-Reply-To: <17934.54983.192724.145829@notabene.brown>

On Saturday 31 March 2007, Neil Brown wrote:
> > > Code: 44 89 74 24 48 0f 20 c6 0f 06 0f 11 04 24 0f 11 4c 24 10 0f 11 54
> > > 24 20 0f
> > >       11 5c 24 30 0f 18 82 00 01 00 00 0f 18 82 20 01 00 00 <00> 00 00
> > > 00 00 00
> > >       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > -
>
> Them bytes that look like '00' are mostly supposed to look like 'F0' -
> an x86 'noop'.
>
> Apparently a bin-utils bug.  An alpha of OpenSUSE-10.3 was compiling
> kernels like this.  I'm told it has been fixed.
>
> What distro/gcc version/binutils version was this compiled on?

You're right -- I'm using the current Ark Linux 2007.1 experimental build 
(always the latest stuff) - the update to binutils 2.17.50.0.13 broke it, 
after upgrading binutils to 2.17.50.0.14 everything is working perfectly 
again.

Thanks
bero

      reply	other threads:[~2007-04-03  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 17:36 2.6.21-rc5-mm[12]: Oops on bootup in xor_see_2 Bernhard Rosenkraenzer
2007-03-31 19:40 ` Andrew Morton
2007-03-31 21:46   ` Neil Brown
2007-04-03 11:02     ` Bernhard Rosenkraenzer [this message]

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=200704031102.40863.bero@arklinux.org \
    --to=bero@arklinux.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.