mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Paulo Marques <pmarques@grupopie.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: inconsistent kallsyms data [2.6.11-mm2]
Date: Mon, 14 Mar 2005 23:14:21 +0100	[thread overview]
Message-ID: <20050314221421.GA13378@isilmar.linta.de> (raw)
In-Reply-To: <423039A6.5010301@grupopie.com>

On Thu, Mar 10, 2005 at 12:12:22PM +0000, Paulo Marques wrote:
> Paulo Marques wrote:
> >[...]
> >A simple and robust way is to do the sampling on a list of symbols 
> >sorted by symbol name. This way, even if the symbol positions that are 
> >given to scripts/kallsyms change, the symbols sampled will be the same.
> >
> >I'll do the patch to do this and send it ASAP.
> 
> Ok, here it is.
> 
> Dominik can you try the attached patch and see if it solves the problem?

It does not solve the problem: 

 ~/local/kernel/linux-2.6.11-mm2 $ patch -p1 < ~/kallpatch 
patching file scripts/kallsyms.c
 ~/local/kernel/linux-2.6.11-mm2 $ make
  CHK     include/linux/version.h
  HOSTCC  scripts/kallsyms
make[1]: »arch/i386/kernel/asm-offsets.s« ist bereits aktualisiert.
  CHK     include/linux/compile.h
  CHK     usr/initramfs_list
  CC [M]  arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.o
  KSYM    .tmp_kallsyms1.S
  AS      .tmp_kallsyms1.o
  LD      .tmp_vmlinux2
  KSYM    .tmp_kallsyms2.S
  AS      .tmp_kallsyms2.o
  LD      vmlinux
  SYSMAP  System.map
  SYSMAP  .tmp_System.map
Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
make: *** [vmlinux] Fehler 1


Will test the other patch floating around in just a moment.

Thanks,
	Dominik

  parent reply	other threads:[~2005-03-14 22:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 11:38 2.6.11-mm2 Andrew Morton
2005-03-08 13:58 ` 2.6.11-mm2 Paul Mundt
2005-03-08 19:40   ` 2.6.11-mm2 Andrew Morton
2005-03-08 16:00 ` 2.6.11-mm2 (compile stats) John Cherry
2005-03-08 18:54 ` 2.6.11-mm2 fremap.c compile error Jurriaan
2005-03-11 22:50   ` Adrian Bunk
2005-03-08 19:29 ` inconsistent kallsyms data [2.6.11-mm2] Dominik Brodowski
2005-03-08 20:35   ` Andrew Morton
2005-03-08 20:45     ` Dominik Brodowski
2005-03-09 12:57       ` Paulo Marques
2005-03-09 20:16         ` Paulo Marques
2005-03-10 12:12           ` Paulo Marques
2005-03-13  8:54             ` Sam Ravnborg
2005-03-14 13:33               ` Paulo Marques
2005-03-14 22:17               ` Dominik Brodowski
2005-03-14 22:14             ` Dominik Brodowski [this message]
2005-03-08 23:20 ` 2.6.11-mm2 Christoph Hellwig
2005-03-08 23:29   ` 2.6.11-mm2 Andrew Morton
2005-03-08 23:36 ` 2.6.11-mm2 J.A. Magallon
2005-03-08 23:44   ` 2.6.11-mm2 Robert Love
2005-03-08 23:51     ` 2.6.11-mm2 J.A. Magallon
2005-03-09  0:02       ` 2.6.11-mm2 Robert Love
2005-03-09  0:16 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  0:53   ` 2.6.11-mm2 Andrew Morton
2005-03-09  1:39     ` 2.6.11-mm2 Jeff Garzik
2005-03-09  0:20 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  1:50   ` 2.6.11-mm2 Karsten Keil
2005-03-10  7:57 ` 2.6.11-mm2 Stefano Rivoir
2005-03-10  8:09   ` 2.6.11-mm2 Andrew Morton
2005-03-21 23:45   ` 2.6.11-mm2 Andrew Morton

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=20050314221421.GA13378@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    /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®