Re: backtrace symbols are bolixed...

[Ingo Molnar]

* David Miller <davem@xxxxxxxxxxxxx> wrote:

> 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.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/