Skip to contentSkip to conversation

backtrace symbols are bolixed...

DISCUSSION David Miller 3 participants 5 messages Jun 19, 2009

lore
Share & tools
lore
#0 lore raw

Sometime in the last day or so backtrace symbol printouts have become useless:

[    0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660()
[    0.000000] Modules linked in:
[    0.000000] Call Trace:
[    0.000000]  [00000000008611b4] __stop_notes+0xbb10/0x1d660
[    0.000000]  [000000000086195c] __stop_notes+0xc2b8/0x1d660
[    0.000000]  [0000000000861a28] __stop_notes+0xc384/0x1d660
[    0.000000]  [0000000000858678] __stop_notes+0x2fd4/0x1d660
[    0.000000]  [000000000085684c] __stop_notes+0x11a8/0x1d660
[    0.000000]  [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18
[    0.000000]  [0000000000000000] (null)

I'll try to bisect but maybe someone can figure it out quickly meanwhile.

#1 lore raw

Hi Dave,

Quoted 15 lines · On Fri, 19 Jun 2009 00:21:01 -0700 (PDT) David Miller <[email protected]>…

Sometime in the last day or so backtrace symbol printouts have become useless:

[    0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660()
[    0.000000] Modules linked in:
[    0.000000] Call Trace:
[    0.000000]  [00000000008611b4] __stop_notes+0xbb10/0x1d660
[    0.000000]  [000000000086195c] __stop_notes+0xc2b8/0x1d660
[    0.000000]  [0000000000861a28] __stop_notes+0xc384/0x1d660
[    0.000000]  [0000000000858678] __stop_notes+0x2fd4/0x1d660
[    0.000000]  [000000000085684c] __stop_notes+0x11a8/0x1d660
[    0.000000]  [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18
[    0.000000]  [0000000000000000] (null)
Quoted 2 lines

I'll try to bisect but maybe someone can figure it out quickly meanwhile.

Try the following patch:

From: Mike Frysinger <[email protected]>
Date: Mon, 15 Jun 2009 07:52:48 -0400
Subject: [PATCH] kallsyms: fix inverted valid symbol checking

The previous commit (17b1f0de) introduced a slightly broken consolidation of the memory text range checking.

---
 scripts/kallsyms.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
scripts/kallsyms.c +3 -3
index 3cb5789..64343cc 100644
@@ -167,11 +167,11 @@ static int symbol_valid_tr(struct sym_entry *s)
 	for (i = 0; i < ARRAY_SIZE(text_ranges); ++i) {
 		tr = &text_ranges[i];
 
-		if (s->addr >= tr->start && s->addr < tr->end)
-			return 0;
+		if (s->addr >= tr->start && s->addr <= tr->end)
+			return 1;
 	}
 
-	return 1;
+	return 0;
 }
 
 static int symbol_valid(struct sym_entry *s)
Signature · 7 lines
1.6.3.1


-- 
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/
#2 lore raw

From: Stephen Rothwell <[email protected]>
Date: Fri, 19 Jun 2009 17:30:52 +1000

Quoted 10 lines

Try the following patch:

From: Mike Frysinger <[email protected]>
Date: Mon, 15 Jun 2009 07:52:48 -0400
Subject: [PATCH] kallsyms: fix inverted valid symbol checking

The previous commit (17b1f0de) introduced a slightly broken consolidation of the memory text range checking.

That fixed it, thanks!

#3 lore raw
In reply to David Miller
Quoted 14 lines · David Miller

Sometime in the last day or so backtrace symbol printouts have become useless:

[    0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660()
[    0.000000] Modules linked in:
[    0.000000] Call Trace:
[    0.000000]  [00000000008611b4] __stop_notes+0xbb10/0x1d660
[    0.000000]  [000000000086195c] __stop_notes+0xc2b8/0x1d660
[    0.000000]  [0000000000861a28] __stop_notes+0xc384/0x1d660
[    0.000000]  [0000000000858678] __stop_notes+0x2fd4/0x1d660
[    0.000000]  [000000000085684c] __stop_notes+0x11a8/0x1d660
[    0.000000]  [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18
[    0.000000]  [0000000000000000] (null)
Quoted 2 lines

I'll try to bisect but maybe someone can figure it out quickly meanwhile.

I saw this too. One change that went upstream when i started seeing these weird backtraces is:

ad6ccfa: kernel/kallsyms.c: replace deprecated __initcall with device_initcall and fix

Sam and Andrew Cc:-ed.

Ingo

#4 lore raw

From: Ingo Molnar <[email protected]>
Date: Fri, 19 Jun 2009 09:30:53 +0200

Quoted 16 lines · David Miller
Quoted 15 lines

Sometime in the last day or so backtrace symbol printouts have become useless:

[    0.000000] WARNING: at mm/bootmem.c:535 __stop_notes+0xbb10/0x1d660()
[    0.000000] Modules linked in:
[    0.000000] Call Trace:
[    0.000000]  [00000000008611b4] __stop_notes+0xbb10/0x1d660
[    0.000000]  [000000000086195c] __stop_notes+0xc2b8/0x1d660
[    0.000000]  [0000000000861a28] __stop_notes+0xc384/0x1d660
[    0.000000]  [0000000000858678] __stop_notes+0x2fd4/0x1d660
[    0.000000]  [000000000085684c] __stop_notes+0x11a8/0x1d660
[    0.000000]  [00000000006e8bdc] _etext+0xfffffffffffe59f4/0xe18
[    0.000000]  [0000000000000000] (null)
Quoted 5 lines
Quoted 2 lines

I'll try to bisect but maybe someone can figure it out quickly meanwhile.

I saw this too. One change that went upstream when i started seeing these weird backtraces is:

The patch from Mike Frysinger posted by Stephen Rothwell fixes it for me.