mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Stephen Hemminger <shemminger@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.18-rc3-mm2 (+ hotfixes): GPF related to skge on suspend
Date: Mon, 14 Aug 2006 10:54:21 +1000	[thread overview]
Message-ID: <17555.1155516861@ocs10w.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 13 Aug 2006 17:35:03 MST." <20060813173503.e009583c.akpm@osdl.org>

Andrew Morton (on Sun, 13 Aug 2006 17:35:03 -0700) wrote:
>On Mon, 14 Aug 2006 10:21:55 +1000
>Keith Owens <kaos@ocs.com.au> wrote:
>
>> ksymoops -VKLMO -t elf64-x86-64 -a i386:x86-64
>
>box:/home/akpm> ksymoops -VKLMO -t elf64-x86-64 -a i386:x86-64 < x
>ksymoops 2.4.11 on x86_64 2.6.17-rc5.  Options used
>     -V (specified)
>     -K (specified)
>     -L (specified)
>     -O (specified)
>     -M (specified)
>     -t elf64-x86-64 -a i386:x86-64
>
>Warning (merge_maps): no symbols in merged map
>CPU 0
>...
> [<ffffffff80471e5b>] _spin_unlock_irq+0x2b/0x60
> [<ffffffff8020a2c0>] restore_args+0x0/0x30
> [<ffffffff80243620>] kthread+0x0/0x110
> [<ffffffff8020a6fe>] child_rip+0x0/0x12
>Code: 44 8b 28 c7 45 d0 00 00 00 00 45 85 ed 0f 89 29 fb ff ff e9
>Error (Oops_bfd_perror): /tmp/ksymoops.0lrVNY Invalid bfd target
>
>box:/home/akpm> rpm -qi ksymoops 
>Name        : ksymoops                     Relocations: (not relocatable)
>Version     : 2.4.11                            Vendor: (none)
>Release     : 1                             Build Date: Sat Jan  8 05:43:45 2005
>Install Date: Wed Jun 28 16:59:45 2006      Build Host: ocs3.ocs.com.au
>Group       : Utilities/System              Source RPM: ksymoops-2.4.11-1.src.rpm

Back in 2000 there were a lot of version problems between ksymoops and
libbfd and libiberty, so I statically link against these libraries when
I build the rpm.  You have an i386 version of ksymoops, which was built
against an i386 only version of libbfd, it does not support target
elf64-x86-64.  Grab the ksymoops src.rpm and rebuild on x86_64, or use
a binary rpm from an x86_64 distribution.


  reply	other threads:[~2006-08-14  0:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  8:53 Chuck Ebbert
2006-08-13 17:38 ` Andrew Morton
2006-08-14  0:21 ` Keith Owens
2006-08-14  0:35   ` Andrew Morton
2006-08-14  0:54     ` Keith Owens [this message]
2006-08-14  1:06       ` Andrew Morton
2006-08-14  1:10         ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2006-08-12 10:07 Rafael J. Wysocki
2006-08-12 12:28 ` Andrew Morton
2006-08-12 13:39   ` Jeff Garzik
2006-08-12 14:32     ` Rafael J. Wysocki
2006-08-12 19:34       ` Rafael J. Wysocki
2006-08-12 14:31   ` Rafael J. Wysocki
2006-08-12 16:12     ` Edgar E. Iglesias
2006-08-12 17:13       ` Rafael J. Wysocki
2006-08-12 18:16         ` Edgar E. Iglesias
2006-08-12 19:32           ` Rafael J. Wysocki
2006-08-13  5:56           ` Stephen Hemminger

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=17555.1155516861@ocs10w.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=shemminger@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®