All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-alpha@vger.kernel.org
Subject: Re: [1/4] 2.6.23-rc4: known regressions
Date: Thu, 30 Aug 2007 20:46:37 +0200	[thread overview]
Message-ID: <46D7108D.9090104@l4x.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708301112030.7975@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Thu, 30 Aug 2007, Jan Dittmer wrote:
> 
>> Christoph Lameter wrote:
>>> On Thu, 30 Aug 2007, Adrian Bunk wrote:
>>>
>>>> Christoph, is your fix in -mm suitable for 2.6.23, or how else should this
>>>> regression be fixed for 2.6.23?
>>> Looks like this is just alpha and a certain particular compiler version? 
>> binutils 2.15.95, gcc 3.3.6 and I could update to 4.0.4 or something
>> more recent I guess. And yes, it's only alpha.
>>
>> Of which file do you want the objdump?
> 
> The one where the link fails. Dump the code around the unresolved symbol.

Here is one of them:

   19380:       10 00 1f 20     lda     v0,16
   19384:       e6 ff ff c3     br      19320 <srmcons_get_private_struct+0x90>
                 * Generate a link failure. Would be great if we could
                 * do something to stop the compile here.
                 */
                extern void __kmalloc_size_too_large(void);
                __kmalloc_size_too_large();
   19388:       00 00 7d a7     ldq     t12,0(gp)
   1938c:       00 40 5b 6b     jsr     ra,(t12),19390 <srmcons_get_private_struct+0x100>
   19390:       00 00 ba 27     ldah    gp,0(ra)
   19394:       00 00 bd 23     lda     gp,0(gp)
   19398:       d6 ff ff c3     br      192f4 <srmcons_get_private_struct+0x64>
   1939c:       00 00 fe 2f     unop

Jan

  reply	other threads:[~2007-08-30 18:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 15:26 [1/4] 2.6.23-rc4: known regressions Michal Piotrowski
2007-08-29 18:04 ` Jan Dittmer
2007-08-29 23:29   ` [2.6.23 patch] xtensa process.c must #include <linux/fs.h> Adrian Bunk
2007-08-29 23:47   ` [1/4] 2.6.23-rc4: known regressions Adrian Bunk
2007-08-30  0:11     ` Christoph Lameter
2007-08-30  0:39     ` Christoph Lameter
2007-08-30  7:10       ` Jan Dittmer
2007-08-30 18:12         ` Christoph Lameter
2007-08-30 18:46           ` Jan Dittmer [this message]
2007-08-31  7:48             ` Christoph Lameter
2007-08-31  7:48               ` Christoph Lameter
2007-08-31  8:03               ` Adrian Bunk
2007-08-29 19:07 ` Jeff Chua

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=46D7108D.9090104@l4x.org \
    --to=jdi@l4x.org \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=clameter@sgi.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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.